NEMO Requirementsand Mailing List

Discussions/Conclusions

T.J. Kniveton - Nokia

Pascal Thubert - Cisco

IETF 54 – July 14, 2002

Yokohama, Japan

Requirements agreed thus far

Phase 1: Basic Support

• Provide continuous connectivity to mobile network nodes

• MNNs can be fixed or mobile (MIPv6 aware/unaware)

• MNNs do not require any NEMO-awareness

• Solutions leverage existing Mobile IPv6 capabilities

Phase 2: Advanced Support

• Route optimization between mobile networks

• Possible routing-based solution

• Multicast capabilities

• Other issues that may come up during Phase 1 implementation

Open (& Closed) Issues on mailing list (1)

• Charter• Consensus: Submitted charter represents intentions of

group

• Basing solution on IPv6• Consensus: Solution should be based on IPv6, and

leave open the possibility for MIPv4 compatible solution

• Amendment: Interest shown to complete Basic IPv4 support during this BOF could lead to charter item

• Basing solution on Mobile IP(v6)• Basic support utilitizes components of Mobile IPv6• Optimization/advanced may use other routing

solutions

• Nesting• Consensus: must be supported in solution

Mailing list issues, cont’d (2)

• Securing mobile network a la VPN• Securing packet traffic between MR and HA to

allow equivalent level of privacy for FNs as when MR at home

• Consensus: Can be solved using existing security

• Multihoming• Consensus: Multihoming is important and should

be addressed• MR vs. mobile network multihoming

• Scenario 1: Multiple egress interfaces on MR.• Scenario 2: Multiple MRs on a shared link: this implies multiple

mobile networks, and MRs must at least be aware of the prefix (in RA). Each mo.net. (prefix) is only owned by ONE MR.

• Consensus: MRs must, at the minimum, listen to other nodes’ RAs

• Transit networks not allowed

Mailing list issues, cont’d (3)

• Access Control• There are discussions on how to do access control• Consensus: Talks should continue, but not be

contained in the charter of the group.• Multicast

• Within the mobile network• Between access network and mobile network• Consensus: This is an issue that people are

interested in supporting.• MONET vs. MANET

• Consensus (already described in charter issue)• Interaction with other WGs

• Consensus: To incorporate other protocols and communicate requirements, WG chairs will handle communications with other groups

Mailing List Issues, cont’d (4)• Route Optimization

• Consensus: Basic solution will operate without Route optimization• Will be part of the advanced

solution (round 2)• Outside the mobile

network• Inside the nested mobile

network• MRs should be able to talk

directly, without using HAs• Signalling between parent and

child MRs• RR test might require

extension• MIPv6 CN impact• Correspondent Router

concept

MR3’s HA

MR2’s HA

MR1’s HATunnel

MR3

MR2

MR1

LFN1

Packets route

Access Router

Internet

CN1

Conclusion1. Requirements for BASIC case

• Consensus: Basic solutions in basic case will be based on reverse tunneling from MR to home agent, continuous connectivity

• Supporting FNs without NEMO support means reverse tunneling

• Solution uses MIPv6 components and is IPv6-only• Network transparency is required

• FNs and MNs must both be supported in mobile network• Solution should not restrict internal architecture of mobile net• Does not break existing protocols (I.e. AAA)• IPv6 solution is primary focus. Update: IPv4 support possible

2. Elements to compare solutions• Minimize control traffic to ease costly networks• Reasonable scalability characteristics

• MINTS vs. large networks like Bus or Plane• Affects on home agent should be minimized

• Extensibility to advanced features: route optim, multihoming,..• Reduced protocol overhead / Maximize bandwidth efficiency

Drafts• Requirements-related

• Draft-ersnt-monet-terminology-01.txt• Draft-ernst-monet-requiements-00.txt• Draft-lach-requirements-00.txt• Draft-kniveton-requirements-00.txt

Requirements drafts will be merged into one draft, to follow..

• Solutions proposals so far• Draft-ernst-mobileip-v6-network-03.txt• Draft-kniveton-mobrtr-02.txt• Draft-thubert-nemo-reverse-routing-header-00.txt• Draft-ietf-mobileip-hmipv6-05.txt

After requirements draft is finished, these drafts can be revised and more invited.