Download IETF presentation monami

ACP-SWGN1-10/WP-Ivancic
International Civil Aviation Organization
13 Nov 2006
WORKING PAPER
AERONAUTICAL COMMUNICATIONS PANEL (ACP)
10th MEETING OF SUB-WORKING GROUP N-1
Montreal, Canada 13-17 November 2006
Agenda Item TBD: Internet Engineering Task Force presentation to working groups on
network mobility
MULTI-HOMED MOBILE PLATFORMS – 67TH IETF PRESENTATION
(Presented by William Ivancic)
SUMMARY
The referenced document is a presentation given at the 67th Internet
Engineering Task Force meeting to the Networks in Motion (nemo) and
MObile Networks and Multiple Interfaces for IPv6
(monami6) working
groups regarding requirements for multi-domained, multi-homed mobile
platforms
ACTION
It is highly recommended It is highly recommended that ICAO encourage
member states and the aeronautics community to participate in the various
Internet Engineering Task Force working groups addressing issues related to
network mobility in order to have their concerns heard and addressed.
The nemo working group is rechartering and will specifically be addressing
requirements of the aeronautics and automotive industries. It is imperative
that the aviation industry participate NOW as the deadline for having a
requirements document is March/April of 2007. Failure to produce such a
document will result in that item being dropped from the charter due to lack of
interest.
(4 pages)
ACP-SWGN1-10/WP- Multi-Homed Mobile Platforms – 67th IETF Presentation
-2-
1.
ACP-SWGN110/WP- Multi-Homed Mobile
Platforms – 67th IETF Presentation
INTRODUCTION
1.1
The document, “IETF67nemo-monami6-final”, is a presentation given at the 67th Internet
Engineering Task Force meeting to the Networks in Motion (nemo) and MObile Networks and Multiple
Interfaces for IPv6 (monami6) working groups regarding requirements for multi-domained, multi-homed
mobile platforms
2.
DISCUSSION
2.1
This document describes numerous problems associated with deployment of multi-homed
mobile platforms consisting of multiple networks and traversing large geographical areas.
It is a
summary of two Internet Drafts: “Multi-Domained, Multi-Homed Mobile Networks,” and “Aviation
Global Internet Operations Requirements.”
These Internet Drafts can be found at:
http://roland.grc.nasa.gov/~ivancic/papers_presentations/2006/draft-ivancic-mobile-platforms-problem00.txt , and http://www.ietf.org/internet-drafts/draft-davis-aviationreq-00.txt
In addition, a website and mail list has been setup for discussion and to easily disseminate information on
this topic. The URL for the web site follows. Information on the mail list is available on the web site.
http://www.multicasttech.com/mpi/
2.2
below:
The latest proposed charter for the Networks in Motion (nemo) working group is shown
Proposal for new NEMO Charter
Version: November 2, 2006
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 accomodate nodes inside the network
that are not generally aware of mobility.
Basic network mobility support is described in RFC 3963. This RFC
-3-
ACP-SWGN110/WP- Multi-Homed Mobile
Platforms – 67th IETF Presentation
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 address deployment issues. In addition, the group
will design a mechanism to allow mixed IPv4/IPv6 networks, carrying
signalling messages that describe both IPv4 and IPv6 addresses and
mobile network prefixes. The latter task is shared with the Mobile
IPv6 working group, addressed by a joint design team. Finally, the
group may work on topics that arise around network mobility, to
address needed protocol design.
At this point, the working group is concerned with solving deployment
issues of NEMO, primarily relating to the identified needs of the
automotive and flying communities. The group will gather requirements
from those builders and users, and then solve the route optimization
issues necessary for optimized deployments.
The WG will:
- Finish working group documents that are currently in process, and
submit for RFC.
- Gather requirements for NEMO Route Optimization in deployment
scenarios.
- Automotive industry who are deploying NEMO for in-car
communication, entertainment, and data gathering, possible
control systems use, and communication to roadside devices.
- Airline and spacecraft community, who are deploying NEMO for
control systems, as well as Internet connectivity and
entertainment systems.
- 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 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.
The working group will endeavor to separate research issues, and refer
them to the IRTF as appropriate.
-4-
ACP-SWGN110/WP- Multi-Homed Mobile
Platforms – 67th IETF Presentation
Goals and Milestones:
May 2006
Nov
Nov
Nov
Nov
Nov
2006
2006
2006
2006
2006
Dec 2006
Dec 2006
Apr 2007
May 2007
Jul 2007
Aug 2007
Mar 2008
3.
Finish draft on Threat Analysis and Security
Requirements for NEMO.
Submit Terminology as Informational to IESG
Submit Goals and Requirements as Informational to IESG
Submit final doc Multihoming Problem Statement
Submit final doc on NEMO Basic Support Usages
Submit final doc(s) on Analysis of the Solution Space
for Route Optimization
Submit final doc on MIB for NEMO Basic Support
Submit final doc(s) on Prefix Delegation for NEMO
Submit -00 draft on Route Optimization Needs for
Aircraft and Spacecraft Deployments
Submit -00 draft on Route Optimization Needs for
Automobile and Highway Deployments
Submit -00 draft for solution to aircraft/spacecraft
problem
Submit -00 draft for solution to automotive problem
Shut down or recharter the WG to solve further
identified topics
ACTION BY THE MEETING
3.1
It is highly recommended that ICAO encourage member states and the aeronautics
community to participate in the various Internet Engineering Task Force working groups addressing
issues related to network mobility in order to have their concerns heard and addressed.
3.2
The nemo working group is rechartering and will specifically be addressing requirements
of the aeronautics and automotive industries. It is imperative that the aviation industry participate NOW
as the deadline for having a requirements document is March/April of 2007. Failure to produce such a
document will result in that item being dropped from the charter due to lack of interest.
3.3
Working groups that are working area of interest to ICAO, its member states and the
aeronautics community include:







Mobility for IPv4 (mip4)
Mobility for IPv6 (mip6)
Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop)
Mobile Nodes and Multiple Interfaces in IPv6 (monami6)
Network Mobility (nemo)
Network-based Localized Mobility Management (netlmm)
Networks in Motion (nemo)