Deoknyong Ko New Connectivity TF Network Technology R&D Center SKtelecom

What’s the first things that pops into your mind when you hear the word, Korea?

Which country invented the Internet for the first time in the world ? for the first time in the world ? Which country was next ?

Which country invented the Mobile IPv6 Internet for the first time in the world ? for the first time in the world ? Which country was next ?

What’s the first things that pops into your mind when you hear the word, Korea?

※ The Market Share of Mobile Subscribers in Korea SKtelecom 50.5% KT LG U+ Wired Broadband Mobile PlatformSemiconductor

Background IPv6 Transition Schemes Contents FAQ

Background IPv6 Transition Schemes Contents FAQ

Korean Status in The Past France United States Japan Germany Romania

Korean Government’s Encourage Subject Company NetworksDate Operator SKtelecomOn Commercial' SKbroadbandOn Field Trial’ KTPreparing LGU+ On Commercial (Only Voice) Portal NaverPreparing DaumOn Commercial' NatePreparing

Summary of Applying IPv6 Subject Purpose Networks Transition Scheme Date Subscriber s Wired Field TrialHFC, G-PONDual Stack ’ thousand Wireless CommercialLTEOnly IPv6' thousands IPv4 Networks Dual Stack (IPv4/IPv6) Only IPv6 Networks IPv4 Networks ※ Subscribers by Jan Only IPv6 Networks

Why Did SKT Decide to Adopt IPv6 ?

Why Did SKT Decide to Adopt IPv6 ? CapEx for NAT equipment ※ Reference: ∙ LTE device has 2 different IPv4 addresses by default in SKT. ∙ The number of connected device could exponentially increase.

Difficult to operate duplicated networks Why Did SKT Decide to Adopt IPv6 ?

Korean government’s encouragement Why Did SKT Decide to Adopt IPv6 ? ※ The statistics of IPv6 users. ( United States Norway Germany Belgium

Which Networks to be migrated IPv6? Applying IPv6 to only primary networks. Legacy network will be replaced to LTE or G-PON. Subject NetworksApplying IPv6Note Wireless LTEOCommercial WCDMAX Wi-FiX Wired G-PONOField Trial HFCX xDLSX

Contents Background IPv6 Transition Schemes FAQ

Summary of IPv6 Transition Schemes Subject Transition Schemes BackboneDual Stack Access Networks (LTE EPC) NAT64, 464XLAT

Transition Scheme for Backbone Dual stack can support both IPv4 and IPv6 access networks. There is no issue. We don’t even need to apply Only-IPv6 to the backbone.

Case#1: IPv6 is enabled on contents server (End-to-End IPv6 connectivity) Transition Scheme for Access Network Case#2: IPv6 is not enabled on contents servers

Case#1: IPv6 is enabled on contents server (End-to-End IPv6 connectivity) Transition Scheme for Access Network (contd)

Case#2: IPv6 is not enabled on contents servers SKT should support that only-IPv6 subscribers can connect to only-IPv4 contents server. NAT64, DNS64

Algorithm of NAT64, DNS64 ① Customer tries to connect to ② LTE device asks DNS64 server what is an IP address of ③ DNS64 server responds ‘64:ff9b:: ④ LTE device tries to connect to ‘64:ff9b:: ⑤ NAT64 translate IPv6 packet to IPv4 packet

Drawback of NAT64 Algorithm Some applications are Hard Coded as only IPv4 address instead of domain name. ∙ IPv6 LTE device doesn’t ask DNS64 server. ∙ Only IPv6 LTE device can’t interpret an IPv4 address. Error occurred !!

464XLAT Overview RFC 6877, “464XLAT: Combination of stateful and stateless translation” (Information Track) Provided by Android OS by default T-Mobile USA and SKT adopted

464XLAT Architecture 464XLAT has two operations, CLAT and PLAT Subject CLATPLAT Full NameCustomer-side translatorProvider-side translator LocationIn cellphoneIn operator’s network TranslationIPv4  IPv6IPv6  IPv4

464XLAT Operation Subject Interface Source Address Data Packet LTE Data Original Allocated from P-GW (e.g. 2001:290::1) CLAT “ ” (dummy IPv4 address) “LTE data interface ::464” (e.g. 2001:290::464) Voice Packet LTE IMSAllocated from P-GW (e.g. 2001:2b8::1) LTE device has 3 outgoing interfaces

464XLAT Operation (contd) If android OS find a hard coded for IPv4 address( ), android OS will transfer packet via CLAT interface. CLAT PLAT ( ) PLAT ( ) Content Server ( ) Content Server ( ) Src: Dest: Src: Dest: Src: 2001:290::464 Dest: 64:ff9b:: Src: 2001:290::464 Dest: 64:ff9b:: Src: 2001:290::464 Dest: 64:ff9b:: Src: 2001:290::464 Dest: 64:ff9b:: Src: Dest: Src: Dest: Src: Dest: Src: Dest:

Verify 464XLAT Schemes Verified 15 hundreds applications while preparing the commercial service. A few applications have trouble due to customer’s circumstance.

Background IPv6 Transition Schemes Contents FAQ

Which handset OSs and models are supported an IPv6 service? ∙ We applied to only android OS not iOS. ∙ We applied to Galaxy Note 4 first. (‘ ) ∙ We have applied to all new devices including tablet since then.

Do you support IMS service(VoLTE) also? ∙ Of course. ∙ We support an IPv6 service of LTE Data and LTE Voice.

Do you support international roaming service? ∙ Not yet. ∙ We don’t have a plan to launch now. Do you support Wi-Fi service?

Do you support tethering service? ∙ Yes. ∙ LTE device allocates an IPv4 address not IPv6 address to laptop.

Do you satisfy the quality of IPv6 data and IMS service compared to IPv4 ? ∙ Yes. ∙ We can’t find the quality difference between IPv4 and IPv6 service.

Can I know about the increase of IPv6 users and IP deployment since commercial service ? ∙ I’m sorry but, I can’t inform that. ∙ IPv6 users and the CapEx for IP deployment are restricted document.

Can I know about the increase of IPv6 traffic since commercial service ? ∙ Recent IP equipment(ex> Router, P-GW) can’t distinguish between IPv4 traffic and IPv6 traffic.

Do you inform your customers that they are serviced by IPv6 ? ∙ No. ∙ Our aim is that our customer can’t recognize which service is provided.

How to utilize the collected Public IPv4 addresses ? ∙ Private IPv4 addresses were used to VoLTE Service. ∙ We are currently allocating Public IPv4 addresses to VoLTE service to raise voice quality.

Do you have a plan to launch the new BM based on IPv6 ? ∙ Yes. ∙ We are developing the cellular based IoT Service (ex> MTC, NB CIoT).