MONET Problem Scope and Requirements

1. MONET Problem Scopeand Requirements draft-kniveton-monet-requirements-00 T.J. Kniveton Alper Yegin IETF 53 21 March 2002

2. Introduction • These requirements are based on terminology in Ernst’s terminology draft and further discussions on MONET list • Changes from other drafts: • No distinction between local and visiting MNs, or local fixed router • Main entities: FH, FR, MH, MR, MN • View on requirements may be simplified but compatible with other requirements drafts • We are focused on solving IPv6 mobile network problems based on actual members’ requirements • We look at MIPv6 as a good starting point, and favor analysis of other protocols to exclude aspects already solved in other contexts

3. Problem Scope • Primary goal to allow MNNs to remain connected to the Internet and continuously reachable while MONET moves • MNNs could be either fixed on MONET, or mobile • Secondary goals to investigate effects of network mobility on MNNs’ communications • Routing protocol changes • Realtime traffic and fast handovers • Other optimizations and service aspects • Since this is within IETF purview, focus should remain on implementation-oriented solutions. Research can be redirected to IRTF and other appropriate venues

4. Non-goals • Host mobility (MIP) • Administration of Network • Address Assignment • Network Architectures (this may be open to discussion) • Service discovery solutions • Complicated abstract architectures

5. Security • MR has unique characteristics: security may be a hybrid of host and router • In subscriber case, MR may have limited power such as being delegated a prefix • MR may be part of trusted routing fabric • Trust relationship between MR and nodes on mobile network • Should be similar to fixed network R/N trust

6. Protocols • IPv6 is basis for defining mobile networks • IPv4 is not excluded from scope • but IPv6 is the requirement • Mobile IPv6 is probably the best starting pt • Already solves host mobility • Extensions should provide simplest path to achieve goals of MONET • Routing and addressing changes • Route optimization is desirable but secondary • P.S. there are proposed solutions and implementations for MONET, but..let’s not talk about that yet

7. Architectural Suggestions • Supporting nesting is desirable • Transit networks are excluded • To keep clear distinction from MANET • Multi homing is allowed • Infrastructure-less route optimization is desirable but secondary – security issues need to be solved first

8. A Network AR1 This is not a MANET. Fixed Internet. Rtr MN FN Rtr

9. MONET Should Solve: AR2 AR1 Fixed Infr. • MONET solves the area in the green blob  • How can a router traverse the fixed infrastructure and bring a static, semi-static, or dynamic subnetwork with it, so that packets still arrive for that net? MR A network Using a prefix.

10. A MONET 1 AR2 AR1 Fixed Infr. MR A moving network. The nodes in the network do not need to be aware that its point of attachment to fixed topology has changed. This is still not a MANET. (For the same reason Mobile IP is not a case of MANET). MN FN Rtr

11. A MONET 2 (This slide wasn’t presented during MONET BOF) AR2 AR1 Fixed Infr. MR The MR is routing to nodes inside its moving network, which happen to be communicating with eachother using MANET proto. MR’s association with the fixed infrastructure and movement of MANET prefixes still not a MANET. MANET MaR MaR MaR

12. Thank you. draft-kniveton-monet-requirements-00 T.J. Kniveton <timothy.kniveton@nokia.com> Alper Yegin <alper@docomolabs-usa.com>