Thanks for your second round of comments Peter. See comments inline. > Page 6, Rsvd2 definition: the definition both says "reserved for future use" > and then says some types actually use it. That sounds like present use. > And to generically say that it should be sent as zero and ignored, but then > to give uses (such as Type 2) for it is confusing. I suggest rethinking > the wording here. I have fixed this and received multiple comemnts on this from various people. > Page 6, Length definition: there's mention of a "Reserved" field that's > included in the minimum length of 8 bytes that are not part of the length > value. Since there are actually Rsvd1 and Rsvd2 fields in the generic > version of the LCAF and sometimes even Rsvd3 and Rsvd4 fields when using > specific Types, it might be better to spell out which reserved fields (Rsvd1 > and Rsvd2) are meant here rather than giving the field a summary name that > doesn't actually appear in the format. This is also important because any > Rsvd3 and Rsvd4 fields are included in the Length field, so using a generic > "Reserved" description is ambiguous at best. Should be fixed now. > Page 13, RTR RLOC Address definition, 4th sentence: The ability to determine > the number of RTRs encoded by looking at the value of the LCAF length > doesn't seem feasible. 3 IPv4 RTR RLOCs will produce the same LCAF Length > as 1 IPv6 RTR RLOC. Fixed now. > Page 13, RTR RLOC Address definition, 5th sentence: this sentence gives two > means to indicate that there RTR field values. What's the point of having > two different means of doing so? This just seems to introduce complexity > and increase the chance for implementations that may not handle both schemes > correctly. One scheme ought to suffice. I prefer the Length field method > since it requires fewer bytes transmitted, but either works. An implementation must be prepared to find the RTR RLOC address entry with an AFI=0. So either the length includes all bytes up to and including the “Private ETR RLOC Address” field which basically encodes no “RTR RLOC Address” more efficiently or it does include an AFI=0 for the “RTR RLOC Address” entry. Since an AFI can be a value of 0 in any LISP message, we have to document the two ways to encode “no RLOC addresses”. > Nits: > > Page 5, Type definition: change the comma to a semicolon. > > Page 8, Usage, 1st sentence: change the second "a" to "an". > > Page 9, AS Number definition: insert "to" before "either". > > Page 13, RTR RLOC Address definition, 3rd sentence: change "these" to > "this". > > Page 14, section 4.5, 2nd paragraph: change "it's" to "its". > > Page 15, Source/Subnet Address and Group Address definitions: delete an > extra space before "is" in each definition. > > Page 16, Strict bit (S) definition, 1st sentence: change "Rencap" to > "Reencap". > > Page 18, Key Count definition, 2nd sentence: change "the" to "of". > > Page 18, AFI = x definition: insert two spaces before the second sentence. > > Page 24, section 4.10.3, 1st paragraph: delete "where it is delimited by > length 'n' of the LCAF Length encoding" > > Page 26, 1st paragraph after Length2 definition: change "AFI-encoded" to > "AFI encoded". My apologies for suggesting a blind find-and-replace in the > previous review. Obviously that was wrong here. Made changes for above. > Page 27, section 5.1, Length value n definition: I'm not sure what qualifies > as "8-byte Application Data fields", but there appear to be 12 bytes before > the AFI and that's reflected in the Length field in the figure. So the > local and remote port ranges are the 8-byte Application Data fields? This > comes back to my minor issue with how Length values are described in the > text and in the figures. Please clarify what's meant here. I don’t find any reference in document -17 to "8-byte Application Data fields”. > Page 29, Key Field Num definition: change "the the" to "the". > > Page 32, section 5.5, 1st paragraph, 2nd sentence: insert "the" before > "key”. Made these changes too. Thanks. Dino