< draft-ernst-monet-terminology-00.txt		draft-ernst-monet-terminology-01.txt >
	IETF INTERNET-DRAFT Thierry Ernst		IETF INTERNET-DRAFT Thierry Ernst
	WIDE Project / INRIA		WIDE Project and INRIA
	Hong-Yon Lach		Hong-Yon Lach
	Motorola Labs		Motorola Labs
	February 2002		July 2002
	Network Mobility Support Terminology		Network Mobility Support Terminology
	draft-ernst-monet-terminology-00.txt		draft-ernst-monet-terminology-01.txt
	Status of This Memo		Status of This Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that other		Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Abstract		Abstract
	The purpose of traditional mobility support is to provide continuous		This document proposes a terminology for defining the problem faced
	Internet connectivity to mobile hosts (host mobility support). In		by network mobility. Network mobility is concerned with situations
	contrast, network mobility support is concerned with situations where		where an entire network changes its point of attachment to the
	an entire network changes its point of attachment to the Internet and		Internet and thus its reachability in the topology. We shall refer to
	thus its reachability in the topology. We shall refer to such a		such a network as a mobile network. Network mobility support is to
	network as a mobile network (MONET). There is presently no existing		maintain session continuity between nodes in the mobile network and
	terminology to define the issues, goals, architecture elements,		nodes in the global Internet.
	problems and requirements pertaining to network mobility support, but
	one is needed. It is therefore the object of this document to define
	a new terminology, to depict the characteristics of mobile networks
	and to make some observations.
	Contents		Contents
	Status of This Memo		Status of This Memo
	Abstract		Abstract
	1. Introduction		1. Introduction
	2. Terminology		2. Terminology
	2.1. Architecture Components		2.1. Architecture Components
	2.2. Other Terminology		2.2. Nested Mobility
			2.3. Miscellaneous Terms
	3. Characteristics / Observations		3. Characteristics / Observations
			4. Changes since last version of the draft
	Acknowledgments		Acknowledgments
	References		References
	Author's Addresses		Author's Addresses
	1. Introduction		1. Introduction
	The purpose of traditional mobility support is to provide continuous		A mobile network is an entire network, moving as a unit, which
	Internet connectivity to mobile hosts (host mobility support). In		changes its point of attachment to the Internet and thus its
	contrast, network mobility support is concerned with situations where		reachability in the topology. A mobile network may be composed by one
	an entire network changes its point of attachment to the Internet and		or more IP-subnets and is connected to the global Internet via one or
	thus its reachability in the topology. We shall refer to such a		more Mobile Routers (MR). Nodes behind the MR primarily comprise
	network as a mobile network (MONET).		fixed nodes (nodes unable to change their point of attachment while
			maintaining ongoing sessions), and additionally mobile nodes (nodes
			able to change their point of attachment while maintaining ongoing
			sessions). The internal configuration of the mobile network is
			assumed to be relatively stable with respect to the MR.
			If network mobility is not explicitly supported by some mechanisms
			once a MR changes its point of attachment, existing sessions between
			CNs and nodes behind the MR are broken, and connectivity to the
			global Internet is lost. In addition, fixed nodes behind the MR may
			experiment dog-leg routing, whereas multiple levels of mobility may
			cause multiple dog-leg routing. Traditional work on mobility support
			as conducted in the Mobile IP working group is to provide continuous
			Internet connectivity to mobile hosts only (host mobility support)
			and are unable to support network mobility. It is thus proposed to
			create a NEMO working group that would specify solutions for network
			mobility support (the proposed name for the working group was renamed
			from MONET to NEMO).
	Cases of mobile networks include networks attached to people		Cases of mobile networks include networks attached to people
	(Personal Area Network or PAN, i.e. a network composed by all		(Personal Area Network or PAN, i.e. a network composed by all
	Internet appliances carried by people, like a PDA, a mobile phone, a		Internet appliances carried by people, like a PDA, a mobile phone, a
	digital camera, a laptop, etc.) and networks of sensors deployed in		digital camera, a laptop, etc.) and networks of sensors deployed in
	aircrafts, boats, busses, cars, trains, etc. An airline company that		aircrafts, boats, busses, cars, trains, etc. An airline company that
	provides permanent on-board Internet access is an example of a mobile		provides permanent on-board Internet access is an example of a mobile
	network. This allows passengers to use their laptops (this scenario		network. This allows passengers to use their laptops (this scenario
	is mentioned in [Tanenbaum96] under section 1.2.4 and section 5.5.8;		is mentioned in [Tanenbaum96] under section 1.2.4 and section 5.5.8;
	[Perkins98] under section 5.12; [Solomon98] under section 11.2; and		[Perkins98] under section 5.12; [Solomon98] under section 11.2; and
	skipping to change at page 3, line 28 ¶		skipping to change at page 3, line 48 ¶
	(network management, security, performance,...), it is desirable to		(network management, security, performance,...), it is desirable to
	interconnect the Internet appliances deployed in cars, trains, busses		interconnect the Internet appliances deployed in cars, trains, busses
	by means of, for instance, an Ethernet cable, instead of connecting		by means of, for instance, an Ethernet cable, instead of connecting
	them individually and directly to the Internet, therefore exhibiting		them individually and directly to the Internet, therefore exhibiting
	the need to displace an entire network.		the need to displace an entire network.
	To describe such kind of scenarios, we need to agree on a		To describe such kind of scenarios, we need to agree on a
	terminology. However, there is presently no existing terminology to		terminology. However, there is presently no existing terminology to
	define the issues, goals, architecture elements, problems and		define the issues, goals, architecture elements, problems and
	requirements pertaining to the scenarios outlined here above, but one		requirements pertaining to the scenarios outlined here above, but one
	is needed. It is therefore the object of this document to define such		is needed. It is therefore the object of this document to propose
	a new terminology and to make some observations. The material		such a new terminology and to highlight some characteristics of
	presented in this document is based on [Ernst01] and on our former		mobile networks.
	internet-draft that was submitted in July 2001 [OLD-draft] for the
	consideration of the Mobile IP Working Group. In addition to the		The material presented in this document is based on [Ernst01] and on
	present terminology, this former draft was also presenting a set of		our former internet-draft that was submitted in July 2001 [OLD-draft]
	requirements and issues as an attempt to clarify the problem caused		for the consideration of the Mobile IP Working Group. In addition to
	by networks in motion. We decided to split this former document in		the present terminology, this former draft was also presenting a set
	two because requirements are more subject to discussion and		of requirements and issues as an attempt to clarify the problem
	disagreements that the terminology on which we must agree on to base		caused by network mobility. We decided to split this former document
			in two because requirements are more subject to discussion and
			disagreements than the terminology on which we must agree on to base
	our discussion. Our proposed requirements can therefore now be found		our discussion. Our proposed requirements can therefore now be found
	in [REQUIREMENTS]. Additional requirements may be found in		in [REQUIREMENTS-1]. Additional requirements may be found in
	[REQUIREMENTS-NOKIA] and [REQUIREMENTS-MOTOROLA]. A comprehensive		[REQUIREMENTS-2] and [REQUIREMENTS-3]. A comprehensive description of
	description of the problem and issues posed by networks in motion is		the problem and issues posed by network mobility is discussed in
	discussed in [SCOPE]. More information may be found on the MONET web		[SCOPE]. More information may be found on the MONET web page [WEB-
	page [WEB-MONET].		MONET].
	2. Terminology		2. Terminology
	Our proposed terminology defines a number of new terms in conformance		The new terms we introduce comply with the terminology already
	with the terminology already defined in the IPv6 [RFC2460] and Mobile		defined in the IPv6 [RFC2460] and Mobile IPv6 [MIPv6] specifications.
	IPv6 [MIPv6] specifications. Note that our terminology is primarily		Although our terminology is primarily targeted toward IPv6, it is not
	targeted to IPv6, but is not limited to it. The first section defines		necessarily limited to it. This list comprises terms that appeared on
	the architecture components, and the second section defines a number		the mailing list for the purpose of explaining the problem scope.
	of other terms useful to discuss requirements.		Some of them may only be useful for the purpose of defining the
			problem scope and functional requirements of network mobility
			support. Definitions will have to be refined once we agree on the
			problem scope.
			The first section introduces terms to define the architecture
			components; the second introduces terms to discuss nested mobility;
			the last section introduces a number of other terms useful to discuss
			requirements.
	2.1. Architecture Components		2.1. Architecture Components
	Mobile Network (MONET)		Mobile Network
	A set of nodes composed by one or more IP-subnets attached to a		An entire network, moving as a unit, which dynamically changes its
	mobile router (MR) and mobile as a unit, with respect to the rest		point of attachment to the Internet and thus its reachability in
	of the Internet, i.e. a MR and all its attached nodes. The MR		the topology. The mobile network is connected to the global
	changes dynamically its point of attachment to the Internet and		Internet via one or more mobile router(s) (MR). The internal
	thus its reachability in the Internet.		configuration of the mobile network is assumed to be relatively
			stable with respect to the MR and is not a matter of concern.
	Mobile IP-subnet		Mobile Network Node (MNN)
			Any host or router located within the mobile network, either
			permanently or temporarily. A MNN could be any of a MR, LFN, VMN,
			or LMN. The distinction between LFN, LMN and VMN is necessary to
			discuss issues related to mobility management and access control,
			but does not preclude that mobility should be handled differently.
			Nodes are classified according to their function and capabilities.
	A MONET composed of a single IP-subnet.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	skipping to change at page 4, line 47 ¶		skipping to change at page 5, line 35 ¶
	| MR | Mobile Router		| MR | Mobile Router
	|____|		|____|
	_________|_______ internal		_________|_______ internal
	__|__ __|__ link		__|__ __|__ link
	| | | |		| | | |
	| MNN | | MNN | Mobile Network Nodes		| MNN | | MNN | Mobile Network Nodes
	|_____| |_____|		|_____| |_____|
	Figure 1: Terminology		Figure 1: Terminology
	Mobile Network Node (MNN)		Mobile Router (MR)
	Any host or router located within the MONET, either permanently or		A router which changes its point of attachment to the Internet and
	temporarily. A MNN could be any of a MR, LFN, VMN, or LMN. The		which acts as a gateway to route packets between the mobile
	distinction between LFN, LMN and VMN is necessary to discuss		network and the rest of the Internet. The MR is NEMO-enabled and
	issues related to mobility management and access control, but does		maintains the Internet connectivity for the mobile network. It has
	not preclude that mobility should be handled differently.		at least two interfaces, an egress interface, and an ingress
			interface. When transmitting a packet to the Internet (i.e.
			outside), it forwards it through the egress interface; when
			transmitting it withing the mobile network (i.e. inside), it
			forwards it through the ingress interface.
	Mobile Router (MR)		Local Fixed Node (LFN)
			A standard IPv6 node, either a host (LFH) or a router (LFR), that
			belongs to the mobile network and which has no mobility support
			capabilities at all (i.e. it isn't NEMO-enabled nor
			MIPv6-enabled).
	A router which attaches the MONET to the rest of the Internet. The
	MR maintains the Internet connectivity for the MONET. It is used
	as a gateway to route packets between the MONET and the Internet.
	The MR has at least two interfaces, an egress interface, and an
	ingress interface. When transmitting a packet to the Internet
	(i.e. outside), it sends it through the egress interface; when
	transmitting it withing the MONET (i.e. inside), it sends it
	through the ingress interface.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	skipping to change at page 5, line 47 ¶		skipping to change at page 6, line 36 ¶
	| __|__ __|__ link 1		| __|__ __|__ link 1
	_____ | | | | |		_____ | | | | |
	| |__| | LFN | | LMN |		| |__| | LFN | | LMN |
	| LFN | | |_____| |_____|		| LFN | | |_____| |_____|
	|_____| |		|_____| |
	| internal		| internal
	link 2		link 2
	Figure 2: Larger Mobile Network with 2 subnets		Figure 2: Larger Mobile Network with 2 subnets
	Local Fixed Node (LFN)		Local Mobile Node (LMN)
	A node permanently located within the MONET and that does not		A mobile node, either a host (LMH) or a router (LMR), that belongs
	change its point of attachment. A LFN can either be a LFH (Local		to the mobile network (i.e. its home link is within the mobile
	Fixed Host) or a LFR (Local Fixed Router).		network). It is MIPv6-enabled and may be NEMO-enabled.
	Local Mobile Node (LMN)		Visiting Mobile Node (VMN)
	A mobile node that belongs to the MONET and that changes its point		A mobile node, either a host (VMH) or a router (VMR), that doesn't
	of attachment from a link within the mobile network to another		belong to the mobile network (i.e. its home link is not within the
	link within or outside the MONET (the home link of the LMN is a		mobile network), and which gets attached to a link within the
	link within MONET). A LMN can either be a LMH (Local Mobile Host)		mobile network and obtains an address on that link. It is
	or a LMR (Local Mobile Router).		MIPv6-enabled and may be NEMO-enabled.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	skipping to change at page 6, line 44 ¶		skipping to change at page 7, line 36 ¶
	| _____ | | |		| _____ | | |
	| | |__| | LFN |		| | |__| | LFN |
	| | LFN | | |_____| |		| | LFN | | |_____| |
	| |_____| | |		| |_____| | |
	| | internal |		| | internal |
	| link 2 |		| link 2 |
	|------------------------------|		|------------------------------|
	Figure 3: LMN changing subnet		Figure 3: LMN changing subnet
	Visiting Mobile Node (VMN)
	A mobile node that does not belong to the MONET and that changes
	its point of attachment from a link outside the MONET to a link
	within the MONET (the home link of the VMN is not a link within
	the MONET). A VMN that attaches to a link within the MONET obtains
	an address on that link. A VMN can either be a VMH (Visiting
	Mobile Host) or a VMR (Visiting Mobile Router).
	Top-Level Mobile Router (TLMR)
	In case there are more MONETs aggregated into the MONET, the TLMR
	is the MR(s) used to direcly connect the aggregated MONET to the
	fixed Internet.
	Node behind the MR		Node behind the MR
	Any MNN in a MONET that is not a MR for this MONET.		Any MNN in a mobile network that is not a MR for this mobile
			network.
	Correspondent Node (CN) of a MONET		Correspondent Node (CN)
	Any node located outside the MONET that is communicating with one		Any node that is communicating with one or more MNNs located in
	or more MNNs. CNs corresponding with MNNs located in the same		the same mobile network. A CN could itself be located within the
	MONET are said to be CNs of this MONET.		mobile network.
	Access Router (AR)		Access Router (AR)
	Any subsequent point of attachment of the MONET at the network		Any subsequent point of attachment of the MR at the network layer.
	layer. Basically, a router on the home link or the foreign link.		Basically, a router on the home link or the foreign link.
	When considering nested mobility, an AR seen by the MONET may be a
	MR or a LFR for the entire network.
	Home subnet prefix		Home subnet prefix
	A bit string that consists of some number of initial bits of an IP		A bit string that consists of some number of initial bits of an IP
	address which identifies the home link within the Internet		address which identifies the MR's home link within the Internet
	topology (i.e. the IP subnet prefix corresponding to the mobile		topology (i.e. the IP subnet prefix corresponding to the mobile
	node's home address, as defined in [MIPv6]).		node's home address, as defined in [MIPv6]).
	Foreign subnet prefix		Foreign subnet prefix
	A bit string that consists of some number of initial bits of an IP		A bit string that consists of some number of initial bits of an IP
	address which identifies a foreign link within the Internet		address which identifies the MR's foreign link within the Internet
	topology.		topology.
	Mobile Network Prefix		Mobile Network Prefix
	A bit string that consists of some number of initial bits of an IP		A bit string that consists of some number of initial bits of an IP
	address which identifies a MONET within the Internet topology.		address which identifies the entire mobile network within the
	Nodes belonging to the MONET (i.e. at least MR, LFNs and LMNs)		Internet topology. All MNNs necessarily have an address named
	share the same IPv6 "network identifier". For a single mobile IP-		after this prefix.
	subnet, the Mobile Network Prefix is the "network identifier" of
	this subnet.
	Egress Interface of a MR		Egress Interface of a MR
	The interface attached to the home link if the MONET is at home,		The interface attached to the home link if the MR is at home, or
	or attached to a foreign link if the MONET is in a foreign		attached to a foreign link if the MR is in a foreign network.
	network.
	Ingress Interface of a MR		Ingress Interface of a MR
	The interface attached to a link inside the MONET. This interface		The interface attached to a link inside the mobile network. This
	is configured with the Mobile Network Prefix.		interface is configured with the Mobile Network Prefix.
			The terminology is summarized in fig.1 to 3. Fig.1 shows a single
			mobile subnetwork. Fig.2. shows a larger mobile network comprising
			several subnetworks. Fig.3 illustrates a LMN changing its point of
			attachment within the mobile network.
			2.2. Nested Mobility
			We speak about nested mobility when there are more than one level of
			mobility, i.e. when a VMN gets attached to the mobile network. A MNN
			acts as an Access Router for this VMN.
			If the VMN is actually a VMR with nodes behind it, this is a mobile
			network which gets attached to a larger mobile network. The former is
			a sub-MONET, and the latter the parent-MONET. It is generally
			assumed that the sub-MONET and the parent-MONET become a single
			aggregated mobile network, i.e. the sub-MONET is indeed a subservient
			of the larger MONET in terms of getting address space.
			The MR(s) used to directly connect the aggregated mobile network to
			the fixed Internet is referred to as the Top-Level Mobile Router
			(TLMR) The terms upstream-MONET, downstream-MONET, and root-MONET
			have also been introduced.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	skipping to change at page 8, line 39 ¶		skipping to change at page 9, line 40 ¶
	| | |__| |____|		| | |__| |____|
	----------> | VMN | | __|_____________ internal		----------> | VMN | | __|_____________ internal
	|_____| | __|__ __|__ link 1		|_____| | __|__ __|__ link 1
	_____ | | | | |		_____ | | | | |
	| |__| | LFN | | LMN |		| |__| | LFN | | LMN |
	| LFN | | |_____| |_____|		| LFN | | |_____| |_____|
	|_____| |		|_____| |
	| internal		| internal
	link 2		link 2
	Figure 4: Nested Mobility: Visiting Mobile Node (VMN)		Figure 4: Nested Mobility: single VMN that attaches to a mobile network
	The terminology is summarized in fig.1 and to 5. Fig.1 shows a single
	mobile IP-subnet. Fig.2. shows a large mobile network. Fig.3
	illustrates a LMN changing subnet within the mobile network whereas
	fig.4 illustrates the case of a VMN that enters the mobile network.
	Fig 5. illustrates the case of a mobile IP-subnet that attaches to a
	MONET.
	2.2. Other Terminology		As for an instance of nested mobility, when a passenger carrying a
			mobile phone (VMN) or a PAN (sub-MONET) gets Internet access from
			the public access network deployed in the bus (parent-MONET).
			Fig.4 and 5. illustrate nested mobility. In fig.4, a single VMN
			gets attached to the mobile network. In fig 5, a VMR carrying an
			entire network, thus a sub-MONET.
	Nested mobility
	We speak about nested mobility when a MONET comprises mobile nodes
	(LMNs or VMNs) and even MONETs. In the bus instance, the bus is a
	MONET whereas a passenger is either a VMN in a MONET if it carries
	a mobile phone or a MONET in the MONET if it carries a PAN.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	skipping to change at page 9, line 35 ¶		skipping to change at page 10, line 32 ¶
	| _____ |__| MR | Mobile Router (TLMR)		| _____ |__| MR | Mobile Router (TLMR)
	|_| |__| |____|		|_| |__| |____|
	| | VMR | | __|_____________ internal		| | VMR | | __|_____________ internal
	| |_____| | __|__ __|__ link 1		| |_____| | __|__ __|__ link 1
	_____ | | | | | |		_____ | | | | | |
	| | | | | LFN | | LMN |		| | | | | LFN | | LMN |
	| LFN |__| | |_____| |_____|		| LFN |__| | |_____| |_____|
	|_____| | |		|_____| | |
	| | internal		| | internal
	link 2		link 2
			<------------------> <--------------------------->
			sub-MONET parent-MONET
			Figure 5: Nested Mobility: sub-MONET that attaches to a larger
			mobile network
	Figure 5: Nested Mobility: mobile IP-subnet in a MONET		2.3. Miscellaneous Terms
	Multi-Homing		NEMO-enabled node
	A MONET is multi-homed when it has two or more active egress		a node that has been extended with NEtwork MObility support
	interfaces connected to distinct parts of the Internet. This could		capabilities and may take special actions based on that. (Details
	either be a single MR with two egress interfaces simultaneously		of the capabilities are not known yet, but it will be based on
	connected to the Internet, or the MONET may be connected to the		enhancements to Mobile IPv6 [MIPv6] and may be implementing some
	Internet via two or more MRs. In the first case, we could think of		sort of Route Optimization).
	a unique router used to connect a car both to the cellular phone
	network and to a satellite. In the second case, we may think of a		MIPv6-enabled node
	PAN where a phone is used to connect the PAN to the cellular phone
	network whereas a Bluetooth PDA is used to collect bus timetables		A mobile node that implements the "MN Operation" of Mobile IPv6
	from the city bus network. In this situation both the phone and
	the PDA are MRs.		[MIPv6]. I.e. A node that only implements the "CN Operation" of
			Mobile IPv6 is NOT considered MIPv6-enabled.
			Multihoming
			Multihoming, as currently defined by the IETF, covers site-
			multihoming [MULTI6] and host multihoming. Within host-
			multihoming, a host may be either:
			- multi-addressed: multiple source addresses to choose between
			on a given interface; all IPv6 nodes are multi-addressed due to
			the presence of link-local addresses on all interfaces.
			- multi-interfaced: multiple interfaces according to [RFC2460]
			definition.
			- multi-linked: just like multi-interfaced but all interfaces
			are NOT connected to the same link.
			- multi-sited: when using IPv6 site-local address and attached
			to different sites
			What is meant by a multihomed-MONET is not clear and is left for
			open discussion. It depends on the possible configurations covered
			by the revised problem scope. Future discussion will assess if a
			MR may fall in all the above described cases and if multiple MRs
			may be used to connect the mobile network to the Internet.
	Local-Area Mobility		Local-Area Mobility
	Mobility within a single administrative domain, i.e. between		Mobility within a single administrative domain, i.e. between
	subnetworks topologically close in the IP hierarchy. In the		subnetworks topologically close in the IP hierarchy. In the
	literature, and depending on the definition of ``closeness'', this		literature, and depending on the definition of ``closeness'', this
	is also termed intra-site mobility, intra-domain mobility, local		is also termed intra-site mobility, intra-domain mobility, local
	mobility or micro-mobility. As an instance of Local-Area Mobility,		mobility or micro-mobility. As an instance of Local-Area Mobility,
	the displacement of a node within a limited vicinity of adjacent		the displacement of a node within a limited vicinity of adjacent
	subnetworks, like in a campus, that belong to the same		subnetworks, like in a campus, that belong to the same
	skipping to change at page 10, line 32 ¶		skipping to change at page 12, line 11 ¶
	macro-mobility. As an instance of Wide-Area Mobility, displacement		macro-mobility. As an instance of Wide-Area Mobility, displacement
	of a node between distinct ISPs or organizations, or between		of a node between distinct ISPs or organizations, or between
	widely separated sites of a single organization.		widely separated sites of a single organization.
	Idle MNN		Idle MNN
	A MNN that does not engage in any communication.		A MNN that does not engage in any communication.
	Idle Mobile Network		Idle Mobile Network
	A MONET that does not engage in any communication outside the		A mobile network that does not engage in any communication outside
	network may be considered as idle from the point of view of the		the network may be considered as idle from the point of view of
	Internet. This doesn't preclude that MNNs are themselves idle.		the Internet. This doesn't preclude that MNNs are themselves idle.
	Internal traffic between any two MNNs located in the same MONET is		Internal traffic between any two MNNs located in the same mobile
	not concerned by this statement.		network is not concerned by this statement.
	3. Observations		3. Observations
	Structure of the mobile network		Structure of the mobile network
	A MR changing its point of attachment does not cause the MNNs		A MR changing its point of attachment does not cause the MNNs
	behind the MR to change their own physical point of attachment.		behind the MR to change their own physical point of attachment.
	Thus, the internal structure of a MONET is not modified as a		Thus, the internal structure of a mobile network is not modified
	result of the MONET changing its point of attachment and a MNN may		as a result of the mobile network changing its point of
	not notice such a displacement. However, MNNs MAY appear to move		attachment. MNNs may or may not notice such a displacement, but
	from the point of view of an other node in the Internet.		they must not be required to be NEMO-enabled. However, MNNs MAY
			appear to move from the point of view of an observer in the
			Internet. In addition, the internal structure of the mobile
			network is assumed to be relatively stable (no dynamic change of
			the topology).
	Mobile Router is a transit point		Mobile Router is a transit point
	All packets sent from a CN to a MNN necessarily transit through a		All packets sent from a CN to a MNN necessarily transit through a
	MR.		MR.
	Size of the MONET		Size of the mobile network
	A MONET may comprise one or more subnets. Its size could scale		A mobile network may comprise one or more subnets. Its size could
	from a sole subnet with a few IP devices, such as in the case of a		scale from a sole subnet with a few IP devices, such as in the
	PAN, to a collection of subnets with hundreds of IP devices, such		case of a PAN, to a collection of subnets with hundreds of IP
	as in a train.		devices, such as in a train.
	Large number of CNs		Large number of CNs
	A MONET may have a very large number of CNs. For instance, each		A mobile network may have a very large number of CNs. For
	passenger in a train may be considered a MNN. Each of them may be		instance, each passenger in a train may be considered a MNN. Each
	communicating with a few CNs. As a result, the total number of CNs		of them may be communicating with a few CNs. As a result, the
	could be several times as large as the number of MNNs and scale up		total number of CNs could be several times as large as the number
	to a few thousands.		of MNNs and scale up to a few thousands.
	Sparseness of the CNs		Sparseness of the CNs
	CNs are typically sparsely distributed in the Internet and belong		CNs are typically sparsely distributed in the Internet and belong
	to distinct administrative domains.		to distinct administrative domains.
	Handoff frequency		Handoff frequency
	MONETs may not move with the same speed and frequency. For		Mobile networks may not move with the same speed and frequency.
	instance, a PAN connected to the Internet via a 802.11b WLAN (e.g.		For instance, a PAN connected to the Internet via a 802.11b WLAN
	user in a shopping mall) is likely to change its point of		(e.g. user in a shopping mall) is likely to change its point of
	attachment very frequently, while an aircraft or a boat may be		attachment very frequently, while an aircraft or a boat may be
	connected to the Internet via the same satellite link for a couple		connected to the Internet via the same satellite link for a couple
	of hours. Obviously, MONETs may not move at all for a large amount		of hours. Obviously, mobile networks may not move at all for a
	of time.		large amount of time.
			Dog-leg Routing
			As a result of mobility, routing between a CN in the global
			Internet and a mobile node may not be optimal. Packets usually
			transit via the home link of the mobile node if no routing
			optimization is explicitly performed. In network mobility,
			multiple dog-leg routing may be introduced by nested mobility. In
			this case, packets intended to a VMN may first transit by the
			VMN's home link, then being rerouted to the MR's home link.
	Ad-Hoc Network		Ad-Hoc Network
	An Ad-hoc network as defined in the IETF MANET Working Group is		An Ad-hoc network as defined in the IETF MANET Working Group is
	not to be confused with a MONET. An ad-hoc network is an		not to be confused with a mobile network. An ad-hoc network is an
	autonomous system of mobile nodes (i.e. routers) connected by		autonomous system made of mobile nodes (i.e. routers) connected by
	wireless links. The routers are free to move randomly and to		wireless links. The routers are free to move randomly and to
	organize themselves arbitrary. In a mobile network, some routers		organize themselves arbitrary. Topologies are highly dynamic. In a
	may effectively move arbitrary, but this not a common case.		mobile network, some routers may effectively move arbitrary, but
	However, an Ad-hoc network connected to the Internet and that		this not a common case. However, an Ad-hoc network connected to
	changes its point of attachment may be considered as a special		the Internet and that changes its point of attachment may be
	instance of a MONET.		considered as a special instance of a mobile network.
			Network mobility support (NEMO) and Mobile Ad-hoc Networking
			(MANET) have not the same objectives. Network mobility support
			aims at providing Internet reachability to nodes in the mobile
			network and at maintaining session continuity after the mobile
			network has changed its point of attachment in the topology. On
			the other hand, MANET aims at maintaining routes between highly
			dynamic nodes.
	Routers in the Mobile Network		Routers in the Mobile Network
	All routers in the Internet are considered to run a number of		All routers in the Internet are considered to run a number of
	protocols such as a routing protocol, Neighbor Discovery, ICMP,		protocols such as a routing protocol, Neighbor Discovery, ICMP,
	and others. This also applies to routers in the MONET, including		and others. This also applies to routers in the mobile network,
	the MR.		including the MR.
			4. Changes from previous draft
			- updated definition of LFN, LMN, VMN, mobile network, mobile network
			prefix, CN
			- added terms NEMO-enabled and MIPv6-enabled.
			- added a section (2.2) for terminology specific to nested mobility:
			root-MONET, parent-MONET, sub-MONET, upstream, downstream.
			- added a paragraph about multihoming
			- removed mobile IP-subnet.
			- added comments about Ad-Hoc network in section 3
			- added comments about multiple dog-leg routing in section 3
	Acknowledgments		Acknowledgments
	The first author would like to thank both Motorola Labs Paris and		The first author would like to thank both Motorola Labs Paris and
	INRIA Rhône-Alpes, for the opportunity to bring this topic to the		INRIA Rhône-Alpes, for the opportunity to bring this topic to the
	IETF, and particularly Claude Castelluccia (INRIA) for its advices,		IETF, and particularly Claude Castelluccia (INRIA) for its advices,
	suggestions, and direction. We also acknowledge Alexandru Petrescu		suggestions, and direction. We also acknowledge Alexandru Petrescu
	(Motorola), Christophe Janneteau (Motorola), Hesham Soliman		(Motorola), Christophe Janneteau (Motorola), Hesham Soliman
	(Ericsson) and Mattias Petterson (Ericsson) for their comments on		(Ericsson) and Mattias Petterson (Ericsson) for their comments on
	this draft.		this draft. We also thank people on the MONET mailing list for their
			discussion which helped to improve this draft.
	References		References
	[Ernst01] Thierry Ernst "Network Mobility Support in IPv6", PhD		[Ernst01] Thierry Ernst
	Thesis, University Joseph Fourier Grenoble, France. October 2001.		"Network Mobility Support in IPv6", PhD Thesis,
			University Joseph Fourier Grenoble, France. October
			2001.
	[MIPv6] David B. Johnson and C. Perkins. "Mobility Support in IPv6".		[MIPv6] David B. Johnson and C. Perkins.
	Internet Draft draft-ietf-mobileip-ipv6-14.txt, Internet Engineering		"Mobility Support in IPv6".
	Task Force (IETF), July 2001. Work in progress.		Internet Draft draft-ietf-mobileip-ipv6-14.txt, July
			2001.
			Work in progress.
	[OLD-draft] Thierry Ernst, Hong-Yon Lach, Claude Castelluccia		[MULTI6] B. Black, V. Gill and J. Abley
	"Network Mobility Support in IPv6: Problem Statement and		"Requirements for IPv6 Site-Multihoming
	Requirements", IETF Internet-Draft draft-ernst-mobileip-		Architectures"
	monetv6-00.txt, July 2001. Expiration pending.		draft-ietf-multi6-multihoming-requirements-03
			May 2002. Work in progress
	[Perkins98] C. E. Perkins. Mobile IP, Design Principles and		[OLD-draft] Thierry Ernst, Hong-Yon Lach, Claude Castelluccia
	Practices. Wireless Communications Series. Addison-Wesley, 1998. ISBN		"Network Mobility Support in IPv6: Problem Statement
	0-201-63469-4.		and
			Requirements",
			Internet-Draft draft-ernst-mobileip-monetv6-00.txt,
			July 2001.
			Expired.
	[Quinot98] Thomas Quinot. An IPv6 architecture for Aeronautical		[Perkins98] C. E. Perkins.
	Telecommunication Network. Master's thesis, Ecole Nationale		"Mobile IP, Design Principles and Practices."
	Superieure des Telecommunications Paris, EUROCONTROL - European		Wireless Communications Series. Addison-Wesley,
	Organization for the Safety of Air Navigation - ISA project (IPv6,		1998.
	Satellite communication and ATMode for ATN), 1998.		ISBN 0-201-63469-4.
	http://www.eurocontrol.fr/.
	[RFC1726] C. Partridge "Technical Criteria for Choosing IP the Next		[Quinot98] Thomas Quinot.
	Generation (IPng)", IETF RFC 1726 section 5.15, December 1994.		"An IPv6 architecture for Aeronautical
			Telecommunication Network"
			Master's thesis,
			Ecole Nationale Superieure des Telecommunications
			Paris,
			EUROCONTROL - European Organization for the Safety
			of Air Navigation
			ISA project (IPv6, Satellite communication and
			ATMode for ATN),
			1998. http://www.eurocontrol.fr/.
	[RFC2460] S. Deering and R. Hinden. "Internet Protocol Version 6		[RFC1726] C. Partridge
	(IPv6) Specification". IETF RFC 2460, Internet Engineering Task		"Technical Criteria for Choosing IP the Next
	Force (IETF), December 1998.		Generation (IPng)",
			IETF RFC 1726 section 5.15, December 1994.
	[RFC2002] C. Perkins (Editor). IP Mobility Support. IETF RFC 2002,		[RFC2460] S. Deering and R. Hinden.
	October 1996.		"Internet Protocol Version 6 (IPv6) Specification".
			IETF RFC 2460, December 1998.
	[REQUIREMENTS] Thierry Ernst "Requirements for Network Mobility		[RFC2002] C. Perkins (Editor).
	Support", IETF Internet-Draft draft-ernst-monet-requirements-00.txt,		"IP Mobility Support".
	February 2001. Work in progress.		IETF RFC 2002,October 1996.
	[REQUIREMENTS-MOTOROLA] Hong-Yon Lach "Mobile Network Scenarios,		[REQUIREMENTS-1] Thierry Ernst, Hong Yon Lach
	Scope and Requirements", IETF Internet-Draft draft-lach-monet-		"Requirements for Network Mobility Support",
	requirements-00.txt, February 2002. Work in progress.		Internet-Draft draft-ernst-monet-
			requirements-00.txt,
			February 2001. Work in progress.
	[REQUIREMENTS-NOKIA] draft-kniveton-monet-requirements.txt, February		[REQUIREMENTS-2] Hong-Yon Lach, Christophe Janneteau, Alexandru
	2002. Work in progress.		Petrescu
			"Mobile Network Scenarios, Scope and Requirements",
			Internet-Draft draft-lach-monet-requirements-00.txt,
			February 2002. Work in progress.
	[SCOPE] Hesham Soliman "Problem Scope", IETF Internet-Draft draft-		[REQUIREMENTS-3] T.J. Kniveton
	soliman-monet-scope-00.txt, February 2002. Work in progress.		draft-kniveton-monet-requirements.txt, February
			2002.
			Work in progress.
	[Solomon98] J. D. Solomon. Mobile IP, The Internet Unplugged.		[SCOPE] Hesham Soliman
	Prentice Hall Series in Computer Networking and Distributed Systems.		"Problem Scope",
	Prentice Hall PTR, 1998. ISBN 0-13-856246-6.		Internet-Draft draft-soliman-monet-scope-00.txt,
			February 2002. Work in progress.
	[Tanenbaum96] Andrew Tanenbaum "Computer Networks", Prentice-Hall,		[Solomon98] J. D. Solomon.
	Third Edition. 1996		"Mobile IP, The Internet Unplugged".
			Prentice Hall Series in Computer Networking and
			Distributed Systems.
			Prentice Hall PTR, 1998. ISBN 0-13-856246-6.
	[WEB-MONET] MONET web page http://www.nal.motlabs.com/monet		[Tanenbaum96] Andrew Tanenbaum
			"Computer Networks",
			Prentice-Hall, Third Edition. 1996
			[WEB-MONET] NEMO web page
			http://www.nal.motlabs.com/monet
	Author's Addresses		Author's Addresses
	Questions about this document can be directed to the authors:		Questions about this document can be directed to the authors:
	Thierry Ernst,		Thierry Ernst,
	WIDE Project		French National Institute for Research in Computer Science and Control
			Visiting Researcher at WIDE Project
	Jun Murai lab. Faculty of Environmental Information,		Jun Murai lab. Faculty of Environmental Information,
	Keio University.		Keio University.
	5322 Endo, Fujisawa-shi, Kanagawa 252-8520, Japan.		5322 Endo, Fujisawa-shi, Kanagawa 252-8520, Japan.
	Phone : +81-466-49-1100		Phone : +81-466-49-1100
	Fax : +81-466-49-1395		Fax : +81-466-49-1395
	E-mail: ernst@sfc.wide.ad.jp		E-mail: ernst@sfc.wide.ad.jp
	Web: http://www.sfc.wide.ad.jp/~ernst/		Web: http://www.sfc.wide.ad.jp/~ernst/
	Hong-Yon Lach		Hong-Yon Lach
	Motorola Labs Paris, Lab Manager,		Motorola Labs Paris, Lab Manager,
End of changes. 67 change blocks.
	214 lines changed or deleted		354 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/