IPv6 in the Telco Cloud and 5G

Copyright Telstra©
IPv6 in the Wireless Telco
Cloud and 5G
APRICOT 2018 – February 2018
| Telstra Unrestricted | IPv6 in the Telco Cloud and 5G | Jeff Schmidt | 12/2017Page 1

Jeff Schmidt
Technology Team Manager, Telstra Wireless Network Engineering
jeff.schmidt@team.telstra.com
Technical Manager Supporting :
Wireless IPv6 deployment
Wireless Mobile Edge and Telco Cloud IP Architecture
Introduction

What does a IPv6 Mobile Network look like?
Where are we at with deployment?
What challenges lies ahead? Where else do we need to consider
IPv6?
Executive Summary

Copyright Telstra©
IPv6 for a Mobile Network

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
Why?

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

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

Copyright Telstra©
What have we achieved so far?

Most major content providers are providing IPv6 reachability
Some providers have mandated IPv6 support in their app stores
and all new apps must support native IPv6
Networks are evolving to support new IPv6 connections – SS or DS
Devices are beginning to support IPv6 natively
As native IPv6 is supported by more applications and devices the
reliance on 464xlat is reduced

IPv6 Global Traffic
Source - https://www.google.com/intl/en/ipv6/statistics.html

So what is there left to do?

Copyright Telstra©
Complexity in the network

Value Added Services or packet processing requires manual steps
today
Each path may require a unique VPN or PBR to define its path. As
additional services are added the complexity increases
exponentially.
InternetMobile Network
PGW
FW
Video
Optimizer
Parental
Control
BorderRouter

Virtualisation may reduce the
cost of such network functions,
but does not necessarily reduce
the network complexity
Each path may require a unique
VPN or PBR to define its path.
The more services, the more
convoluted this becomes.
Network Function Virtualization
vFW
vVideo
Optimizer
vParental
Control
vPGW
Internet ProviderMobile Network
PE
Leaf
BR
vCGN
Leaf
Spine Spine

Software-Defined Network means
many different things to many
people.
SDN is a way to simplify network
service chaining
1. Identify the user
2. Allocate a service chain to the
user according to their
subscription
3. Program the network to direct
the packets of this user to the
appropriate VNFs
SDN only solves one of many problem
vFW
vVideo
Optimizer
vParental
Control
vPGW
PE
Leaf
BR
vCGN
Leaf
Spine Spine
If Service A
then vFW
then vCGN
then Internet
If Service B
then vFW
then vParental Control
then vCGN
then Internet
If Service C
then vVideo Optimizer
then vParental Control
then vCGN
then Internet
Openflow
Switch

Lets dive deeper…

Underlay can be IPv4 only. But
why?
Can we do Point-to-Point /127 and
do away with IPv4 altogether?
Is VXLAN over EVPN the best
solution for a Telco Cloud? What
about service chaining?
This should all be contained within
a single AS. What routing protocol
is run between VTEPs?
If this is entirely IPv6, can we
leverage Segment Routing for
SDN control?
Underlay and Overlay
vFW
vVideo
Optimizer
vParental
Control
vPGW
PE
Leaf
BR
vCGN
Leaf
Spine Spine
SR?

Openstack is somewhat
ready for IPv6 – neutron
supports IPv6 subnets and
DHCPv6, as well as SLAAC
You can begin to onboard
tenants that can be IPv6
enabled.
Really there is only two
options – Dual-Stack
everything, or Conditional
Dual-Stack.
Openstack
API endpoints
Databases
Automation
Interfaces
IPv4/IPv6
IPv4/IPv6
IPv4/IPv6
IPv4/IPv6

Does not support the use of an external IPAM module for IPv6 to
allocate the subnet.
OVS tunnel types do not support IPv6 endpoints until OVS 2.6.0+
Single-stack IPv6 tenant networking not fully available.
VPN support not good until at least Kilo.
Openstack does not fully support IPv6

Is a NFV solution ready user plane functions in commodity compute
A hybrid solution of control plane running in NFV and user plane in
physical platforms is an option for now
Is CUPS a prerequisite to M CORD ?
Carrier Grade

Copyright Telstra©
Fog and Transport

5G requires super low latency
depending on the network slice
required and the application
behind it.
At some point, we must move the
cloud even closer to the user
Telco Cloud:
1. Service Functions in VNFs
2. Virtualised Packet Core Nodes
3. Media Cache
4. Value Added Services
Fog
Transit Provider Content Provider
MPLS Core
Internet
Aggregation
PE
BorderRouter
Roaming Gateway
CRAN
Telco
Cloud

IPv6 SS for transport layer ? (6PE)
SRIPv6 to replace traditional
MPLS?
6VPE required to ensure services
provided by different VPNs have
IPv6 support
Are there benefits using segment
routing ?
Transport
Transit Provider Content Provider
MPLS Core
Internet
Aggregation
PE
BorderRouter
Roaming Gateway
CRAN
Telco
Cloud

IPV6 Considerations
Similar to current Mobiles access technologies IPv6
deployments should focus on subscriber end points as this is
where pressure on address space exists
O&M networks can follow using dual stack with the eventual
removal of IPv4
IOT will require large scale corporate network solutions
Network slicing will increase pressure on infrastructure
addressing

Copyright Telstra©
Internet of Things
Telemetry is driving the development of purpose built wireless
devices with very large battery life and low cost devices
Systems allowing customers to control their own SIMs
Traditional corporate solutions allow reuse of address space so
may not be a focus to move to IPv6 but the scale of the
solutions will increase with IOT and some customers may
mandate IPv6 a requirement
The core will need to support a set of solutions to
accommodate customer requirements, some of those solutions
are not new.

Copyright Telstra©
Traditional Corporate Solutions
L2TP is not efficient or will it scale to support IOT
Private networks – opportunity for carriers
Customers can run IOT solutions over the Mobile Broad
Band product – with or without NAT
PGW as a MPLS PE could run corporate VPNs at scale
Fixed addressing is a challenge at scale which could be
resolved by maintaining state between PGWs

Copyright Telstra©
Network Slicing
Non Traditional Corporate Solutions
RRH
MBB Voice Mission Critical Massive IoT
RRH RRH RRH
PHY/MAC/RLC PHY/MAC/RLC PHY/MAC/RLC PHY/MAC/RLCCell
Site
MEC
vBBH vBBH vBBH vBBH
vEPC (UP) vEPC (UP)
Content Content
vEPC (CP) vEPC (CP) vEPC (CP) vEPC (CP)
vEPC (UP) vEPC (UP)
Content Content Content Content
Centralised
DC

The full removal of IPv4 private and public addressing from the
entire network.
Enable NAT translations for only what is necessary
IPv4aaS
What is our goal?

There is a long journey yet for IPv6, this is only the starting point

IPv6 in the Telco Cloud and 5G

More Related Content

What's hot

Similar to IPv6 in the Telco Cloud and 5G

More from APNIC

IPv6 in the Telco Cloud and 5G