1. IETF 79 th Considerations for Stateless Translation (IVI/dIVI) in Large SP draft-sunq-v6ops-ivi-sp-01 Qiong Sun( China Telecom) Heyu Wang( China Telecom) Xing Li( Tsinghua University) Congxiao Bao( Tsinghua University) Ming Feng( China Telecom)

2. IETF 79 th IPv6 Transition Overview IPv6 deployment is a huge systematic project and there is no single solution which can solve all the problems. We mainly focus on IVI/dIVI in this document and explore the way to deploy it in SP network. Dual-Stack : NAT444, CGN Tunneling : DS-Lite/GI-DS-Lite, A+P, SAM, etc. Translation : IVI/dIVI, NAT64, DNS64, FTP64, etc.

3. IETF 79 th Major Requirements for IPv6 transition The pool of public IPv4 addressing is nearing its exhaustion. Basic requirements in IPv6 transition – Reduce IPv4 address consumption – Accelerate the deployment of IPv6 – No perceived degradation of customer experience – Achieve scalability, simplicity and high availability Operational requirements in IPv6 transition – Incremental deployment – Integrated address assignment and user authentication – User management and network management – Traceability for the origin of IPv6 traffic

4. IETF 79 th Features of dIVI dIVI is an extension of stateless translation (IVI), which enables – Sharing public IPv4 addresses among several IPv6 end systems – Support bidirectional initiated communications – No requirements for ALG – No requirements for DNS64 The figure is from proceedings of ietf76

5. IETF 79 th Laboratory Experiment IVI6= XXXX:XXXX:XXXX::/48 IPv6/48 IVI4= XXX.XXX.XXX.XXX/30 IPv4/24 Ratio= 128(512 available ports per user) Host Non-IVI6= YYYY:YYYY:YYYY::/48 IPv6/48 DNS R1 R3 R5 R4 IPv6 network IPv4 Internet R2 IPv6 Internet 1:N IVI H 1.0 H 1.1 H 1.2 Hgw 1.0 Hgw 1.1 Hgw 1.2 S

6. IETF 79 th Experimental Results TypeExperimental Result Application testdIVI hosts can widely support Web, Email, IM, FTP, telnet, SSH, video, Video Camera, P2P, online game, voip, etc. Operating System test dIVI can support Win7, VISTA, windows XP, etc. Performance testThe performance test for dIVI Xlate is carried out on a normal PC. Due to limitation of the PC hardware, the overall throughput is not quite good. However, it can still support more than one hundred million concurrent sessions. From the experiment, we can have the following conclusions: – dIVI can have good scalability and it can be deployed in an incremental way – dIVI can support a majority of current IPv4 applications – dIVI can support a variety of Operating Systems – Port restriction will not have evident impact on user experience with reasonable port configuration.

7. IETF 79 th dIVI Deployment Scenarios in SP(1) IPv4 Server Metro Network (IPv6) Backbone (IPv4) BRAS/SR CR Access Network (IPv6) 1:N IVI IPv4-only user Hgw 1.0 IPv6 traffic IPv4 traffic

8. IETF 79 th dIVI Deployment Scenarios in SP(2) Metro Network (IPv6) Backbone (IPv4) Backbone (IPv6) BRAS/SR CR Dual-stack user Access Network (IPv6) 1:N IVI Hgw 2.0 IPv6 traffic IPv4 traffic IPv4 Server IPv6 Server

9. IETF 79 th Deployment Considerations Basic configuration in commercial SP network Addressing – IPv6 address: No need to allocate IVI6 address explicitly. – IPv4 address: Hgw needs to get IVI4 address and reallocate it to end user. Routing – IVI4(i) and IVI6(i) will be aggregated to ISP’s IPv4 and ISP’s IPv6 address. – IVI6(i): Hgw  1:N IVI Xlate IVI4(i): 1:N IVI Xlate  Internet – Automatic announcement via dynamic routing protocols DNS – No DNS64/DNS46 needed in dIVI. – Implement IPv4-to-IPv6 DNS Proxy

10. IETF 79 th Deployment Considerations Operational considerations in commercial SP network AAA and User Management – support the identification of IPv6-only/dIVI subscriber in AAA Network management – Manage IPv6-only network, including IPv6 MIB modules, Netflow, etc. – Manage the translation process, including dIVI device management, dIVI traffic monitoring, etc. CPE Requirements and Configuration – Address assignment: support IVI4 address assignment – Integrated user authentication function – DNS configuration: support IPv4-to-IPv6 DNS proxy

11. IETF 79 th Deployment Considerations Operational considerations in commercial SP network dIVI Xlate Placement – Centralized Model It can be deployed in the place of Core Router, or in the entrance of ICP. It can reduce cost, be easier for management, fit for stateless solution. – Distributed model It can be integrated with BRAS/SR. MAN has to support dual-stack, and so decreased operational cost is rather limited. ALG consideration – dIVI does not require ALG.

12. IETF 79 th Conclusion dIVI is one of the IPv6 transition solutions which can meet the majority of IPv6 transition requirements. In order to deploy transition techniques in commercial network, special attention should be paid to operational issues in SP network. Most of the operational issues are not specific to dIVI, but rather to a general requirement on all IPv6 transition techniques. We highly recommend that manufactures should take the corresponding extensions for IPv6 transition.

13. IETF 79 th Next Steps Take further trial in commercial network Comments and contributions are welcome – http://tools.ietf.org/html/draft-sunq-v6ops-ivi-sp-01 http://tools.ietf.org/html/draft-sunq-v6ops-ivi-sp-01

14. IETF 79 th Thank You!

15. IETF 79 th dIVI References dIVI is an extension of stateless translation (IVI) – https://datatracker.ietf.org/doc/rfc6052/ https://datatracker.ietf.org/doc/rfc6052/ – https://datatracker.ietf.org/doc/draft-ietf-behave-v6v4- xlate/ https://datatracker.ietf.org/doc/draft-ietf-behave-v6v4- xlate/ – https://datatracker.ietf.org/doc/draft-bcx-address-fmt- extension/ https://datatracker.ietf.org/doc/draft-bcx-address-fmt- extension/ dIVI references can be found in – http://tools.ietf.org/html/draft-xli-behave-divi-01 http://tools.ietf.org/html/draft-xli-behave-divi-01 – http://www.ietf.org/proceedings/76/slides/behave-10.pdf http://www.ietf.org/proceedings/76/slides/behave-10.pdf