Pasi et al,
Good feedback as usual from the gen-art folk, thanks!
Comments inline, primarily for the draft editors. I don't believe
there's anything significant here that can't be addressed in
RFC Editor comments.
On Mar 18, 2007, at 6:35 AM, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
1) As the PROTO write-up already pointed out, the current version
has a normative downward reference to draft-ietf-l3vpn-bgpvpn-auto.
To me it seems this might be changed to informative reference,
but probably someone more familiar with the protocol(s) should
also confirm this.
Yep.
2) In Section 3.2 the document uses the phrases like "the AC ID is
NULL" to mean that that "AC ID" field is not included in the message
at all. I found this a bit confusing; probably something like "the AC
ID field is omitted" would be clearer?
Yes, and tightening up the corresponding text in the final
bullet of section 3.2.
3) Section 3.2, "If the global ID is derived from a 2-octet AS
number, then the high-order 4 octets of this 4 octet field MUST
be set to zero." Should this be "...the high-order 2 octets..."?
Yes, I believe so..
4) The document uses RFC 2119 keywords, but does not include
RFC 2119 in the references list.
Indeed..
-danny
_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art
