Public IPv4-over-IPv6 Access Network
RFC 7040, “Public IPv4-over-IPv6 Access Network”, is an Informational document published in November 2013 by Y. Cui, J. Wu, P. Wu, O. Vautrin, Y. Lee. The canonical text is published by the RFC Editor.
Abstract
This document describes a mechanism called Public 4over6, which is designed to provide IPv4 Internet connectivity over an IPv6 access network using global IPv4 addresses. Public 4over6 was developed in the IETF and is in use in some existing deployments but is not recommended for new deployments. Future deployments of similar scenarios should use Lightweight 4over6. Public 4over6 follows the Hub and Spoke softwire model and uses an IPv4-in-IPv6 tunnel to forward IPv4 packets over an IPv6 access network. The bidirectionality of the IPv4 communication is achieved by explicitly allocating global non-shared IPv4 addresses to end users and by maintaining IPv4-IPv6 address binding on the border relay. Public 4over6 aims to provide uninterrupted IPv4 services to users, like Internet Content Providers (ICPs), etc., while an operator makes the access network transition to an IPv6-only access network.
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 7040 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7039 Source Address Validation Improvement Framework
- RFC 7041 Extensions to the Virtual Private LAN Service Provider Edge Model for Provider Backbone Bridging
- RFC 7038 Use of OSPF-MDR in Single-Hop Broadcast Networks
- RFC 7042 IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters
- RFC 7037 RADIUS Option for the DHCPv6 Relay Agent
- RFC 7043 Resource Records for EUI-48 and EUI-64 Addresses in the DNS
- RFC 7036 Object Identifier Registry for the Long-Term Archive and Notary Services Working Group
- RFC 7035 Relative Location Representation