464XLAT/MAT-T Optimization
draft-ietf-v6ops-464xlat-optimization-04
| Document | Type |
Expired Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jordi Palet Martinez , Alejandro D'Egidio | ||
| Last updated | 2023-09-14 (Latest revision 2023-03-13) | ||
| Replaces | draft-palet-v6ops-464xlat-opt-cdn-caches | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Jen Linkova | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | Jen Linkova <furry@google.com>, Jen Linkova <furry13@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IP/ICMP Translation Algorithm (SIIT) can be used to provide access for IPv4-only hosts or applications to IPv4-only or dual-stack destinations over IPv6-only infrastructure. In that case, the traffic flows are translated twice: first from IPv4 to IPv6 (stateless NAT46 at the ingress point to the IPv6-only infrastructure) and then from IPv6 back to IPv4 (stateful NAT64, at the egress point). When the destination is IPv6-enabled, the second translation might be avoided. This document describes a possible optimization to 464XLAT and MAP-T to avoid translating IPv6 flows back to IPv4 if the destination is reachable over IPv6. The proposed solution would significantly reduce the NAT64 utilization in the operator's network, increasing the performance.
Authors
Jordi Palet Martinez
Alejandro D'Egidio
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)