Network Mobility (nemo) ----------------------- Charter Last Modified: 2007-06-15 Current Status: Active Working Group Chair(s): Thierry Ernst TJ Kniveton Internet Area Director(s): Jari Arkko Mark Townsley Internet Area Advisor: Jari Arkko Technical Advisor(s): Steven Bellovin Mailing Lists: General Discussion:nemo@ietf.org To Subscribe: nemo-request@ietf.org Archive: http://www.ietf.org/mail-archive/web/nemo/index.html Description of Working Group: The NEMO Working Group is concerned with managing the mobility of an entire network, which changes its point of attachment to the Internet and thus its reachability in the network topology. The mobile network includes one or more mobile routers (MRs) which connect the rest of the mobile network to the global Internet. For the purposes of this working group, a mobile network is a leaf network; it does not carry transit traffic. Nonetheless, it could be multihomed, either with a single MR that has multiple attachments to the Internet, or by using multiple MRs that attach the mobile network to the Internet. For the basic NEMO support case, none of the nodes behind the MR need be aware of the network's mobility; thus, the network's movement is completely transparent to the nodes inside the mobile network. This design consideration was made to accommodate nodes inside the network that are not generally aware of mobility. Basic network mobility support is described in RFC 3963. This RFC contains NEMO Basic Support, which is a protocol based on Mobile IPv6 (RFC 3775, 3776) that enables network mobility in an IPv6 network. The working group is tasked with continuing to evolve RFC 3963 to correct errors and maintain the specification. In addition, the group works in co-operation with the MIP6 WG to design a mechanism to allow mixed IPv4/IPv6 networks to be used. At this point, the working group is concerned with solving deployment issues of NEMO, primarily relating to the identified needs of the automotive and aviation communities. The group will gather requirements from those builders and users, and then solve the route optimization issues necessary for optimized deployments. Among the deployments that have issues which may be solved by NEMO Route Optimization feature(s), we have identified three cases that have a likelihood of requirements gathering and an Optimization solution. These are called the Aviation case, the Automotive case, and the Personal Mobile Router (consumer electronics) case, though the actual technical problems are characterized by the type of movements and environments more than by the specific industry using the technology. The group will explore these cases to gather requirements and, if those requirements match the capability of a NEMO RO solution space, proceed with solving the open issues. The WG will: - Finish working group documents that are currently in process, and submit for RFC. This includes prefix delegation protocol mechanisms, a multihoming problem statement, and a MIB for NEMO Basic Support. - Gather requirements for NEMO Route Optimization in deployment scenarios: (1) Airline and spacecraft community, who are deploying NEMO for control systems, as well as Internet connectivity and entertainment systems. This use case is characterized by fast (~ 1000 km/h) moving objects over large distances (across continents). The main technical problem is that tunneling-based solutions imply a roundtrip to another continent and that BGP based solutions imply significant churn in the global Internet routing table. (2) Automotive industry who are deploying NEMO for in-car communication, entertainment, and data gathering, possible control systems use, and communication to roadside devices. This use case is characterized by moderately fast (~ 100-300 km/h) moving objects that employ local or cellular networks for connectivity. (3) Personal Mobile Routers, which are consumer devices that allow the user to bring a NEMO network with the user while mobile, and communicate with peer NEMO networks/MNNs. After gathering the requirements for these types of deployments, the working group will evaluate what type of route optimization needs to be performed (if any), and formulate a solution to those problems. If no requirements for those scenarios can be collected by the deadline, it will be assumed that the work is premature, and that type of deployment will be dropped from the list of use cases currently addressed by NEMO. The group will only consider airline and spacecraft solutions that combine tunneling solutions for small movements with either federated tunnel servers or slowly changing end host prefixes. The group will only consider personal mobile router requirements about optimized routes to another mobile router belonging to the same operator. The group will only consider automotive industry requirements to allow MR-attached hosts to directly access the network where MR has attached to. Work on automotive and personal mobile router solutions requires rechartering. The WG will not: - consider routing issues inside the mobile network. Existing routing protocols (including MANET protocols) can be used to solve these problems. - consider general route optimization, multihoming, or other problems that are not related to the deployment and maintenance of NEMO networks. - consider or rely on the results of general routing architecture, Internet architecture, or identifier-locator split issues that are discussed in separate, long term efforts elsewhere in the IETF - consider solutions that require changes from correspondent nodes in the general Internet The working group will endeavor to separate research issues, and refer them to the IRTF as appropriate. Goals and Milestones: Done Submit terminology and requirements documents (for Basic support). Done Submit NEMO Basic Support to IESG Done Submit WG draft -00 on Threat Analysis and Security Requirements for NEMO. Done Submit WG draft -00 on Multihoming Problem Statement Done Submit WG draft -00 on NEMO Basic Support Usages Done Submit WG draft -00 on Prefix Delegation for NEMO Done Submit WG draft -00 on MIB for NEMO Basic Support Done Submit WG draft -00 on Analysis of the Solution Space for Route Optimization Done Submit Terminology as Informational to IESG Done Submit Goals and Requirements as Informational to IESG May 2007 Submit the final doc Multihoming Problem Statement to the IESG, for Informational May 2007 Submit the final doc on MIB for NEMO Basic Support to the IESG, for Proposed Standard Done Submit the final doc on Prefix Delegation for NEMO to the IESG, for Proposed Standard Jul 2007 Submit -00 draft on Route Optimization Needs for Aircraft and Spacecraft Deployments Jul 2007 Submit -00 draft on Route Optimization Needs for Automobile and Highway Deployments Jul 2007 Submit -00 draft on Route Optimization needs for Personal Mobile Router Sep 2007 Submit -00 draft for solution to aircraft/spacecraft problem Nov 2007 Submit final doc on Route Optimization Needs for Aircraft and Spacecraft Deployments, for Informational Nov 2007 Submit final doc on Route Optimization Needs for Automobile and Highway Deployments, for Informational Nov 2007 Submit final doc on Route Optimization needs for Personal Mobile Router, for Informational Dec 2007 Determine how to proceed with remaining automotive/Personal Mobile Router solutions Dec 2007 Recharter to work on the remaining automotive/Personal Mobile Router solutions Jan 2008 Submit final doc for solution to aircraft/spacecraft problem to the IESG, for Proposed Standard Jun 2008 Shut down or recharter the WG to solve further identified topics Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Feb 2003 Nov 2006 Network Mobility Support Goals and Requirements May 2003 Nov 2006 Network Mobility Support Terminology Apr 2004 Feb 2006 NEMO Home Network models Jul 2004 Feb 2007 Analysis of Multihoming in Network Mobility Support Oct 2004 Jul 2007 NEMO Management Information Base Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC3963Standard Jan 2005 Network Mobility (NEMO) Basic Support Protocol RFC4889 I Jul 2007 Network Mobility Route Optimization Solution Space Analysis RFC4888 I Jul 2007 Network Mobility Route Optimization Problem Statement