The China Education and Research Network IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition
RFC 6219, “The China Education and Research Network IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition”, is an Informational document published in May 2011 by X. Li, C. Bao, M. Chen, H. Zhang, J. Wu. The canonical text is published by the RFC Editor.
Abstract
This document presents the China Education and Research Network (CERNET)'s IVI translation design and deployment for the IPv4/IPv6 coexistence and transition.
The IVI is a prefix-specific and stateless address mapping mechanism for "an IPv6 network to the IPv4 Internet" and "the IPv4 Internet to an IPv6 network" scenarios. In the IVI design, subsets of the ISP's IPv4 addresses are embedded in the ISP's IPv6 addresses, and the hosts using these IPv6 addresses can therefore communicate with the global IPv6 Internet directly and can communicate with the global IPv4 Internet via stateless translators. The communications can either be IPv6 initiated or IPv4 initiated. The IVI mechanism supports the end-to-end address transparency and incremental deployment. The IVI is an early design deployed in the CERNET as a reference for the IETF standard documents on IPv4/IPv6 stateless translation. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6219 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6218 Cisco Vendor-Specific RADIUS Attributes for the Delivery of Keying Material
- RFC 6220 Defining the Role and Function of IETF Protocol Parameter Registry Operators
- RFC 6217 Regional Broadcast Using an Atmospheric Link Layer
- RFC 6221 Lightweight DHCPv6 Relay Agent
- RFC 6216 Example Call Flows Using Session Initiation Protocol Security Mechanisms
- RFC 6222 Guidelines for Choosing RTP Control Protocol Canonical Names
- RFC 6215 MPLS Transport Profile User-to-Network and Network-to-Network Interfaces
- RFC 6223 Indication of Support for Keep-Alive