On Jul 14, 2012, at 3:18 PM, Christian Huitema wrote: > Very useful document, certainly worth publishing. +1 > It is one of those documents that needs frequent updates. > +1 > RFC 6052, IPv6 Addressing of IPv4/IPv6 Translators, makes reference to a predecessor of this document, stating in section 3.1 that "The Well-Known Prefix MUST NOT be used to represent non-global IPv4 addresses, such as those defined in [RFC1918] or listed in Section 3 of [RFC5735]." I assume that implementers will automatically upgrade their code to reference the new version. > -1 -- I would not assume any such thing. I *might* guess that implementors will include the new version in new / updated code, but the not necessarily the "automatically" bit :-P W > -----Original Message----- > From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On Behalf Of Randy Bush > Sent: Friday, July 13, 2012 4:21 PM > To: IETF Disgust; The IESG > Subject: [IETF] Re: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt> (Special Use IPv4 Addresses) to Best Current Practice > >> The IESG has received a request from an individual submitter to >> consider the following document: >> - 'Special Use IPv4 Addresses' >> <draft-vegoda-cotton-rfc5735bis-02.txt> as Best Current Practice > > read and support > > randy > > -- "Working the ICANN process is like being nibbled to death by ducks, it takes forever, it doesn't make sense, and in the end we're still dead in the water." -- Tom Galvin, VeriSign's vice president for government relations.