1 / 5

NAT64 Operational Considerations draft-chen-v6ops-nat64-cpe-03.txt IETF 82- Taipei, Nov 2011

NAT64 Operational Considerations draft-chen-v6ops-nat64-cpe-03.txt IETF 82- Taipei, Nov 2011. Gang Chen ( chengang@chinamobile.com ) Qibo Niu( niu.qibo@zte.com.cn ). Changes since IETF#81 (-02 to -03).

thelma
Download Presentation

NAT64 Operational Considerations draft-chen-v6ops-nat64-cpe-03.txt IETF 82- Taipei, Nov 2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NAT64 Operational Considerationsdraft-chen-v6ops-nat64-cpe-03.txtIETF 82- Taipei, Nov 2011 Gang Chen (chengang@chinamobile.com) Qibo Niu(niu.qibo@zte.com.cn)

  2. Changes since IETF#81 (-02 to -03) • Added different deployment considerations regarding the different positions of NAT64, which is focusing “An IPv6 Network to the IPv4 Internet: NAT64-CGN” and “The IPv6 Internet to an IPv4 Network: NAT64-CE” • Aligned with RFC6144

  3. Considerations for NAT64-CGN deployment PC DNS DNS64 HG ONU/SW OLT/SW BRAS NAT64 IPv4 Server PPPoEv6/IPoEv6 SLAAC/DHCPv6 DNS query(AAAA) DNS query(AAAA/A) DNS Response(synthesized AAAA) DNS Response (A) IPv6 Network IPv4 Internet • Implementation: Standalone CGN VS Embedded CGN (BNG, Aggregation Router or PGW) • CGN location: centralized deployment VS distributed deployment; • Performance: Traffic throughout, concurrent sessions and session rate of IDC CGN and Internet CGN is related with WEB traffic and Subscriber scale respectively, • Reliability: NAT64 session + Filter/Mapping mode should be synchronized between Master and backup CGN • Service Richness: FTP, SIP, DNS64, RSTP, H.323, SCCP, PPTP and so on; • Security: Lawful interception (ETSI CC IIF) and user traceability for Legal Entity; TCP tracking, uRPF, blacklist and Mapping/Filter mode for CGN security; • Other requirements: Load Balancer, PCP server and subscriber policy (similar to BNG)

  4. Considerations for NAT64-CE deployment NAT64-CE PC IPv6 Internet PC Residential Network Enterprise Network NAT64-CE IPv4 Network IPv6 Internet • Implementation: Embedded NAT64 functionalities • NAT64 location: Co-located with enterprise gateway or home gateway • Performance: NAT64 are serving for relatively small scale of customers • DNS resolving: static AAAA records can be added directly in authoritative DNS • Service Richness: VPN, P2P, Web (Office automation), FTP • Reliability: Standalone NAT64 deployment • Security: IPsec VPN may need to be deployed to prevent privacy invasion • Other requirements: PCP proxy functionalities

  5. Next steps • Future works • Add justification for NAT64 deployment considerations • Make detailed comparison for different cases • Adopt?

More Related