1 / 16

NEMO Multi-homing Issues

NEMO Multi-homing Issues. Prepared for 59 th IETF NEMO WG By Chan-Wah NG, Eun-Kyoung PAIK, Thierry ERNST, Julien CHARBON 2004 03 01 draft-ng-nemo-multihoming-issues-03.txt. Change-Log. Changes to draft-ng-nemo-multihoming-issues merged in draft-paik-nemo-multihoming-problem

ryder
Download Presentation

NEMO Multi-homing Issues

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 Multi-homing Issues Prepared for 59th IETF NEMO WG By Chan-Wah NG, Eun-Kyoung PAIK, Thierry ERNST, Julien CHARBON 2004 03 01 draft-ng-nemo-multihoming-issues-03.txt 59th IETF – NEMO Working Group

  2. Change-Log • Changes to draft-ng-nemo-multihoming-issues • merged in draft-paik-nemo-multihoming-problem • moved alternatives classifications to appendix • based benefits/goals from draft-multihoming-generic-goals-and-benefits-00.txt • title change to “Analysis of Multihoming in Network Mobility Support” 59th IETF – NEMO Working Group

  3. Contents (1) • Sect 1: Introduction • Important thing is the objective: • To identify which multihoming configurations are useful • To capture issues for deploying a multihomed mobile network • Assuming NEMO Basic Support solution is used 59th IETF – NEMO Working Group

  4. Contents (2) • Sect 2: Classification • The usual (x,y,z) classification • x = number of MRs where x=1 implies a single mobile router with multiple interfaces and x=N implies multiple mobile routers • y = number of home-agent • z = number of NEMO-Prefix announced to the MNNs • Important point is to identify the useful classifications • We will return to this when we talk about Section 5 59th IETF – NEMO Working Group

  5. Contents (3) • Sect 3: Benefits & Goals of Multihoming in NEMO • Give deployment scenarios of each of five goals/benefits identified in draft-multihoming-generic-goals-and-benefits-00.txt • Ubiquitous Access • Redundancy/Fault-Recovery • Load Sharing • Load Balancing • Preference Settings 59th IETF – NEMO Working Group

  6. Contents (4) • Sect 4: Problem Statement • Identifies the main problem when trying to reach the goals with NEMO • Connection Availability • Connection Selection • Scalability • RO Consideration • Ingress Filtering • Failure Detection 59th IETF – NEMO Working Group

  7. Contents (5) • Sect 5: Evaluation of Basic NEMO Solution • Discusses issues and problems implementers might face for each of the 8 identified multihomed NEMO configurations 59th IETF – NEMO Working Group

  8. Moving Forward • Decide on which scenario is useful for NEMO • Is the content structure of the draft okay? • Introduction • Classification/Taxonomy • Benefits/Scenarios • Problem Statement • Evaluation of NEMO Basic Support 59th IETF – NEMO Working Group

  9. HA INTERNET MR P MNN MNN (1,1,1): 1 MR, 1 HA, 1 Prefix • Scenario: • Multi-mode MR (a MR with GPRS and 802.11) • Benefits: • Ubiquitous Access, Redundancy/Fault-Recovery • Problems/Issues: • Need to associate multiple CoAs to one NEMO prefix • Clearly NEMO-Specific 59th IETF – NEMO Working Group

  10. HA INTERNET MR P1,P2 MNN MNN (1,1,N): 1 MR, 1 HA, N Prefixes • Scenario: • Car with a single MR and different sub-nets, one for sensors, one for data • Benefits: • Ubiquitous Access, Redundancy/Fault-Recovery • Problems/Issues: • Need to associate multiple CoAs with one or multiple prefixes 59th IETF – NEMO Working Group

  11. HA-2 HA-1 INTERNET MR P MNN MNN (1,N,1): 1 MR, N HA, 1 Prefix • Scenario: • dynamically assign/selects home-agents to reduce delays • Transatlantic flight • Benefits: • Ubiquitous Access (reduce delays) • Redundancy (HA failure) • Problems/Issues: • One HoA registered at different home agents • MIPv6 specific • One NEMO-Prefix advertised by different home agents • Complex problem • Best left to multi6 WG 59th IETF – NEMO Working Group

  12. HA-2 HA-1 INTERNET MR P1,P2 MNN MNN (1,N,N): 1 MR, N HAs, N Prefixes • Scenario: • Multi-mode MRs (8012.11+3G) subscribing to different ISPs • Benefits: • Ubiquitous Access, Fault-Recovery • Problems/Issues: • Similar problems with (1,N,1) • However, NEMO can support the case when each NEMO-Prefix is only registered with one home agent 59th IETF – NEMO Working Group

  13. HA INTERNET MR-2 MR-1 P P MNN MNN (N,1,1): N MRs, 1 HA, 1 Prefix • Scenario: • Multiple MRs • A Wireless-PAN with GPRS phone and 802.11 PDA • Benefits: • Load-Sharing, Ubiquity, Fault-Recovery • Problems/Issues: • None 59th IETF – NEMO Working Group

  14. HA INTERNET MR-2 MR-1 P2 P1 MNN MNN (N,1,N): N MRs, 1 HA, N Prefixes • Scenario: • Trains/ships with one MR in each car/cabin • Benefits: • Load Sharing • Problems/Issues: • None 59th IETF – NEMO Working Group

  15. HA-1 HA-2 INTERNET MR-2 MR-1 P P MNN MNN (N,N,1): N MRs, N HAs, 1 Prefix • Scenario: • Train/Ship with satellite dish and antenna to use ground-bases telecommunications infrastructure • Benefits: • Load-sharing, Fault-recovery • Problems/Issues: • Same issue as (1,N,1) where one NEMO-prefix is registered at two home-agents 59th IETF – NEMO Working Group

  16. HA-1 HA-2 INTERNET MR-2 MR-1 P2 P1 MNN MNN (N,N,N) Mobile Network • Scenario: • W-PAN with 802.11 PDA and GPRS Phone subscribing to different ISPs • Benefits: • Load-Sharing, Fault-Recovery, Ubiquitous Access • Problems/Issues: • Main problem is if a prefix is registered by more than one home-agent • NEMO can support the case when each NEMO-Prefix is only registered to one home-agent • Issue raised on burden of MNNs to remember which MR advertises which prefix 59th IETF – NEMO Working Group

More Related