6to4 Provider Managed Tunnels
RFC 6732, “6to4 Provider Managed Tunnels”, is a Historic document published in September 2012 by V. Kuarsingh, Y. Lee, O. Vautrin. It has been obsoleted by RFC 7526 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
6to4 Provider Managed Tunnels (6to4-PMT) provide a framework that can help manage 6to4 tunnels operating in an anycast configuration. The 6to4-PMT framework is intended to serve as an option for operators to help improve the experience of 6to4 operation when conditions of the network may provide sub-optimal performance or break normal 6to4 operation. 6to4-PMT supplies a stable provider prefix and forwarding environment by utilizing existing 6to4 relays with an added function of IPv6 Prefix Translation. This operation may be particularly important in NAT444 infrastructures where a customer endpoint may be assigned a non-RFC1918 address, thus breaking the return path for anycast-based 6to4 operation. 6to4-PMT has been successfully used in a production network, implemented as open source code, and implemented by a major routing vendor. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Historic” means
A specification that has been superseded or is otherwise no longer recommended for use.
The canonical text of RFC 6732 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6731 Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
- RFC 6733 Diameter Base Protocol
- RFC 6730 Requirements for IETF Nominations Committee Tools
- RFC 6734 Diameter Attribute-Value Pairs for Cryptographic Key Transport
- RFC 6729 Indicating Email Handling States in Trace Fields
- RFC 6735 Diameter Priority Attribute-Value Pairs
- RFC 6728 Configuration Data Model for the IP Flow Information Export and Packet Sampling Protocols
- RFC 6736 Diameter Network Address and Port Translation Control Application