Running Multiple PLATs in 464XLAT
draft-sun-v6ops-xlat-multi-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Qiong Sun , Zhirong Zhang , Qin Zhao , Sheng Jiang , XiaoDong Lee , Yu Fu | ||
| Last updated | 2015-12-27 (Latest revision 2015-06-25) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
The IPv6 transition has been an ongoing process throughout the world due to the exhaustion of the IPv4 address space. The 464XLAT [RFC6877] provides a solution with limited IPv4 connectivity across an IPv6-only network, and the android system (version 2.3 and above) has already implemented the 464XLAT and the Prefix discovery solution [RFC7050]. However, the current 464XLAT architecture can only deal with the scenario with single PLAT in the network. When operator deploys multiple PLATs with different Pref64 prefixes, 464XLAT cannot cope with multiple prefixes for different destination addresses. This document describes the architecture with multiple PLATs and also the deployment considerations.
Authors
Qiong Sun
Zhirong Zhang
Qin Zhao
Sheng Jiang
XiaoDong Lee
Yu Fu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)