1 / 17

NEMO Multihoming Issues draft-ietf-nemo-multihoming-issues-04.txt

NEMO Multihoming Issues draft-ietf-nemo-multihoming-issues-04.txt. Chan Wah Ng Paik Eun Kyoung Thierry Ernst Marcelo Bagnulo. Change Log. Updated Section 3: Deployment Scenarios and Pre-requisite Modifications to Section 4: Merged “Media Detection” into “Path Exploration”

cheung
Download Presentation

NEMO Multihoming Issues draft-ietf-nemo-multihoming-issues-04.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NEMO Multihoming Issuesdraft-ietf-nemo-multihoming-issues-04.txt Chan Wah Ng Paik Eun Kyoung Thierry Ernst Marcelo Bagnulo 64th IETF - NEMO WG

  2. Change 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 64th IETF - NEMO WG

  3. Current 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 64th IETF - NEMO WG

  4. ML 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) 64th IETF - NEMO WG

  5. Our Recommendations [4.1] CN • 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 HA1 HA2 MR1 MR2 NEMO MNN 64th IETF - NEMO WG

  6. Our Recommendations [4.2] CN • Ingress Filtering for (n MR,n HA,n MNP) • Worked on by NEMO WG HA1 HA2 Prefix=P2 Prefix=P1 MR1 MR2 Prefix=P2 Prefix=P1 NEMO Address=P1::MNN MNN 64th IETF - NEMO WG

  7. Our Recommendations [4.3] How to delegate the same prefix? How to delegate the same prefix? • 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 HA1 HA2 Prefix Delegation Prefix Delegation MR1 MR2 NEMO MNN 64th IETF - NEMO WG

  8. 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 Can we coordinate to achieve fault tolerance, etc? How to delegate the same prefix? MR1 MR2 NEMO MNN 64th IETF - NEMO WG

  9. Our Recommendations [4.5] • Prefix Delegation • The WG Drafts on prefix delegation to be reviewed for multihoming considerations by the NEMO WG 64th IETF - NEMO WG

  10. Our Recommendations [4.6] • Multiple Bindings • Worked on by Monami6 WG • Chartered Work Item • Ensure its compatible with NEMO HA How to register two CoAs? WLAN 3GPP MR MNN1 NEMO MNN2 64th IETF - NEMO WG

  11. 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 Hmm … which address should I choose? MR1 MR2 Prefix=P2 Prefix=P1 NEMO MNN 64th IETF - NEMO WG

  12. Our Recommendations [4.8] • Loop Prevention in Nested NEMO • Study the effect of loops forming in nested NEMO Internet AR attaches to MR1 attaches to MR3 attaches to attaches to attaches to MR4 MR2 attaches to attaches to attaches to MR5 64th IETF - NEMO WG

  13. Our Recommendations [4.9] • Prefix Ownership • Vendors and Operators to express their interest in this problem • Need not be solved now Who owns the prefix P1? HA MR2 MR1 MR1 MR2 Prefix=P1 Prefix=P1 Prefix=P1 Prefix=P1 NEMO NEMO MNN1 MNN2 MNN2 MNN1 64th IETF - NEMO WG

  14. 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 HA How can I tell MR to use WLAN or 3GPP? WLAN 3GPP MR MNN1 NEMO MNN2 64th IETF - NEMO WG

  15. Moving 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? 64th IETF - NEMO WG

  16. Poll 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? 64th IETF - NEMO WG

  17. Poll 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? 64th IETF - NEMO WG

More Related