2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 11

NEMO Multihoming IssuesNEMO Multihoming Issuesdraft-ietf-nemo-multihoming-issues-04.txtdraft-ietf-nemo-multihoming-issues-04.txt

Chan Wah NgChan Wah Ng

Paik Eun KyoungPaik Eun Kyoung

Thierry ErnstThierry Ernst

Marcelo BagnuloMarcelo Bagnulo

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 22

Change LogChange Log

• Updated Section 3: Deployment Scenarios and Pre-requisite

• Modifications to Section 4:– Merged “Media Detection” into “Path

Exploration”– Added new Section 4.10: “Preference Settings”

• Modifications to Section 5:– Identifies which issues are important– Made recommendations on how to resolve the

issues

• Added clarifying text to Appendix B

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 33

Current Multihoming IssuesCurrent Multihoming Issues

4.1- Fault Tolerance

– Failure Detection

– Path Exploration

– Path Selection

– Re-Homing

4.2- Ingress Filtering

4.3- HA Synchronization

4.4- MR synchronization

4.5- Prefix Delegation

4.6- Multiple Bindings

4.7- Source Address Selection

4.8- Loop Prevention

4.9- Prefix Ownership

4.10- Preference Settings

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 44

ML Issues ListML Issues List

• http://www.mobilenetworks.org/nemo/draft-ietf-nemo-multihoming-issues/

• 23 Issues– 18 Accepted– 2 Rejected– 2 Closed– 1 On-Going (resolved, to close in -05)

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 55

NEMO

Our Recommendations [4.1]Our Recommendations [4.1]

• Failure Detection, Path Exploration Path-Selection, Re-Homing– Worked on by

Monami6/Shim6 WG– A lot of similarities between

fault recovery of bi-direction tunnels in NEMO and MIPv6

– Those NEMO-Specific configurations, e.g. (n MR,* HA,* MNP), can be augmented with a MR synchronization mechanism

MR1 MR2

HA1 HA2

CN

MNN

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 66

NEMO

Our Recommendations [4.2]Our Recommendations [4.2]

• Ingress Filtering for (n MR,n HA,n MNP)– Worked on by

NEMO WG

MR1 MR2

HA1 HA2

CN

MNN

Prefix=P1 Prefix=P2

Address=P1::MNN

Prefix=P1 Prefix=P2

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 77

Our Recommendations [4.3]Our Recommendations [4.3]

• HA Synchronization – Worked on by

Monami6 WG– This is not specific to

NEMO, since a mechanism such as a HAHA protocol can also be used for MIPv6 Hosts MR1 MR2

HA1 HA2

MNN

Prefix Delegation

Prefix Delegation

NEMO

How to delegate the same prefix?How to delegate the same prefix?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 88

Our Recommendations [4.4]Our Recommendations [4.4]

• MR Synchronization– Generic IPv6 issues

• Any link with multiple default routers would require some form of signaling

– Individual draft submissions seems to indicate a NEMO-specific interest

MR1 MR2

MNN

NEMO

How to delegate the same prefix?

Can we coordinate to achieve fault tolerance, etc?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 99

Our Recommendations [4.5]Our Recommendations [4.5]

• Prefix Delegation– The WG Drafts on prefix delegation to

be reviewed for multihoming considerations by the NEMO WG

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1010

Our Recommendations [4.6]Our Recommendations [4.6]

• Multiple Bindings– Worked on by

Monami6 WG• Chartered Work

Item

– Ensure its compatible with NEMO MNN1

MR

HA

MNN2

WLAN

NEMO

How to register two CoAs?

3GPP

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1111

Our Recommendations [4.7]Our Recommendations [4.7]

• Source Address Selection– There should be a

mechanism for MNNs to choose its source address

– A general IPv6 problem– Not very important

NEMO

MR1 MR2

MNN

Prefix=P1 Prefix=P2

Hmm … which address should I

choose?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1212

Our Recommendations [4.8]Our Recommendations [4.8]

• Loop Prevention in Nested NEMO– Study the effect of

loops forming in nested NEMO

MR5MR5

MR2MR2MR4MR4

MR3MR3

MR1MR1

attaches to

attaches to

attaches to

attaches to

attaches toattaches

to

attaches to

Internet

attaches to

ARAR

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1313

Our Recommendations [4.9]Our Recommendations [4.9]

• Prefix Ownership– Vendors and Operators to express

their interest in this problem– Need not be solved now

NEMO

MR1 MR2

HA

MNN1

Prefix=P1 Prefix=P1

MNN2

NEMO

MR1 MR2

MNN1

Prefix=P1Prefix=P1

MNN2

Who owns the prefix P1?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1414

Our Recommendations [4.10]Our Recommendations [4.10]

• Preference Settings– There should be a

mechanism for NMMs to set its preference for exit routers

– A general IPv6 problem

– Not very important

MNN1MR

HA

MNN2

WLAN

NEMO

How can I tell MR to use WLAN or 3GPP?

3GPP

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1515

Moving ForwardMoving Forward

• For each issue:

Q1: Is our recommendation the WG consensus?

Q2: How many people think that the issue is significant enough to be worked on?

Q3: How many people are willing to work on the issue?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1616

PollPoll

Issue Our Rec. Q1 Q2 Q3

Fault Tolerance Shim6/Monami6

Ingress Filtering NEMO

HA Synchronization Monami6

MR Synchronization IPv6

Prefix Delegation NEMO

Recall: Q1- Is our recommendation the WG consensus?Q2- How many think the issue is important?Q3- How many are willing to work on it?

2005110920051109 64th IETF - NEMO WG64th IETF - NEMO WG 1717

PollPoll

Issue Our Rec. Q1 Q2 Q3

Multiple Bindings Monami6

Source Address Selection

--

Loop Prevention NEMO

Prefix Ownership --

Preference Settings --Recall: Q1- Is our recommendation the WG consensus?

Q2- How many think the issue is important?Q3- How many are willing to work on it?