An Architecture View of Softbank

Transcription

1 An Architecture View of Softbank to IPv6 transition and packet transport for Mobile and Broadband Satoru Matsushima Softbank Telecom Softbank BB Softbank Mobile

2 Introduction

3 Introduction In the transition state from to IPv6, we should consider We cannot assign new global addresses for new subscribers The network (particularly access NW) may have only capabilities or only IPv6 capabilities There are many deployment solutions for such cases IPv6 over, over IPv6 and Protocol Translation, etc., Requirements of each network provider are different depending on various factors, so appropriate solutions are also different For existing user or new user? For existing infrastructure or newly deployed infrastructure? For only network or IPv6 only network? This presentation shows our case study for the transition at Yahoo! Broadband (Y!BB) which is one of largest ISPs in Japan 2

4 IPv6 for Everybody! For all of broadband customer in Japan, BBIX provides 6rd and native IPv6 service to other ISPs For Everybody! IPv6 Internet Softbank Group s ISP ISP ISP ISP ISP 6rd Native IPv6 Y!BB Existing Access CATV Other Access Existing FTTH New FTTH Access Customer 3

5 Softbank IP Network Broadband Mobile Existing New (IPv6) (Global) (Private) 4

6 Existing vs New networks We built it by ourselves, leasing L0/1 infrastructure (DF, Copper line, CO site) NTT s CO-site Our Router NTT s Router Y!BB s Nationwide backbone ADSL Access network DSLAM CPE FTTH Access network PON CPE NTT East/West built it, and we are leasing L2/L3 connectivity 5

7 Existing Broadband network Broadband Mobile Existing New (IPv6) (Global ) (Privat e) 6

8 Conditions and requirements in existing access network Existing subscribers already have global addresses and the # of subscribers is slightly decreasing We don t need to consider how to provide connectivity Just using global address is enough Existing access network is only network Replacing or upgrading all devices to enable IPv6 is not realistic We will need 6 over 4 technology to provide IPv6 connectivity Since we are providing CPEs, we can control software in CPEs On the other hand, we want to minimize configuration cost of CPEs 7

9 Our decision 6rd - IPv6 Internet IPv6 Network 6rd Relay Router address is used as internal ID IPv6 prefix which is delegated for each subscriber is derived from global address which is assigned for same subscriber CPE can automatically configure its delegated IPv6 prefix to home network ISP s network IPv6 based Home Network L3 () 6rd CPE Network 6rd CPE 6rd Domain 8 For downstream packet, 6rd relay router can automatically form encap header from dst IPv6 address of incoming packet (without configuring a tunnel for each subs) For upstream packet, CPE can figure out tunnel end point (6rd relay router or other CPE) from dst IPv6 address

10 Why we choose 6rd? - Cost Comparison - 9

11 Architecture directs business plan Business plan simulations P/L of 6rd - JPY(M) 50 Business plan simulations - Cash flow of 6rd - JPY(M) How much does it cost to provide IPv6 service for one million customers? 13 Monthly fee (JPY) month month Cost simulations NPV comparison - 14 Monthly fee (JPY) rd Other solution JPY(M) 400 Other solutions 6rd # of server # of aggregation router cost 2 JPY1,200 万 USD133, JPY15,200 万 USD1,688, Cost Effective! Monthly fee (JPY)

12 Y!BB IPv6 Service Customer IPv6 Prefix length Monthly Charge /56 No additional Charge! ONU=Optical Network Unit HGW= Home GateWay 11

13 MHMP: Multi-homing with multi-prefix issues at IPv6 enabled residential Softbank NTT IPv6 Internet via 6rd IPv6 closednetwork via native IPv6 1. Source Address Selection 2. Next-hop Router Selection 3. DNS Server Selection Softbank s CPE 12

14 New IPv6 network Broadband Mobile Existing New (IPv6) (Global) (Private ) 13

15 Background NTT East and West assign their own IPv6 address for each user, but this address is not for the internet connectivity From next year, we can inject our own prefix to NTT network, and then our customer who connected to NTT would be assigned Softbank s IPv6 prefix. # of customer is increasing We need to provide both of and IPv6 service over native IPv6 network We should share a global address between multiple customers Big Question How to provide service over native IPv6 network? How to share one address with many customers? 14

16 Remember, architecture directs business plan 15

17 4rd: Residual Deployment Four Japanese ISP intent to adopt 4rd 32bit 16bit ISP s prefix subscriber ID TCP/UDP Port SP s IPv6 prefix Subscriber ID local site Interface ID 16

18 Example Configuration SP Prefix = /16 routing table /16 => tunnel0 Default => routing table /16 => Border Relay Router - Define global address and NAPT ports, consist of SP s IPv6 address - Encapsulate by IPv6 packet appropriately address: AB.CD NAPT ports: 0xEF00~0xEFFF tunnel0 SP s IPv6 access NW 2400:2400::/24 CPE tunnel0 2400:2401::1 DHCP-PD 2400:24AB:CDEF::1 17 Tunnel0 address= /32 One address is shared with 256 customers Tunnel0 address=unnumbered Border Relay = 2400:2401::1 LAN address = / /24

19 Example Behavior Upstream SP Prefix = /16 routing table /16 => tunnel0 Default => Border Relay Router tunnel0 2400:2401::1 Packet Packet TCP routing table /16 => Dst= :80 Src= AB.CD:0xEF00 TCP Tunnel0 address= /32 Dst= :80 Src= AB.CD:0xEF00 IPv6 Dst=2400:2401::1 Src=2400:24AB:CDEF::1 - Define global address and NAPT ports, consist of SP s IPv6 address - Encapsulate by IPv6 packet appropriately address: AB.CD NAPT ports: 0xEF00~0xEFFF SP s IPv6 access NW 2400::2400/24 CPE NAPT tunnel0 18 Packet Dst= :80 Src= :1024 TCP /24 LAN address = /2

20 Example Behavior Downstream SP Prefix = /16 routing table /16 => tunnel0 Default => Border Relay Router Packet Packet TCP Dst= AB.CD:0xEF00 Src= :80 TCP IPv6 routing table /16 => Tunnel0 address= /32 tunnel0 Dst= AB.CD:0xEF00 Src= : :2401::1 Dst=2400:24AB:CDEF::1 Src=2400:2401::1 - Define global address and NAPT ports, consist of SP s IPv6 address - Encapsulate by IPv6 packet appropriately address: AB.CD NAPT ports: 0xEF00~0xEFFF SP s IPv6 access NW 2400:2400::/24 CPE NAPT tunnel0 19 Packet Dst= :1024 Src= :80 TCP /24 LAN address = /2

21 Example Behavior Upstream (2) SP Prefix = /16 routing table routing table /16 => /16 => tunnel0 Default => Border Relay Router Dst= :66 Src= AB.CD:0xEF Tunnel0 address= /32 tunnel0 2400:2401::1 Hex : 1B Packet TCP IPv6 Dst=2400:241B:2442::1 Src=2400:24AB:CDEF::1 SP s IPv6 access NW 2400::2400/24 Dst= :66 Src= :1024 address: AB.CD NAPT ports: 0xEF00~0xEFFF NAPT Packet TCP CPE tunnel /24

22 The notion of 6rd can spread over IPv6 with address sharing Overview and some use cases with specifications are described in SAM, 4rd (draft-despres-softwire-sam, draft-despres-softwire-4rd) CPE (B4) can automatically configure its shared address and Port prefix based on a delegated IPv6 prefix Border relay router (AFTR) can automatically form encaps header to destine to subscriber with single tunnel configuration NAT44 function and states only exist in the CPE 21

23 Mobile Broadband Mobile Existing New (IPv6) (Global ) (Privat e) 22

24 Background Softbank Mobile provides 3G data service for conventional handset and Smart-phone in Japan. We are facing a circumstance in which exhaustion of both private and global addresses. Helpful guideline exists as TR23.975, scenario 3 and 4 toward IPv6 only 3G network with NAT64. The question is that which scenario can be relay on most effective and reliable architecture for Softbank case. 23

25 Remember Again, architecture directs business plan 24

26 What if stateless NAT64 work with 4rd rule as an alternative of RFC6052 SP Prefix = /16 routing table /16 => 64NAT-IF Default => routing table /16 => NAT64 64NAT-IF 2400:2db8::1 IPv6 routing table Default=>PDP-0 NAT64WKP::/96 => 64NAT-IF routing table Default=>64NAT-IF 64NAT-IF address: AB.CD/32 NAT64 WKP ports: 0xEF00~0xEFFF SP s IPv6 access NW 2400:2db8::/40 64NAT-IF IPv6 RA 2400:2db8:00AB:CDEF::1/64 V4 APP UE 25

27 Example behavior: Upstream SP Prefix = /16 routing table routing table /16 => 64NAT-IF Default => Packet /16 => Dst= :80 Src= AB.CD:0xEF00 TCP NAT64 64-IF 2400:2db8::1 Dst={NAT64WKP}: port80 Src=2400:2db8:00AB:CDEF::1 port 0xEF00 IPv6 routing table Default=>PDP-0 NAT64WKP::/96 => 64NAT-IF routing table Default=>64NAT-IF 64NAT-IF address: AB.CD/32 SP s IPv6 access NW 2400:2db8::/40 64-IF IPv6 RA 2400:2db8:00AB:CDEF::1/64 V4 APP UE Packet TCP IPv6 NAT64 WKP ports: 0xEF00~0xEFFF 26

28 Example Behavior: Downstream SP Prefix = /16 routing table routing table /16 => 64NAT-IF Default => Packet /16 => Dst= AB.CD:0xEF00 Src= :80 TCP NAT64 64-IF 2400:2db8::1 Dst=2400:2db8:00AB:CDEF::1 port 0xEF00 Src={NAT64WKP}: port80 IPv6 routing table Default=>PDP-0 NAT64WKP::/96 => 64NAT-IF routing table Default=>64NAT-IF 64NAT-IF address: AB.CD/32 SP s IPv6 access NW 2400:2db8::/40 64-IF IPv6 RA 2400:2db8:00AB:CDEF::1/64 V4 APP UE Packet TCP IPv6 NAT64 WKP ports: 0xEF00~0xEFFF 27

29 Example Behavior: Upstream(2) SP Prefix = /16 routing table routing table /16 => /16 => 64NAT-IF Default => NAT64 64-IF Drop for out of port-range pkts, or fall down to stateful NAT :2db8::1 Dst={NAT64WKP}: port80 Src=2400:2db8:00AB:CDEF::1 port 0xAB00 IPv6 routing table Default=>PDP-0 NAT64WKP::/96 => 64NAT-IF routing table Default=>64NAT-IF 64NAT-IF address: AB.CD/32 SP s IPv6 access NW 2400:2db8::/40 64-IF IPv6 RA 2400:2db8:00AB:CDEF::1/64 V4 APP UE Packet TCP IPv6 NAT64 WKP ports: 0xEF00~0xEFFF 28

30 Summary Architecture directs business plan Nobody can help v4v6 transition for ISP in business Our case: A stateless address mapping might be helpful for both Softbank s broadband and mobile to IPv6 transition 29