Flow mobility support in PMIPv6 draft-trung-netext-flow-mobility-support-01 T. Tran, Y. Hong (ETRI) Y. Han (KUT) 2/12/20141 [email protected] IETF.

Flow mobility supportin PMIPv6

draft-trung-netext-flow-mobility-support-01

T. Tran, Y. Hong (ETRI)Y. Han (KUT)

04/10/23 [email protected]

IETF 79 - Beijing

Outlines

• Flow mobility requirements• Necessary PMIPv6 extensions• NS3 implementation• Conclusions

04/10/23 [email protected]

Flow mobility requirements (1)

• 5-tuple based flow description: Home Network  Prefix should be able to be shared across its attachments (called shared-prefix model)

04/10/23 [email protected]

WiFi

3GPP

Voice (HNP1)

Proxy- CoA1 Proxy- CoA2

LMA

MAG1 MAG2Video (HNP1)

WiFi

3GPP

Voice (HNP1) Video (HNP1)

Proxy- CoA1 Proxy- CoA2

LMA

MAG1 MAG2

Flow mobility requirements (2)

• HNP based flow description: the HNP is not needed to be shared across interface. Unique-prefix can be assigned to each IF.

04/10/23 [email protected]

WiFi

3GPP

Voice (HNP1)

Proxy- CoA1 Proxy- CoA2

LMA

MAG1 MAG2Video (HNP2)

WiFi

3GPP

Voice (HNP1) Video (HNP2)

Proxy- CoA1 Proxy- CoA2

LMA

MAG1 MAG2

Flow mobility requirements (3)

• LMA should support flow-based routing

04/10/23 [email protected]

TS (Flow inf.)

HNP ATT ProxyCoA

1 (Voice) HNP1 3GPP MAG1

2 (Video) HNP1 WiFi MAG2

Flow HNP ATT ProxyCoA

1 (Voice) HNP1 3GPP MAG1

2 (Video) HNP2 WiFi MAG2

5-tuple based flow description

HNP based flow description

PMIPv6 extensions for supporting shared prefix model

• Pro-active signaling– The same HNPs are assigned to all

interfaces in advance

• Re-active signaling– HNP is shared across interfaces only

when the flow mobility is occurred

04/10/23 [email protected]

MN MAG1 MAG2 LMA

IF1 Bi-Tunnel (HNP1)Attached (HNP1)

Flow 1

IF2(New attachment)

Router Solicitation

HUA

Bi-Tunnel (HNP2)

PBA (HNP1,2)

IF2 (HNP1,2)

HUR (HNP2)

Accept HUR, Setup Tunnel & Routing

Accept HUA, Setup Tunnel & Routing

IF1(HNP1,2)

Update Flow binding table

Flow 1IF2

(HNP1,2)

IF1(HNP1)

PBU (HI=1)

Router Advertisement (HNP1,2)

Flow 1

Router Advertisement (HNP1,2)

Flow 1

Bi-Tunnel (HNP1,2)

Decide to move Flow 1 to MAG2

04/10/23 [email protected] 7

Pro-Active Signaling

(1) Modify PBA message to include the HNPs that are assigned to the existing attachments

(2) Extend the signaling between LMA/MAG to update new HNP to the MAG

MN MAG1 MAG2 LMA

Bi-Tunnel for (HNP1)Attached (HNP1)

Flow 1

Router Solicitation

HUA

Bi-Tunnel (HNP1)

PBA (HNP2)

Decide to move Flow 1 to MAG2

HUR (HNP1)

Accept HUR, Setup Tunnel & Routing

Accept HUA, Setup Tunnel & Routing

Update Flow binding table

Flow 1

PBU (HI=1)

Router Advertisement (HNP2)

Flow 1

Router Advertisement (HNP1,2)

Flow 1

Bi-Tunnel (HNP2)

IF1

IF2 (HNP2)

IF2 (HNP1,2)

IF1(HNP1)

IF2(New attachment)

IF2 (HNP1,2)

04/10/23 [email protected] 8

Re-Active Signaling

(1) Extend the signaling between LMA/MAG to update new HNP to the MAG

PMIPv6 extensions for supportingFlow-based routing (1)

• Extend BCE to support multiple Care-of Address registration

04/10/23 [email protected] 9

BID MN-ID ATT HNP Proxy-CoA

1 MN1 3GPP HNP1 IP1 (MAG1)

2 MN1 WiFi HNP2 IP2 (MAG2)

BID MN-ID ATT HNP Proxy-CoA

1 MN1 3GPP HNP1 IP1(MAG1)

2 MN1 WiFi HNP 2 + HNP1

IP2(MAG2)

(1) The MN1 attached to the network using 2 interfaces

(2) LMA requests MAG2 to updated with HNP1

PMIPv6 extensions for supportingFlow-based routing (2)

• Add flow binding function to the LMA

04/10/23 [email protected] 10

(1) Before the flow mobility occurs

(2)After the LMA decides to move TCP flow 1 to the MAG 2

FID TS BID Action Mode

1 TCP (Flow1) 1 Forward Active

2 UDP 2 Forward Inactive

FID TS BID Action Mode

1 TCP (Flow1) 2 Forward Active

2 UDP 2 Forward Inactive

Implementation in NS3

• We are now implementing our proposals in NS3

• Why NS3?– It supports multi-interface nodes

• In our simulation, an MN will have WLAN, WiMAX, 3GPP interfaces.

• and also logical interface!

– It supports (near-complete) IPv6 stack– It conforms to standard input/output

formats so that other tools can be reused.• e.g., pcap trace output

04/10/23 [email protected] 11

Conclusions

• PMIPv6 can be extended in two ways to support flow mobility: Pro-active and Re-active signaling

• No flow information is needed to be sent from LMA to MAG

• To support full flow granularity movement we should differentiate flows by using 5-tuple inf., otherwise we can support just partial handoff.

• The MN just obeys the flow policy from the network. It always uses the same interface to receive and send packets of a flow.

04/10/23 [email protected] 12

Q & A

Thank you!

04/10/23 [email protected] 13