Neighbor Discovery for IP version 6 (IPv6)
RFC 4861

Dialogue between Gen-ART reviewer (Scott Brim) and author:

 > 3.0 protocol overview
 > 
 >   - Duplicate address detection
 > 
 >      "Duplicate Address Detection: How a node determines that an
 >      address it wishes to use is not already in use by another node."
 > 
 >     should be
 > 
 >      "Duplicate Address Detection: How a node determines whether or
 >      not an address it wishes to use is already in use by another
 >      node."

=> ok.

 >       
 >   - Router advertisement: the phrase "on-link determination" has not
 >     appeared before.  It should be explained.

=> We can add a reference here.

 > 6.2.1 router config variables
 > 
 >   - AdvCurHopLimit
 > 
 >       "The value should be set to that current diameter of the
 >       Internet."
 > 
 >     s/that/the/

=> ok.

["Current diameter of the Internet" is an interesting concept - BC]

 > 8.2.  Router Specification
 ...
 >   - "In the Target Address field: the address to which subsequent
 >     packets for the destination SHOULD be sent."
 > 
 >     That's talking about the recipient of the redirect.  It's not
 >     about the sender's behavior, so this SHOULD should not be
 >     capitalized.

=> Hmm. That's true.

I believe that the first and second sentence in the first paragraph of 6.2.1 may be interpreted as contradictory and be confusing:

OLD: 

   A router MUST allow for the following conceptual variables to be
   configured by system management.  The specific variable names are
   used for demonstration purposes only, and an implementation is not
   required to have them, so long as its external behavior is consistent
   with that described in this document.  Default values are specified
   to simplify configuration in common cases.

I suggest to add a few words of clarification and turn this into: 

NEW: 

   A router MUST allow for the following conceptual variables to be
   configured by system management.  The specific variable names are
   used for demonstration purposes only, and an implementation is not
   required to have them, so long as its external behavior is consistent
   with that described in this document, and the functions described
   by the conceptual variables are configurable by some external 
   management interface.  Default values are specified to simplify 
   configuration in common cases.

While we address Thomas' comments, we should
also look into Donald Estlake's and Ralph
Droms' reviews and how to address them.

Nit in Appendix F


    o Clarified that inconsistency checks for CurHopLimit are done for
      none zero values only.

should be "non-zero", most likely.