Running Multiple PLATs in 464XLAT
draft-sun-v6ops-xlat-multi-02

Document Type Expired Internet-Draft (individual)
Last updated 2015-12-27 (latest revision 2015-06-25)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sun-v6ops-xlat-multi-02.txt

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 (sunqiong@ctbri.com.cn)
Zhirong Zhang (zhangzhr@ctbri.com.cn)
Qin Zhao (zhaoq@bupt.edu.cn)
Sheng Jiang (jiangsheng@huawei.com)
XiaoDong Lee (xl@cnnic.cn)
Yu Fu (fuyu@cnnic.cn)

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