Reasons to Move the Network Address Translator - Protocol Translator to Historic Status
RFC 4966, “Reasons to Move the Network Address Translator - Protocol Translator to Historic Status”, is an Informational document published in July 2007 by C. Aoun, E. Davies. It obsoletes RFC 2766. The canonical text is published by the RFC Editor.
Abstract
This document discusses issues with the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766. These issues are sufficiently serious that recommending RFC 2766 as a general purpose transition mechanism is no longer desirable, and this document recommends that the IETF should reclassify RFC 2766 from Proposed Standard to Historic status. This memo provides information for the Internet community.
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 4966 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4965 CableLabs - IETF Standardization Collaboration
- RFC 4967 Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier
- RFC 4964 The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular
- RFC 4968 Analysis of IPv6 Link Models for 802.16 Based Networks
- RFC 4963 IPv4 Reassembly Errors at High Data Rates
- RFC 4969 IANA Registration for vCard Enumservice
- RFC 4962 Guidance for Authentication, Authorization, and Accounting Key Management
- RFC 4970 Extensions to OSPF for Advertising Optional Router Capabilities