네트워크 인지적 Dual-Stack IP 이동성 및 멀티호밍 기술 Youn-Hee Han Korea University of Technology and Education Internet Computing Laboratory 2 nd IPv6 Forum Korea Workshop 2008

Outline Web 2.0 and IPv6 PMIPv6’s Dual-Stack Support (DS-PMIP) Network Cognition in DS-PMIP Part 1: Subnet Model Part 2: Multihoming & Vertical Handover Determination Conclusions & Discussion 2/402 nd IPv6 Forum Korea Workshop 2008

Web 2.0 and IPv6 3/402 nd IPv6 Forum Korea Workshop 2008

Carrier-Grade NAT (CGN) 4/40 Most conservative access model changes introducing “Carrier-Grade NAT (CGN)” Access Concentrator Internet Global v4 address CPE With NAT Global v4 address End Host Private v4 address FTTH ADSL Access Concentrator With NAT Internet Global v4 address CPE With NAT Private IPv4 address End Host Private v4 address Source: 72th IETF (July 2008) 2 nd IPv6 Forum Korea Workshop 2008

CGN’s Limitation 5/40 CGN looks v6 is not needed? No. CGN has serious restrictions. IPv6 is needed ! Each customer can have only some “limited” numbers of sessions simultaneously. “port number” is just 2bytes which means 64K For example, if 2000 customer shares same Global IPv4 address (please note that this is just for example), only 25 or 30 so sessions can be used by each customer at the worst case. Which means that: 2 nd IPv6 Forum Korea Workshop 2008

CGN’s Limitation - Web 2.0 and IPv6 6/40 Max 30 ConnectionsMax 20 Connections Max 15 ConnectionsMax 10 Connections Source: 72th IETF (July 2008) 2 nd IPv6 Forum Korea Workshop 2008

“Ajax” web application Web 2.0 Application’s Operation Browser UI: server-side server processing Ajax: time UI Other data (e.g. images) HTML / CSS data XML data JavaScript Code – the Ajax Engine XMLHttpRequest() HTML rendering engine JavaScript Engine data stores backend etc. web server browser server-side systems request html + css + xml data mgmt Desktop UI “session” management concurrent sessions 2 nd IPv6 Forum Korea Workshop 20087/40

Web 2.0 and IPv6 8/40 Source: 72th IETF (July 2008) Examples of # of concurrent sessions of web 2.0 sites AJAX applications of Web 2.0 break behind NAT  Too many connections exhaust public IP port space Webpage# of sessions No operation 5 ～ 10 Yahoo top page 10 ～ 20 Google image search 30 ～ 60 Nico Nico Douga 50 ～ 80 OCN photo friend170 ～ 200+ iTunes 230 ～ 270 iGoogle 80 ～ 100 Rakuten 50 ～ 60 Amazon90 HMV100 YouTube90 2 nd IPv6 Forum Korea Workshop 2008

PMIPv6’s Dual-Stack Support (DS-PMIP) 9/402 nd IPv6 Forum Korea Workshop 2008

PMIPv6 Overview LMM (Localized Mobility Management) Domain MAG LMA Proxy Binding Update/Ack. (PBU/PBA) Control message sent by MAG to LMA to establish a binding between MN-HoA and Proxy-CoA Home Network Proxy Care of Address (Proxy-CoA) The address of MAG That will be the tunnel end-point IP Tunnel IP-in-IP tunnel between LMA and MAG MAG LMA: Localized Mobility Agent MAG: Mobile Access Gateway LMA Address (LMAA) MN’ Home Address (MN-HoA) MN continues to use it as long as it roams within a same domain That will be the tunnel entry-point MN’s Home Network (Topological Anchor Point) MN’s Home Network Prefix (MN-HNP) CAFE:2:/64 movement 10/40 RFC nd IPv6 Forum Korea Workshop 2008

IPv4 Support for PMIPv6 Two functions supported IPv4 Transport Network Support IPv4 Home Address Mobility The new WG draft for IPv4 support for PMIPv6 R. Wakikawa (Toyota ITC) and S. Gundavelli (Cisco), “IPv4 Support for Proxy Mobile IPv6”, draft-ietf-netlmm-pmip6-ipv4-support-04.txt, July 14, /40 + RFC 5213 = DS-PMIP 2 nd IPv6 Forum Korea Workshop 2008

DS-PMIP 이 고려하는 전송 네트워크 이질성 IP Transport Network Heterogeneity  IPv6/IPv4/Private IPv4 Transport Network Support Expected Mobility Scenarios Cellular IP network AAA WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 Private IPv4 NAT LMA MN 12/40 MAG 2 nd IPv6 Forum Korea Workshop 2008

DS-PMIP 이 고려하는 어플리케이션 이질성 (1/2) IPv6 Home Address Mobility Expected Mobility Scenarios Cellular IP network WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 Private IPv4 NAT AAA LMA IPv4 IPv6 IPv6 Application (VoD, IP-Phone…) MN 13/40 MAG IPv6 Application (VoD, IP-Phone…) 2 nd IPv6 Forum Korea Workshop 2008

DS-PMIP 이 고려하는 어플리케이션 이질성 (2/2) IPv4 Home Address Mobility Expected Mobility Scenarios Cellular IP network WLAN IP Network WiBro IP Network RAS LTE BS WLAN AP IPv4 IPv6 NAT AAA DSMIPv6 HA IPv4 IPv6 IPv4 Application (VoD…) IPv6 Application (IP-Phone…) 14/40 MAG Private IPv4 MN IPv4 Application (VoD…) IPv6 Application (IP-Phone…) 2 nd IPv6 Forum Korea Workshop 2008

6-in- udp-in-4 Tunnel 4-in- udp-in-4 Tunnel 6-in-4 Tunnel 4-in-4 Tunnel MAG 와 LMA 사이의 시그널링 및 터널 설정 LMA ( 바인딩 관리 : IPv6 HoA & IPv4 HoA  IPv4 or IPv6 Proxy-CoA ) MAG IPv4- UDP- IPv6- PBU IPv4- UDP- IPv6- PBAck 6-in-6 Tunnel 4-in-6 Tunnel MAG IPv6- PBU IPv6- PBAck NAT MN 이 IPv6 네트워크로 이동할 때 MN 이 IPv4 네트워크로 이동할 때 MN 이 Private IPv4 네트워크로 이동할 때 IPv4- UDP- IPv6- PBU IPv4- UDP- IPv6- PBAck 15/40 Signaling & Tunneling in DS-PMIP 2 nd IPv6 Forum Korea Workshop 2008

DS-PMIP 시나리오별 정리 IPv6 HoA 이동성 지원 IPv4 HoA 이동성 지원 IPv6 & IPv4 HoA 이동성 동시 지원 MAG-LMA IPv6 Transport [PBU 전달 방식 ] : IPv6 [PBU 추가 옵션 ] : 없음 [PBA 추가 옵션 ] : 없음 [ 생성되는 데이터 터널 ] : 6-in-6 [PBU 전달 방식 ] : IPv6 [PBU 추가 옵션 ] : IPv4 HoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option [ 생성되는 데이터 터널 ] : 4-in-6 [PBU 전달 방식 ] : IPv6 [PBU 추가 옵션 ] : IPv4 HoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option [ 생성되는 데이터 터널 ] : 6-in-6, 4-in-6 MAG-LMA IPv4 Transport [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 CoA option [PBA 추가 옵션 ] : NAT Detection option [ 생성되는 데이터 터널 ] : 6-in-4 [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 HoA option : IPv4 CoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option : NAT Detection option [ 생성되는 데이터 터널 ] : 4-in-4 [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 HoA option : IPv4 CoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option : NAT Detection option [ 생성되는 데이터 터널 ] : 6-in-4, 6-in-4 MAG-LMA Private IPv4 Transport [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 CoA option [PBA 추가 옵션 ] : NAT Detection option [ 생성되는 데이터 터널 ] : 6-in-udp-in-4 [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 HoA option : IPv4 CoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option : NAT Detection option [ 생성되는 데이터 터널 ] : 4-in-udp-in-4 [PBU 전달 방식 ] : IPv4-UDP 패킷 [PBU 추가 옵션 ] : IPv4 HoA option : IPv4 CoA option [PBA 추가 옵션 ] : IPv4 Address Ack. Option : NAT Detection option [ 생성되는 데이터 터널 ] : 6-in-udp-in-4, 4-in-udp-in-4

DS-PMIP 종합 테스트베드 (2007, 2008) MN has Dual Stack and both addresses are always enabled In ETRI SSID: PMIP1 SSID: PMIP2 SSID: PMIP3 MAG1 ra0) ffe:1:1::1/64 fe80::1 eth0) 3ffe:1::2/64 MAG2 ra0) ffe:1:2::1/64 fe80::1 eth0) ra0) ffe:1:3::1/64 fe80::1 eth0) V6 network V4 network 초기 실행 : v6 VoD Client 초기 실행 : v4 VoD Client LMA CN NAT eth0) ffe:1::1/64 eth1) ffe:2::1/64 eth0) ffe:2::2/64 V4/V6 network Private V4 network MAG3 LMA 가 MN 에게 할당할 Prefix Pool 3ffe:1:3:1::/64 ~ 3ffe:1:3:ffff::/64 17/402 nd IPv6 Forum Korea Workshop 2008 v4/v6 VoD Server

DS-PMIP in only Private IPv4 Network and IPv4 App. (2007) In KT LMA (PC0) VoD (PC4) Subnet 4 NAT1 NAT2 MAG1 (PC1) MAG2 (PC2) Subnet 1Subnet 2 MAG3 (PC3) Subnet 3 Notebook1Notebook2Notebook g802.11a /402 nd IPv6 Forum Korea Workshop 2008

Network Cognition in DS-PMIP Part 1: Subnet Model 19/402 nd IPv6 Forum Korea Workshop 2008

Definitions (RFC 4903, June 2007) Link  a topological area of an IP network delimited by routers. Subnet  a topological area of an IP network that uses the same unsubdivided address prefix. The consensus in IETF A link with multiple subnet prefix: YES A subnet with multiple links (Multi-link Subnet): NO  ONE SUBNET SPANS ONLY ONE LINK However… The design of NETLMM would lay a single subnet on the entire NETLMM domain. Subnet and Link 20/402 nd IPv6 Forum Korea Workshop 2008

Two Contradictory Constraints MN’s subnet does not change when the MN moves in domain (MN’s subnet spans on the entire NetLMM Domain) MN’s subnet does not span more than one link. NetLMM Subnet Model MN’s subnet has to follow the movements of the MN.  Per-MN Subnet MAG LMA MN MAG LMA MN MAG 같은 MN 이네 ? 그럼 똑같은 Subnet 을 만들어 주어야지 PBA (Home Network Prefix #1) RA (Home Network Prefix #1) 21/402 nd IPv6 Forum Korea Workshop 2008

Network Cognition in DS-PMIP Part 2: Multihoming & Vertical Handover Support 22/402 nd IPv6 Forum Korea Workshop 2008

List of PBU Options PBU Options Mandatory Options  MN-ID: MN-NAI  Home Network Prefix (HNP)  Handoff Indicator (HI)  Access Technology Type (ATT) Additional Options  MN-LL (Link-layer)-ID  Link-local Address (of MAG)  Timestamp They are used when MAG/LMA support Multihoming & Horizontal/Vertical Handover 23/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HNP Option Values? Home Network Prefix (HNP) option NON_ZERO (Pre-assigned HNP): Binding Refreshment ALL_ZERO: Initial Attachment / Handoff MAG LMA MN PBU (HNP=ALL_ZERO) MAG LMA MN PBU (HNP=ALL_ZERO) MAG LMA MN MAG 핸드오프 ! ( 핸드오프가 아니라 초기 접속이라도 …) 초기 접속이군 ! Binding 정보를 다시 보내서 Lifetime 을 늘려야겠다. PBU (HNP=HNP #1) 24/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines ATT Option Values? Access Technology Type (ATT) option 1: Virtual 2: PPP (3GPP/3GPP2) 3: IEEE : IEEE a/b/g 5: IEEE e MAC must knows the ATT by which MN is currently attached How to now?  link-specific methods  manual setting  or other methods MAG LMA PBU (ATT=5) MAG MN WiBro ATT is IEEE e !!! 25/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines MN-LL-ID Option Values? MN-Link Layer (LL)-ID option E.g., IEEE 802 MAC Address If MAG can know MN-LL-ID, it must insert it into PBU (Recommended) If MAG cannot know MN-LL-ID, it must not insert it into PBU How to now?  link-specific methods  or other methods MN-LL-ID is used to determine the handoff state MAG LMA PBU (MN-LL-option=XXX) MAG MN WiBro (IEEE 802 MAC: XXX) 3G IEEE 802 MAC: XXX 26/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? Handoff Indicator (HI) option 1: Attachment over a new interface 2: Handoff between two different interfaces of the MN 3: Handoff between MAGs for the same interface 4: Handoff state unknown 5: Handoff state not change (Binding Refresh) WiBro MAG LMA PBU (HI=1) MAG 3G MN 3GWiBro MAG LMA PBU (HI=1) MAG MN 3GWiBro 3G 초기 접속이군 ! 다른 인터페이스의 스위치 를 올려서 단순하게 접속만 시도했군 ! 세션이동성도 없고 … 27/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? Handoff Indicator (HI) option 1: Attachment over a new interface 2: Handoff between two different interfaces of the MN 3: Handoff between MAGs for the same interface 4: Handoff state unknown 5: Handoff state not change (Binding Refresh) WiBro MAG LMA PBU (HI=2) MAG 3G MN 3GWiBro MAG LMA PBU (HI=1) MAG MN WiBro 3G 새로운 인터페이스로 세션을 이동하고 있네 ? Vertical 핸드오버군 ! 28/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? Handoff Indicator (HI) option 1: Attachment over a new interface 2: Handoff between two different interfaces of the MN 3: Handoff between MAGs for the same interface 4: Handoff state unknown 5: Handoff state not change (Binding Refresh) WiBro MAG LMA PBU (HI=3) MAG WiBro MAG LMA PBU (HI=1) MAG MN WiBro 3G MN WiBro3G 같은 인터페이스로 세션을 이동하고 있네 ? Horizontal 핸드오버군 ! 29/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? Handoff Indicator (HI) option 1: Attachment over a new interface 2: Handoff between two different interfaces of the MN 3: Handoff between MAGs for the same interface 4: Handoff state unknown 5: Handoff state not change (Binding Refresh) WiBro MAG LMA PBU (HI=4) MAG WiBro MAG LMA PBU (HI=1) MAG MN WiBro 3G MN WiBro3G 도저히 상황파악을 못하겠다 …??? 30/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? Handoff Indicator (HI) option 1: Attachment over a new interface 2: Handoff between two different interfaces of the MN 3: Handoff between MAGs for the same interface 4: Handoff state unknown 5: Handoff state not change (Binding Refresh) MAG LMA PBU (HI=1) MAG MN WiBro 3G 단순하게 Binding 정보를 다시 보내서 Lifetime 을 늘려야겠다. MAG LMA PBU (HI=5) MAG MN WiBro 3G 31/402 nd IPv6 Forum Korea Workshop 2008

How MAG determines HI Option Values? How to know the value of Handoff Indicator (HI) option? [Case1] Link-specific Method [Case2] Context Transfer between MAGs [Case3] New Signaling Interface between MN and MAG  MN sends the exact indication to MAG  MN’s Layer 2 or 3 modification needed MAG LMA MAG MN MAG LMA MAG MN Context Transfer [Case2] New Signaling [Case3] MAG LMA MAG MN [Case1] Link-specific Method 32/402 nd IPv6 Forum Korea Workshop 2008

LMA’s Policy LMA’s Procedure when it receives PBU (1/3) HNP=ALL_ZERO ? [MN-ID & ATT & MN-LL-ID] matches in BCE ? YES ( 초기 접속 or 핸드오프 ) New BCE Entry Creation & New HNP ( 새로운 Mobility Session 으로 관리 ) The Existing BCE Entry Update ( 기존 Mobility Session 유지관리 ) NO MN-LL-ID exist in PBU? YES NO ( 바인딩 갱신 ) NO Initial Attachment Handoff 세 가지 정보가 모두 일치하는가 ? MN-ID matches in BCE & HI=2 ? 초기 접속인 경우 (Scenario 1) Vertical Handoff 인 경우 (Scenario 3) Horizontal Handoff 인 경우 (Scenario 2) 33/402 nd IPv6 Forum Korea Workshop 2008

LMA’s Policy LMA’s Procedure when it receives PBU (2/3) HNP=ALL_ZERO ? YES ( 초기 접속 or 핸드오프 ) New BCE Entry Creation & New HNP ( 새로운 Mobility Session 으로 관리 ) The Existing BCE Entry Update ( 기존 Mobility Session 유지관리 ) MN-LL-ID exist in PBU? YES NO ( 바인딩 갱신 ) NO MN-ID matches in BCE & HI=2 or HI=3 ? YES NO Initial Attachment Handoff 34/402 nd IPv6 Forum Korea Workshop 2008

LMA’s Policy LMA’s Procedure when it receives PBU (3/3) HNP=ALL_ZERO ? HNP and MN-ID matches in BCE ? NO ( 바인딩 갱신 ) NO New BCE Entry Creation & New HNP ( 새로운 Mobility Session 으로 관리 ) Lifetime Update in the Exiting BCE Entry YES YES ( 초기 접속 or 핸드오프 ) Initial Attachment Binding Refreshment Binding Refreshment 인 경우 (Scenario 4) 35/402 nd IPv6 Forum Korea Workshop 2008

Procedure Summary Scenario 1: Initial Attachment (and Multihoming) LMA creates a new BCE entry LMA allocates a new HNP LMA manages a new different session WiBro MAG LMA MAG 3G MN MAG LMA PBU (MN-ID=MN, HNP=ALL_ZERO, HI=1, ATT=5, MN-LL-ID=XXX) MAG MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) WiBro3G PBA (HNP=HNP#1) RA (Prefix=HNP#1) HNP#1 PBU (MN-ID=MN, HNP=ALL_ZERO, HI=1, ATT=2, MN-LL-ID=YYY) PBA (HNP=HNP#2) RA (Prefix=HNP#2) HNP#1HNP#2 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX HNP #2 MN Proxy -CoA2 2YYY 36/402 nd IPv6 Forum Korea Workshop 2008

Procedure Summary Scenario 2: Horizontal Handoff LMA updates the existing BCE entry LMA allocates the same HNP LMA keeps the existing session WiBro MAG LMA MAG LMA MAG WiBro PBA (HNP=HNP#1) RA (Prefix=HNP#1) PBU (MN-ID=MN, HNP=ALL_ZERO, HI=1, ATT=5, MN-LL-ID=XXX) PBU (MN-ID=MN, HNP=ALL_ZERO, HI=3, ATT=5, MN-LL-ID=XXX) WiBro MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) HNP#1 WiBro MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) HNP#1 RA (Prefix=HNP#1) HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA2 5XXX 37/402 nd IPv6 Forum Korea Workshop 2008

Procedure Summary Scenario 3: Vertical Handoff LMA updates the existing BCE entry LMA allocates the same HNP LMA keeps the existing session WiBro MAG LMA MAG 3G MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) MAG LMA MAG MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) WiBro3G PBA (HNP=HNP#1) HNP#1 PBA (HNP=HNP#1) RA (Prefix=HNP#1) HNP#1 PBU (MN-ID=MN, HNP=ALL_ZERO, HI=1, ATT=5, MN-LL-ID=XXX) PBU (MN-ID=MN, HNP=ALL_ZERO, HI=2, ATT=2, MN-LL-ID=YYY) RA (Prefix=HNP#1) HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA2 2YYY 38/402 nd IPv6 Forum Korea Workshop 2008

Procedure Summary Scenario 4: Binding Refreshment LMA updates lifetime of the existing BCE entry LMA keeps the existing session MAG LMA MAG MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) WiBro3G PBA (HNP=HNP#1) HNP#1 PBU (MN-ID=MN, HNP=ALL_ZERO, HI=1, ATT=5, MN-LL-ID=XXX) RA (Prefix=HNP#1) HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX MAG LMA MAG MN 3G (LL-ID: YYY) WiBro (IEEE 802 MAC: XXX) WiBro3G PBA (HNP=HNP#1) HNP#1 PBU (MN-ID=MN, HNP=HNP#1, HI=5, ATT=5, MN-LL-ID=XXX) RA (Prefix=HNP#1) HNP MN- ID CoAATT MN-LL- ID HNP #1 MN Proxy -CoA1 5XXX 39/402 nd IPv6 Forum Korea Workshop 2008

IPv4 and NAT is limited! Web 2.0 & IPv6 DS-PMIP (Dual-Stack Proxy Mobile IPv6) IPv4/v6 Transport Network Heterogeneity IPv4/v6 Home Address Mobility Network Cognition in DS-PMIP Subnet Model Multihoming & Vertical Handover Determination DS-PMIP’s Network Cognition Behavior is one of early examples of future “Cognitive Networks” Conclusions 40/402 nd IPv6 Forum Korea Workshop 2008