Mobile Networks BOF (monet) Thursday, March 21 at 1300-1500 ================================ CHAIRS: Hesham Soliman Thierry Ernst o DESCRIPTION OF THE BOF: ======================= The purpose of host mobility support is to provide continuous Internet access to mobile hosts. In contrast to host mobility support, network mobility support is concerned with situations where an entire network changes its point of attachment to the Internet and thus its reachability in the topology. We shall refer to such a network as a mobile network (MONET). Network mobility can occur in many different scenarios, including networks of sensors deployed in trains, busses, boats, planes, and Personal Area Networks (PANs). Sensors are typically used to collect information in the mobile network (air pressure, temperature, ...) and may need to communicate this information not only to a server on board the mobile network, but also to servers in the Internet. Meanwhile, a number of Internet appliances deployed in the mobile network are used to collect traffic and navigation data from the Internet. In addition, the mobile network deployed in a train or a bus may also provide Internet connectivity to the passengers that may wish to connect their mobile phone, laptop or the PAN they carry on themselves. The purpose of network mobility support is to provide continuous Internet access to all nodes located in the mobile network for different types of mobile network. The scenarios outlined above would significantly affect the problem definition and raise a number of new addressing, routing, and security issues that have not yet been considered by traditional work on mobility support, as this BOF will try to prove. Several problems will be considering during this BOF, for instance: - A PAN scenario would, in most cases, imply a small number of devices, on a single subnet and likely to be owned by a single entity. On the other hand, mobile networks on a bus represent a different set of problems. Such instance may in some cases contain severals subnets and a potentially large number of nodes belonging to distinct entities. Several PANs may also exist, connected to one or more Mobile Routers (MRs) on the bus, forming nested mobile networks with several subnets. This questions how different levels of mobility could be handled, how lower levels could be granted access to the Internet via the top-level mobile network, and how multiple dog-leg routing could be avoided. - Another dimension of the problem can be seen when considering the speed of mobility. A mobile network on a bus or a train is likely to experience frequent IP handovers, when compared with a mobile network on a plane, connected by satellite to a ground station. The frequency of movement will add certain restrictions on decisions related to allocating addresses to a mobile network, as well as, controlling the frequency of updates. - The number of nodes within a mobile network will certainly affect the mobility management scheme (e.g. the number of updates to be sent when MR(s) change their point of attachment within the topology), and whether they should be aggregated (sent by a single entity on behalf of the network) or not. The pre-BOF meeting held at 52th IETF Salt Lake City shown that there is a strong interest in the IETF community to work on such issues. It is therefore the object of this BOF to define a work context that describes the goal we want to achieve and limits the scope of our study. We must then identify what constraints limit the implementation and the deployment of a potentially and ideally good solution, and what requirements solutions must comply to. The work on network mobility support may span and monitor progress and place requirements on other working groups, including, but not limited to: IPv6, IPSec, MobileIP, PANA, AAA, and possibly SeaMoby and MANET WGs. o The BOF's goals are: =================== - Show concrete instances of mobile networks in order to show why network mobility support is needed. - Assess interest in forming a Working Group on Network Mobility Support - Get feedback on the problem statement, which could be used as the basis for a Working Group Charter. The discussion of the problem statement on the mailing list is recommended prior to the BOF. The BOF will be used to get feedback for the next steps. - Reach consensus on the terminology to be used for Mobile Networks. A discussion on terminology on the mailing list is recommended to speed up the process of reaching consensus. - Outline a number of requirements that must or should be met by the solutions for supporting different scenarios of Mobile Networks. A discussion on the mailing list in order to identify the commonality and differences in the listed requirements is necessary. - Outline security issues peculiar to Network Mobility Support - Discuss the focus of the group: IPv6 only, or both: IPv4 and IPv6 o MONET BOF AGENDA (53th IETF Minneapolis) ======================================== - Introduction and agenda bashing 5 min - Network Mobility Support Terminology - 10 min Thierry Ernst (WIDE/INRIA) draft-ernst-monet-terminology-00.txt - Problem Statement and Scope - 30 min Hesham Soliman (Ericsson) draft-soliman-monet-scope-00.txt - Common Requirements - 30 min Thierry Ernst (WIDE/INRIA) draft-ernst-monet-requirements-00.txt - Requirements from the Public Safety arena (MESA) - 15 min John Boot (Motorola) - Scenarios, Scope and Requirements - 15 min Christophe Janneteau (Motorola) draft-lach-monet-requirements-00.txt - Problem Scope and Requirements - 15 min TJ Kniveton (Nokia) draft-kniveton-monet-reqs-00.txt - Security Issues - 10 min James Kempf (Docomo Labs) - General discussion and opinions on moving forward - All 20 min o DELIVERABLES ============ - Consensus on Terminology: March 02 - Definition of Problem Scope: March 02 - Common Requirements: Spring 02 - Evaluation of MIPv6 (+ MIPv4 ?) shortcomings and their ability to meet the requirements: July 02 o MONET WEB PAGE: ============== http://www.nal.motlabs.com/monet o MAILING LIST: ============= monet@nal.motlabs.com General information about the mailing list: http://www.nal.motlabs.com/mailman/listinfo/monet To subscribe: visit http://www.nal.motlabs.com/mailman/listinfo/monet