As I have said before, I think that it would be a mistake to make this
declaration.
A lot of the world still relies heavily on IPv4, and many countries
would rightly regard IPv4 as critical national infrastructure.
If the IETF announces that it is no longer supporting IPv4, then those
countries would have every right to demand that the ITU-T took over
responsibility for IPv4 development and maintenance of the protocol. If
that happened you would naturally expect them to extend its life,
perhaps even creating a viable competitor to IPv6 with all of the
difficulty and confusion that would then result.
Whilst I think the elements of the ID that talk about ensuring that
every protocol can run in an IPv6 only network are useful, although much
stated in the past, I think that it would be a serious mistake to give
any appearance of abandoning IPv4.
- Stewart
On 28/09/2017 14:26, The IESG wrote:
The IESG has received a request from the Sunsetting IPv4 WG (sunset4) to
consider the following document: - 'IETF: End Work on IPv4'
<draft-ietf-sunset4-ipv6-ietf-01.txt> as Proposed Standard
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@xxxxxxxx mailing lists by 2017-10-12. Exceptionally, comments may be
sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.
Abstract
The IETF will stop working on IPv4, except where needed to mitigate
documented security issues, to facilitate the transition to IPv6, or
to enable IPv4 decommissioning.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-sunset4-ipv6-ietf/
IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-sunset4-ipv6-ietf/ballot/
No IPR declarations have been submitted directly on this I-D.
The document contains these normative downward references.
See RFC 3967 for additional information:
draft-george-ipv6-support: IPv6 Support Within IETF work (None - )