Hi,
I do not support this action. The words in the abstract in RFC6346:
We are facing the exhaustion of the IANA IPv4 free IP address pool.
Unfortunately, IPv6 is not yet deployed widely enough to fully
replace IPv4, and it is unrealistic to expect that this is going to
change before the depletion of IPv4 addresses. Letting hosts
seamlessly communicate in an IPv4 world without assigning a unique
globally routable IPv4 address to each of them is a challenging
problem.
are not accurate. Noting one of many statistics that IPv6 use is growing,
Google is reporting that 5% of their access traffic is from IPv6:
http://www.google.com/intl/en/ipv6/statistics.html
We have effectively gotten to the point of depletion of IPV4 addresses, and the
world has not come to an end. I don't see any need to reclassify this RFC as a
standard and think doing so would cause confusion in the community and be
harmful to the Internet.
Bob
On Dec 1, 2014, at 2:38 PM, The IESG <iesg-secretary(_at_)ietf(_dot_)org> wrote:
The IESG has received a request from an individual participant to make
the following status changes:
- RFC6346 from Experimental to Proposed Standard
(The Address plus Port (A+P) Approach to the IPv4 Address Shortage)
The supporting document for this request can be found here:
http://datatracker.ietf.org/doc/status-change-address-plus-port-to-proposed/
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2014-12-29. Exceptionally, comments
may be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
The affected document can be obtained via
http://datatracker.ietf.org/doc/rfc6346/
IESG discussion of this request can be tracked via
http://datatracker.ietf.org/doc/status-change-address-plus-port-to-proposed/ballot/
signature.asc
Description: Message signed with OpenPGP using GPGMail