1. Running Multiple PLATs in 464XLAT1
Running Multiple PLATs in 464XLAT
draft-sun-v6ops-xlat-multi-00
Qiong Sun, Zhirong Zhang, Qin Zhao
Presenter: Chongfeng Xie
IETF 1 1

2. 2
Introduction
The 464XLAT is an mechanism enabling IPv4 service reachable across IPv6-only networks. However, it can only be used for one-PLAT situation.
In section 6.3 [RFC6877], the CLAT will use the PLAT-side translation IPv6 prefix as the destination of all translation packets that require stateful translation to the IPv4 Internet.
The Prefix Discovery method [RFC7050] cannot deal with the scenario when different PLATs are using with different Pref64 prefixes.
This draft describes the 464XLAT architecture with multiple PLATs by combining with the existing solutions.
2/9 Pages

3. Motivation of Multi-PLATs
Different PLATs may serve for different purposes, with distinguish ALG implementation, QoS treatment,etc.
Deploy multiple PLATs is for load balancing

4. Multi-PLATs Architecture
Prefix Management Server
PLAT1
Network1
Enhanced CLAT
Routing protocols only focus is reachability.
There are dependencies between such information and configurations.
More information, such as latency, congestion, capacity, and particularly available throughput.
More dimensions of the network, such as power saving, load balancing, etc.
PLAT2
Network2
4/9 Pages

5. Enhanced CLAT for Multi-PLATs
Prefix discovery agent: It may implement PCP based prefix discovery method [RFC7225] to allocate multiple Pref64 prefixes.
Pref64 management: Extract the Pref64 from the prefix discovery procedure and manage multiple Pref64 prefixes.
v4addrRange Management: store the corresponding IPv4 address ranges and chose the desired pref64 for each packet.
For example, it may map specific IPv4 destination address ranges to separate Pref64 prefixes, or map specific IPv6 source address ranges to separate Pref64 prefixes, or map both destination IPv4 address and source IPv6 address to Pref64 prefixes. The policy in Prefix Management Server should be consistent with PLAT deployment policy.
5/9 Pages

6. Prefix Management Server
Policy Configuration: the policy to allocate multiple Pref64s.
Prefix discovery agent: It may implement PCP based prefix discovery method [RFC7225] to allocate multiple Pref64 prefixes.
Pref64/IPv4Pref management: Manage multiple Pref64 prefixes and their corresponding IPv4 prefix.
For example, it may map specific IPv4 destination address ranges to separate Pref64 prefixes, or map specific IPv6 source address ranges to separate Pref64 prefixes, or map both destination IPv4 address and source IPv6 address to Pref64 prefixes. The policy in Prefix Management Server should be consistent with PLAT deployment policy.
6/9 Pages

7. Deployment Consideration
The CLAT need to compare the destination address range with each packet it might have effect on the performance efficiency in the client.
Operators should limit the number of address ranges, and aggregate the addresses into a larger address range.
There should be a maximum limit in CLAT on the number of Pref64 prefixes.
When DNS64 is used to enable stateful translation, the multi-prefix policy should be consistent with the Prefix Management Server.
For example, it may map specific IPv4 destination address ranges to separate Pref64 prefixes, or map specific IPv6 source address ranges to separate Pref64 prefixes, or map both destination IPv4 address and source IPv6 address to Pref64 prefixes. The policy in Prefix Management Server should be consistent with PLAT deployment policy.
7/9 Pages

8. Demo System of Multi-PLATs
For example, it may map specific IPv4 destination address ranges to separate Pref64 prefixes, or map specific IPv6 source address ranges to separate Pref64 prefixes, or map both destination IPv4 address and source IPv6 address to Pref64 prefixes. The policy in Prefix Management Server should be consistent with PLAT deployment policy.
8/9 Pages

9. Questions? Discussion? Next Step ? Thanks!
9/9 Pages