@techreport{sun-v6ops-xlat-multi-02,
    number =    {draft-sun-v6ops-xlat-multi-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sun-v6ops-xlat-multi/02/},
    author =    {Qiong Sun and Zhirong Zhang and Qin Zhao and Sheng Jiang and XiaoDong Lee and Yu Fu},
    title =     {{Running Multiple PLATs in 464XLAT}},
    pagetotal = 8,
    year =      2015,
    month =     jun,
    day =       25,
    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.},
}