datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status
draft-ietf-v6ops-natpt-to-historic-00

RFC
Document Stream: IETF
Last updated: 2007-02-21
Replaces: draft-ietf-v6ops-natpt-to-exprmntl
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (v6ops)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 4966
IANA Action State: No IC 
Responsible AD: David Kessens
Send notices to: v6ops-chairs@tools.ietf.org, ietf@energizeurnet.com, elwynd@dial.pipex.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-v6ops-natpt-to-historic.

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.

Authors:
Cedric Aoun <ietf@energizeurnet.com>
Elwyn Davies <elwynd@dial.pipex.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)