<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sun-v6ops-xlat-multi" target="https://datatracker.ietf.org/doc/html/draft-sun-v6ops-xlat-multi-02">
   <front>
      <title>Running Multiple PLATs in 464XLAT</title>
      <author initials="Q." surname="Sun" fullname="Qiong Sun">
         <organization>China Telecom</organization>
      </author>
      <author initials="Z." surname="Zhang" fullname="Zhirong Zhang">
         <organization>China Telecom</organization>
      </author>
      <author initials="Q." surname="Zhao" fullname="Qin Zhao">
         <organization>Beijing University of Posts and Telecommunications</organization>
      </author>
      <author initials="S." surname="Jiang" fullname="Sheng Jiang">
         <organization>Huawei Technologies Co., Ltd</organization>
      </author>
      <author initials="X." surname="Lee" fullname="XiaoDong Lee">
         <organization>CNNIC</organization>
      </author>
      <author initials="Y." surname="Fu" fullname="Yu Fu">
         <organization>CNNIC</organization>
      </author>
      <date month="June" day="25" year="2015" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sun-v6ops-xlat-multi-02" />
   
</reference>
