Journey to IPv6 A Real-World deployment for Mobiles

Transcription

1 Journey to IPv6 A Real-World deployment for Mobiles APRICOT 2017 February 2017 Telstra Unrestricted Copyright Telstra

2 Introduction Instructional Slide Jeff Schmidt- Technology Team Manager, Telstra Wireless Network Engineering Managing the Technical Lead for Wireless IPv6 deployment and Wireless Mobile IP Edge/Core Architecture

3 Agenda 1. Why IPv6? 2. Business and Technical considerations 3. Network Architectures 4. Addressing and Subnetting 5. Deployment Model 6. Our Experience 7. Q&A

4 Why IPv6?

5 Why IPv6? Traffic growth and device per person Network readiness for new technologies: Internet-of-Things VoLTE/IMS ViLTE Management and Backhaul IPv4 public/private address depletion Reduction in network inefficiencies

6 IPv6 Global Traffic Source -

7 Business and Technical Considerations

8 Business and Technical Considerations Depleting public and private IPv4 address range

9 Business and Technical Considerations Non-interworking private IPv4 address ranges duplicated between domains, that now require interworking

10 Business and Technical Considerations $ NAT Continual investment to extend IPv4 resources vs IPv6 to future proof our network or $ IoT

11 Business and Technical Considerations As IPv4 addresses deplete, it will be more expensive to extend IPv4 resources Dual-Stack is an effective transition technology but does not solve the IPv4 depletion problem Introducing IPv6: - Reduced dependency on NAT - Remove the need for regionalisation - Pushes applications to move to IPv6

12 Network Architectures

13 IPv6 Implementation Centralised CGN NAT/PAT 44 Private IPv4 to Public IPv4 Backhaul Internet EPG CGNAT BR Region 1 Region 2 IP Core / Edge Backhaul Internet EPG CGNAT BR NAT/PAT 64 Public IPv6 to Public IPv4 CGN performs NAT/PAT 44 and NAT/PAT 64 PAT substantially reduces Public and Private IPv4 address demand, but does not prevent IPv4 address depletion.

14 IPv6 Implementation Traffic Flow IPv6 NAT64 Public IPv6 to Public IPv4 IPv4 Public Internet Radio Network (IPv4 transport) EPG Carrier Network (IPv4 + IPv6) IBR IPv6 Public Internet Single Bearer IPv6 only user plane Native IPv6

15 Running multiple APNs IPv6 APN DNS64 IPv6 Radio Network IPv4v6 APN Carrier Network Internet IPv4v6 enodeb IPv4 APN IBR NAT44 / NAT64 DNS-DS IPv4 GGSN/EPG Create multiple real APNs that supports IPv4, IPv6, and IPv4v6 individually

16 Running a Single APN IPv6 Radio Network IPv4v6 APN Carrier Network Internet IPv4v6 enodeb IBR NAT44 / NAT64 DNS-DS IPv4 GGSN/EPG Create a single real APN that supports both DS and SS

17 IPv6 Implementation Security NAT44/64 Translation Stateful firewall Untrust to Trust Block all traffic originating from internet Trust to Untrust Allow all traffic IPv6 IPv4 Public Internet Radio Network (IPv4 transport) EPG Carrier Network (IPv4 + IPv6) CGNAT BR IPv6 Public Internet Firewall Application APN ACL Advertise only handset ranges to Carrier Network Block traffic with IP ranges not configured on the EPG IPv6 Native Stateful firewall Untrust to Trust Block all traffic originating from Internet Trust to Untrust Allow all traffic originating from IPv6 handset ranges only Allow DNS traffic Block all infrastructure ranges Block all VoLTE ranges

18 Infrastructure Cloud IPv6 Core Network MPLS Internet Provider PE BR DC Gateway L3 Fabric EVPN ToR vcgn vepc

19 How much traffic will use IPv6?

20 464XLAT Architecture for Mobiles IPv6 Internet User Equipment / Mobile Phone 2001:db8:ca7e::d007 IPv6 IPv4 CLAT Function CLAT> IPv4 host address for XLATE (clat4) [ /32] IPv6 host address for XLATE [2001:db8:aaaa::464/128 PLAT-Side XLATE IPv6 Prefix [2001:db8:bbbb::/96] Carrier Core PLAT (NAT64) PLAT> IPv4 pool [ ] PLAT-Side XLATE IPv6 Prefix [2001:db8:bbbb::/96] IPv4 Internet IPv4 SRC IPv4 DST Stateless NAT64 [RFC6145] IPv6 SRC 2001:db8:aaaa::464 IPv6 DST 2001:db8:bbbb:: Stateful NAT64 [RFC6146] IPv4 SRC IPv4 DST

21 Addressing and Subnetting

22 Addressing and Subnetting 3GPP currently dictates each UE to receive a /64 Future releases may require a /60 with DHCP-PD for single APN tethering 4x /44 per APN per EPG = 4M prefixes You will probably also need a similar range for VoLTE APNs KEY: make sure it is a structured subnetting schema so it is consistent nationally and across the entire organisation.

23 Addressing and Subnetting Infrastructure Addressing: /64 per VLAN Keep it simple! Private or Public but remember to use a firewall and policies to avoid advertising the infrastructure out to the internet! NAT is not a security feature!

24 Deployment Model

25 Carrier Examples SP1 SP2 / SP3 SP4 Dual-Stack SS+NAT64+DNS64+CLAT SS/DS+NAT64+DNS-HD+CLAT 1. Every carrier will have a unique set of circumstances that dictates which transition method they will use. There is no standard way of doing this. 2. You must determine which is the best method for your network. In any method, remember to ensure you have a long-term strategy for the eventual deployment of native Single Stack IPv6!

26 Different APNs for different purposes Two existing APNs one for Handsets, one for Mobile Broadband and Tethering 464XLAT Telstra.WAP NAT64/ DNS64 Internet or Telstra.Internet DNS-DS/ NAT44 Internet 464XLAT + NAT64 + DNS64 for the Handset APN only IPv6 enabled DNS for all other APNs

27 Packet Core Configuration HSS Configuration PDP Context id = IPv4v6 MME Configuration DAF = set EPG Configuration PDPTYPE = IPv4v6 EPG will then also have the following as a minimum within each APN: -IPv6 Handset Range -IPv4 Handset Range -2x IPv4 DNS Name Servers, 2x IPv6 DNS Name Servers

28 UE Requirements and Settings Android 4.3+ supports 464XLAT. We recommend using anything that is or 5.1+ Depending on your setup, either PDP selection is based on the UE or the Network. International Roaming over IPv6 works today! But we recommend the APN Roaming Protocol to be set to IPv4 only for the next two years.

29 Launch Considerations Informed Front of House and provided training, as well as Enterprise support and sales personnel Updated internal Knowledge Base Briefed Operations and provided training Created moderated forum with official details on the network change Provided direct contact to Telstra Engineering Contacted the technical community via mailing lists and public forums before launch

30 Our Experience

31 Our Experience ipad Dual-Stack Carrier Settings Significant IPv6 takeup on ipads since carrier update was made available with Dual-Stack. Update made via ios patch. Users are not immediately aware IPv6 is available on their ipads. Transparent migration. IPv6 take up occurs when ipads are patched to the latest version Single Stack will come later this year

32 Our Experience telstra.wap - IPv6 Usage 01/07/16 01/08/16 01/09/16 01/10/16 01/11/16 NSW QLD SA VIC WA Total 01/12/16 01/01/17

33 BYO device and existing services APN IPv4v6, HLR/HSS IPv4v6 Legacy devices configured with IPv4 only are not impacted New devices configured with IPv4v6 obtains both addresses and is currently growing significantly Existing devices configured with IPv6 only obtains IPv6 only CGNAT NAT64 ALGs: ftp, sip, pptp, rtsp, h323

34 IPv4 vs IPv6 Some applications fail with IPv6 even with 464XLAT. Routing issues? VPNs are a real problem but is it a carrier problem or an application / server problem? HTTP / HTTPS works very well SSH is not a major problem IPv6 is faster in some cases smaller BGP table, no NAT etc. Major apps work very well especially from the major content providers

35 Customer Support Engage the community early so they know what s coming. They will appreciate you are still developing and they will want to be part of the journey! We receive support through our contact points and reply as soon as possible. Don t keep your customers waiting Skip the red tape let customers engage engineering directly Keep management happy! Report SIO and bandwidth usage!

36 Q&A

37 CONTACT

38 Contact Jeff Schmidt Technology Team Manager Telstra Wireless Network Engineering Sunny Yeung Senior Technology Specialist Telstra Wireless Network Engineering