Dear authors, all, Here are my comments/questions regarding the 6lowpan-nd-15 draft. In general the document looks in good shape.
1) Parts on multicast may benefit from some more clarification: section 5.1 "A host would never multicast" -> is this "A host MUST NOT multicast" or SHOULD NOT ? section 5.6 "Multicast addresses are considered to be on-link and are resolved as specified in [RFC4944] or the appropriate IP-over-foo document." However section 5.7 says "As all prefixes but the link-local prefix are always assumed to be off-link, multicast-based address resolution between neighbors is not needed", implying the contrary that multicast addresses are always off-link. Does this conflict? Also, section 5.6 appears to refer to RFC 4944 Section 9, which is only applicable for mesh-under configurations. What about multicast in route-over configurations? (Should it be made more explicit here?) Finally, the text in 5.6 "All other prefixes are assumed to be off-link [RFC5889]" should perhaps be moved lower, so that it indicates the final case of this section. I.e. to first describe the special cases, then finally describe the "all other" case would be clearer I think. 2) Registration lifetime calculation: section 5.8.2. mentions "the maximum Registration lifetime is about 7 days". Taking 65535 units of 60 seconds however, I find 45.5 days? 3) Finally, some typos & minor remarks: section 1.3 last paragraph: "involunterily" "NCE" abbreviation is not defined on first use, also not used in RFC 4861, so should perhaps be defined here. section 1.4 "messages in host-router interface and" -> "messages in host-router interfaces and" ? "multhop" -> multihop section 3.1 "mechanism using new Address" ->"mechanism using a new Address" section 3.5 "As Routers send RAs to hosts, and when routers optionally receive RA messages or receive multicast NS messages from other Routers the result is Garbage-collectible NCEs." -> Maybe more clear using: "When Routers send RAs to hosts, and when routers optionally receive RA messages or receive multicast NS messages from other Routers, the result is Garbage-collectible NCEs." section 4.1 "an SLLA option MUST be include" -> abbreviation "SLLA" is not defined on first use. Also not used in RFC 4861 main text, so could be defined here. section 5.5 (last sent.) "use a router it is registered, it" -> "use a router it is registered to, it" overall: The text "section section" appears a few times. best regards, Esko Esko Dijk Philips Corporate Technologies, Research High Tech Campus 34, Eindhoven, The Netherlands [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Carsten Bormann Sent: Thursday 17 February 2011 16:58 To: 6lowpan Subject: [6lowpan] Working Group Last call for draft-ietf-6lowpan-nd-15 In September/October, we had the first WGLC on 6LoWPAN-ND, which resulted in a number of detailed comments and two resulting fine-tuning iterations of the draft. draft-ietf-6lowpan-nd-15.txt has been out for two months now. I understand it has taken part in several interops with multiple implementations in this period; no issues came up. We now start the Working Group Last Call on: http://tools.ietf.org/html/draft-ietf-6lowpan-nd-15 The document is planned to be submitted by this Working Group to the IESG for publication as a Standards-Track Document. This is a two-week Working-Group Last-Call, ending on Thursday, 2011-03-03 at 2359 UTC. Please review the changes to the document carefully once more, and send your comments to the 6lowpan list. Please also do indicate to the list if you are all-OK with the document. Gruesse, Carsten _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
