Detecting Network Attachment in IPv4 (DNAv4)
RFC 4436
Yes
No Objection
Note: This ballot was opened for revision 18 and is now closed.
(Margaret Cullen; former steering group member) Yes
Comment/question from Jari Arrko's Mobility Directorate review: > [c] If secure detection of network attachment is required. > The reachability test utilizes ARP which is insecure. What, specifically, is your model of "secure detection of network attachment"? How do I implement this requirement in a host i.e. what feature must be on for me to skip DNAv4? Do you mean that if DHCP authentication is on then we skip DNAv4? Also, some forms of secure ARP (e.g. Cisco's DHCP-secured ARP) appear to work without host involvement and would appear to be compatible with DNAv4.
(Alex Zinin; former steering group member) No Objection
(Allison Mankin; former steering group member) No Objection
(Bert Wijnen; former steering group member) No Objection
(Bill Fenner; former steering group member) No Objection
(Brian Carpenter; former steering group member) No Objection
(David Kessens; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sam Hartman; former steering group member) (was Discuss) No Objection
(Scott Hollenbeck; former steering group member) No Objection
(Ted Hardie; former steering group member) No Objection
The document says: Experience has shown that IPv4 Link-Local addresses are often assigned inappropriately, compromising both performance and connectivity. Is there a citation for this, or was this experience shared with the working group?