NAT64/464XLAT Deployment Guidelines in Operator and Enterprise Networks
draft-palet-v6ops-nat64-deployment-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jordi Palet Martinez | ||
| Last updated | 2018-06-26 | ||
| Replaced by | draft-ietf-v6ops-nat64-deployment | ||
| 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-nat64-deployment | |
| 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 describes how NAT64 and 464XLAT can be deployed in an IPv6 operator (cellular and broadband) or enterprise network and the issues to be considered when having an IPv6-only access link, regarding: a) DNS64, b) applications or devices that use literal IPv4 addresses or non-IPv6 compliant APIs, and c) IPv4-only hosts or applications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)