IPv6 Neighbor Discovery On-Link Assumption Considered Harmful
RFC 4943

Note: This ballot was opened for revision 04 and is now closed.

(Bill Fenner; former steering group member) Yes

Yes (2005-12-15 for -)
No email
send info
I'm glad to see documentation of design decisions (& changes thereto).  I wish there was more of this, so there could be less "What were they thinking in 2005 when they removed the on-link assumption!?" in 2010 ;-)

(David Kessens; former steering group member) Yes

Yes ( for -)
No email
send info

(Allison Mankin; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Bert Wijnen; former steering group member) No Objection

No Objection (2005-12-15 for -)
No email
send info

!! Missing citation for Informative reference:
  P007 L015:    [RFC2462]  Thomson, S. and T. Narten, "IPv6 Stateless Address

(Brian Carpenter; former steering group member) No Objection

No Objection (2005-12-13 for -)
No email
send info

(Margaret Cullen; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Sam Hartman; former steering group member) No Objection

No Objection ( for -)
No email
send info

(Ted Hardie; former steering group member) No Objection

No Objection (2005-12-13 for -)
No email
send info
I found Section 3.3 very hard to parse.  This section, in particular:

   The second option
   might succeed in reaching a destination (assuming that one is
   reachable) but is more complex to implement, and isn't guaranteed to
   pick the correct destination.  For example, there is still ambiguity
   about which link to use if more than one node answers the
   solicitations on multiple links. 

In previous parts of Section 3, we seemed to be dealing with a host attempting to send
a packet using a known AAAA record.  In this section, it's not clear whether the argument
is that a host with multiple interfaces has an interface selection problem that is unresolvable
because of on-link assumptions, or that the on-link assumption again causes a poor ordering
of attempts to reach a host, or causes ambiguity because of non-globally unique addressing.
Some clarification would probably help here.