Brett Sheffield wrote:
If RIPE is serious about encouraging IPv6 adoption (and I think we are), we need to deprecate and remove support for IPv4.
The idea of deprecating and removing IPv4 support in order to "encourage" IPv6 adoption is both unrealistic and counterproductive. While IPv6 is a technically superior protocol and its widespread adoption is desirable, the fact remains that IPv4 continues to underpin a vast portion of the global Internet infrastructure. Forcing its removal would not accelerate IPv6 adoption - it would introduce massive disruption and incompatibility. Dual-stack deployments and transition technologies (such as NAT64, DNS64, and 464XLAT) are well-established and allow for a practical coexistence of both protocols. The Internet is a heterogeneous space, and many networks, especially in developing regions or small-scale operations, still rely heavily on IPv4. Moreover, critical systems, embedded devices, legacy applications, and even large-scale services continue to depend on IPv4-only implementations. Mandating IPv6-only operation would sever access to these resources and services. Adoption of IPv6 should be driven by technical and economic incentives, not by the threat of forced obsolescence. Removing support for IPv4 would not solve the adoption problem - it would merely punish those who, for valid reasons, cannot yet migrate. As a coordinating body, RIPE should focus on fostering compatibility, providing incentives, and supporting gradual transition rather than advocating for the removal of functional infrastructure. Deprecating IPv4 is not a path to progress - it is a recipe for fragmentation and exclusion. -- nemox.net Rudolf E. Steiner r.steiner@nemox.net http://nemox.net/pdat/res/