Deprecating Site Local Addresses
draft-ietf-ipv6-deprecate-site-local-03
Yes
(Alex Zinin)
(Bill Fenner)
(Jon Peterson)
(Margaret Cullen)
(Steven Bellovin)
(Ted Hardie)
No Objection
(Bert Wijnen)
(David Kessens)
(Russ Housley)
Note: This ballot was opened for revision 03 and is now closed.
Alex Zinin Former IESG member
(was Discuss)
Yes
Yes
()
Unknown
Allison Mankin Former IESG member
(was Discuss)
Yes
Yes
(2004-03-18)
Unknown
I'm clearing my Discuss because Thomas has written the right IANA fix that I was referring to.
Bill Fenner Former IESG member
Yes
Yes
()
Unknown
Harald Alvestrand Former IESG member
Yes
Yes
(2004-03-16)
Unknown
One comment to the security considerations section by Scott Brim, GEN-AREA reviewer: in the Security section, I would add a paragraph reiterating of the issues due to ambiguity which were brought up in the preceding sections. Leakage, misrouting, etc., are noteworthy security issues. Not worth holding the document for.
Jon Peterson Former IESG member
Yes
Yes
()
Unknown
Margaret Cullen Former IESG member
Yes
Yes
()
Unknown
Steven Bellovin Former IESG member
Yes
Yes
()
Unknown
Ted Hardie Former IESG member
Yes
Yes
()
Unknown
Thomas Narten Former IESG member
(was No Record, Discuss)
Yes
Yes
(2004-03-18)
Unknown
> Applications would learn or remember that the address of some > correspondent was "FEC0::1234:5678:9ABC", they would try to feed the > address in a socket address structure and issue a connect, and the > call will fail because they did not fill up the "site identifier" > variable, as in "FEC0::1234:5678:9ABC&1". The problem is compounded Would be good to cite the document that explains the "&" syntax in addresses. > Having non-ambiguous address solves a large part of the developers' s/address/addresses/
Bert Wijnen Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
(2004-03-08)
Unknown
RFC 3513 is listed as both a normative reference and an informative reference. I would suggest striking it from the list of informative references.