Reasons to Deprecate NAT-PT
draft-aoun-v6ops-natpt-deprecate-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Cedric Aoun | ||
| Last updated | 2005-03-01 (Latest revision 2004-09-21) | ||
| Replaced by | draft-ietf-v6ops-natpt-to-exprmntl | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-natpt-to-exprmntl | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses reasons why use of the specific form of IPv6-IPv4 protocol translation mechanism implemented by the Network Address Translator - Protocol Translator (NAT-PT) defined in RFC 2766 should be deprecated and RFC2766 moved to historic status. Description of an alternative protocol translation mechanism is out of scope for this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)