< draft-ietf-nemo-terminology-00.txt		draft-ietf-nemo-terminology-01.txt >
	IETF NEMO Working Group Thierry Ernst, WIDE and INRIA		NEMO Working Group T. Ernst
	Internet-Draft Hong-Yon Lach, Motorola Labs Paris		Internet-Draft WIDE at Keio University
	May 2003		Expires: August 16, 2004 H-Y. Lach
			Motorola Labs
			February 16, 2004
	Network Mobility Support Terminology		Network Mobility Support Terminology
	draft-ietf-nemo-terminology-00.txt		draft-ietf-nemo-terminology-01
	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.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	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://
	http://www.ietf.org/ietf/1id-abstracts.txt		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.
			This Internet-Draft will expire on August 16, 2004.
			Copyright Notice
			Copyright (C) The Internet Society (2004). All Rights Reserved.
	Abstract		Abstract
	This document defines a terminology for discussing network mobility		This document defines a terminology for discussing network mobility
	problems and solution requirements. Network mobility arises when a		problems and solution requirements. Network mobility arises when a
	router connecting an entire network to the Internet dynamically		router connecting an entire network to the Internet dynamically
	changes its point of attachment to the Internet therefrom causing the		changes its point of attachment to the Internet therefrom causing the
	reachability of the entire network to be changed in the topology.		reachability of the entire network to be changed in the topology.
	Such kind of network is referred to as a mobile network. Without		Such kind of network is referred to as a mobile network. Without
	appropriate mechanisms, sessions established between nodes in the		appropriate mechanisms, sessions established between nodes in the
	mobile network and the global Internet cannot be maintained while the		mobile network and the global Internet cannot be maintained while the
	mobile router changes its point of attachment.		mobile router changes its point of attachment.
	Table of Contents		Table of Contents
	Status of This Memo
	Abstract
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 04		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Architecture Components . . . . . . . . . . . . . . . . . . . . 05		2. Architecture Components . . . . . . . . . . . . . . . . . . 4
	3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . . 07		3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . 5
			3.1 Mobile Network . . . . . . . . . . . . . . . . . . . . . . . 6
			3.2 NEMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
			3.3 MONET [DEPRECIATED] . . . . . . . . . . . . . . . . . . . . 6
			3.4 Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . . 7
			3.5 Egress Interface (E-face) . . . . . . . . . . . . . . . . . 7
			3.6 Ingress Interface (I-face) . . . . . . . . . . . . . . . . . 7
			3.7 NEMO-prefix (MNP) . . . . . . . . . . . . . . . . . . . . . 7
			3.8 NEMO-link . . . . . . . . . . . . . . . . . . . . . . . . . 7
			3.9 Mobile Network Node (MNN) . . . . . . . . . . . . . . . . . 7
			3.10 Node behind the MR . . . . . . . . . . . . . . . . . . . . . 7
			3.11 Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . . 7
			3.12 Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . . 7
			3.13 Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . . 7
			3.14 NEMO-enabled (NEMO-node) . . . . . . . . . . . . . . . . . . 8
			3.15 NEMO-enabled MR . . . . . . . . . . . . . . . . . . . . . . 8
			3.16 MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . . 9
			3.17 Correspondent Node (CN) . . . . . . . . . . . . . . . . . . 9
	Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . . . . 07		4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . 9
	Local Mobile Node (LMN). . . . . . . . . . . . . . . . . . . . . 07		4.1 Nested Mobile Network . . . . . . . . . . . . . . . . . . . 9
	Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . . . . 07		4.2 root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 9
	NEMO-enabled (NEMO-node) . . . . . . . . . . . . . . . . . . . . 07		4.3 parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 9
	MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . . . . 07		4.4 sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . . 10
			4.5 root-MR (or TLMR, but depreciated) . . . . . . . . . . . . . 10
			4.6 parent-MR . . . . . . . . . . . . . . . . . . . . . . . . . 10
			4.7 sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
	4. Nested Mobility. . . . . . . . . . . . . . . . . . . . . . . . . 09		5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . 11
			5.1 Multihomed Host . . . . . . . . . . . . . . . . . . . . . . 11
			5.2 Multihomed Mobile Router . . . . . . . . . . . . . . . . . . 12
			5.3 Multihomed Mobile Network . . . . . . . . . . . . . . . . . 13
			5.4 Multihomed and Nested Mobile Network . . . . . . . . . . . . 13
			5.5 Illustration . . . . . . . . . . . . . . . . . . . . . . . . 14
	Nested Mobile Network. . . . . . . . . . . . . . . . . . . . . . 09		6. Mobility Support Terms . . . . . . . . . . . . . . . . . . . 15
	root-NEMO. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10		6.1 Host mobility support . . . . . . . . . . . . . . . . . . . 15
	parent-NEMO. . . . . . . . . . . . . . . . . . . . . . . . . . . 10		6.2 Network Mobility support (NEMO Support) . . . . . . . . . . 15
	sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10		6.3 NEMO Basic Support . . . . . . . . . . . . . . . . . . . . . 16
	root-MR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11		6.4 NEMO Extended Support . . . . . . . . . . . . . . . . . . . 16
	parent-MR. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
	sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
	5. Multihoming . . . . . . . . . . . . . . . . . . . . . . . . . . 12		7. New Text From Usage Draft . . . . . . . . . . . . . . . . . 16
			7.1 Home Link . . . . . . . . . . . . . . . . . . . . . . . . . 16
			7.2 Home Network . . . . . . . . . . . . . . . . . . . . . . . . 16
			7.3 Home Address . . . . . . . . . . . . . . . . . . . . . . . . 16
			7.4 MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . . 16
			7.5 Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . . 16
			7.6 Aggregated Home Network . . . . . . . . . . . . . . . . . . 16
			7.7 Extended Home Network . . . . . . . . . . . . . . . . . . . 17
			7.8 Virtual Home Network . . . . . . . . . . . . . . . . . . . . 17
	Multihomed Host. . . . . . . . . . . . . . . . . . . . . . . . . 12		8. Miscellaneous Terms . . . . . . . . . . . . . . . . . . . . 17
	multi-addressed host . . . . . . . . . . . . . . . . . . . . . . 12		8.1 Idle MNN . . . . . . . . . . . . . . . . . . . . . . . . . . 17
	multi-interfaced host. . . . . . . . . . . . . . . . . . . . . . 12		8.2 Idle Mobile Network . . . . . . . . . . . . . . . . . . . . 17
	mutli-linked host. . . . . . . . . . . . . . . . . . . . . . . . 12
	multi-sited host . . . . . . . . . . . . . . . . . . . . . . . . 12
	Multihomed Mobile Router . . . . . . . . . . . . . . . . . . . . 12
	multi-egress-addressed MR . . . . . . . . . . . . . . . . . . . 12
	multi-egress-interfaced MR . . . . . . . . . . . . . . . . . . . 12
	mutli-egress-linked MR . . . . . . . . . . . . . . . . . . . . . 12
	multi-egress-sited MR . . . . . . . . . . . . . . . . . . . . . 12
	Multihomed Mobile Network . . . . . . . . . . . . . . . . . . . 12
	multi-MR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	Multihomed Nested Mobile Network . . . . . . . . . . . . . . . . 14
	multi-root . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
	Multihoming Illustration . . . . . . . . . . . . . . . . . . . . 14
	6. Miscellaneous Terms . . . . . . . . . . . . . . . . . . . . . . 16		9. Changes since draft-nemo-terminology-00.txt . . . . . . . . 17
	Host Mobility Support . . . . . . . . . . . . . . . . . . . . . 16
	Network Mobility Support (NEMO Support). . . . . . . . . . . . . 16
	NEMO Basic Support . . . . . . . . . . . . . . . . . . . . . . 16
	NEMO Extended Support . . . . . . . . . . . . . . . . . . . . . 16
	Node behind the MR . . . . . . . . . . . . . . . . . . . . . . . 16
	Correspondent Node (CN). . . . . . . . . . . . . . . . . . . . . 16
	MNP . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 16
	Idle MNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
	Idle Mobile Network . . . . . . . . . . . . . . . . . . . . . . 16
	7. Changes Since Previous Draft . . . . . . . . . . . . . . . . . . 17		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 18
	A. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . 17		References . . . . . . . . . . . . . . . . . . . . . . . . . 18
	B. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 17		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19
	C. Contact Address . . . . . . . . . . . . . . . . . . . . . . . . 18		Intellectual Property and Copyright Statements . . . . . . . 20
	D. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 19		1. Introduction
	1. Introduction
	Network mobility support is concerned with managing the mobility of		Network mobility support is concerned with managing the mobility of
	an entire network which changes its point of attachment to the		an entire network which changes its point of attachment to the
	Internet and thus its reachability in the Internet topology. If		Internet and thus its reachability in the Internet topology. If
	network mobility is not explicitly supported by some mechanisms,		network mobility is not explicitly supported by some mechanisms,
	existing sessions break and connectivity to the global Internet is		existing sessions break and connectivity to the global Internet is
	lost.		lost.
	This document defines the specific terminology needed to describe the		This document defines the specific terminology needed to describe the
	problem space we face with network mobility and to edict the		problem space we face with network mobility and to edict the
	solutions and the requirements they must comply with. This		solutions and the requirements they must comply with. This
	terminology complies with the usual IPv6 terminology [RFC2460] and		terminology complies with the usual IPv6 terminology [7] and the
	the generic mobility-related terms already defined in [Mobility] and		generic mobility-related terms already defined in [2] and in the
	in the Mobile IPv6 [MIPv6] specifications. Some terms introduced in		Mobile IPv6 [1] specifications. Some terms introduced in the present
	the present version of the draft may only be useful for the purpose		version of the draft may only be useful for the purpose of defining
	of defining the problem scope and functional requirements of network		the problem scope and functional requirements of network mobility
	mobility support and shall be removed or refined once we agree on the		support and shall be removed or refined once we agree on the
	requirements.		requirements.
	The first section introduces terms to define the architecture		The first section introduces terms to define the architecture
	components; the second introduces terms to discuss the requirements,		components; the second introduces terms to discuss the requirements,
	the third, terms to discuss nested mobility; the forth defines		the third, terms to discuss nested mobility; the forth defines
	multihoming, and the last, miscellaneous terms which do not fit in		multihoming, and the last, miscellaneous terms which do not fit in
	either sections. The overall terminology is summarized in fig.1 to 5.		either sections. The overall terminology is summarized in fig.1 to 5.
	Fig.1 shows a single mobile subnetwork. Fig.2. shows a larger mobile		Fig.1 shows a single mobile subnetwork. Fig.2. shows a larger mobile
	network comprising several subnetworks, attached on a foreign link.		network comprising several subnetworks, attached on a foreign link.
	Fig.3 illustrates a node changing its point of attachment within the		Fig.3 illustrates a node changing its point of attachment within the
	mobile network. Fig.4 and 5 illustrate nested mobility whereas Fig.6		mobile network. Fig.4 and 5 illustrate nested mobility whereas Fig.6
	to Fig.8 illustrate multihoming.		to Fig.8 illustrate multihoming.
	2. Architecture Components		2. Architecture Components
	Fig.1 and 2 illustrate the architecture components involved in		Fig.1 and 2 illustrate the architecture components involved in
	network mobility. The terms "Fixed Node (FN)", "Mobile Node (MN)",		network mobility. The terms "Fixed Node (FN)", "Mobile Node (MN)",
	"Mobile Network", "Mobile Router (MR)", "Mobile Network Node (MNN)",		"Mobile Network", "Mobile Router (MR)", "Mobile Network Node (MNN)",
	"home link", "foreign link", "ingress interface", "egress interface",		"home link", "foreign link", "ingress interface", "egress interface",
	access router (AR), home link, foreign link are defined in		access router (AR), home link, foreign link are defined in [2].
	[Mobility].
	A mobile network is composed by one or more IP-subnet and is viewed		A mobile network is composed by one or more IP-subnet and is viewed
	as a single unit. It is connected to the Internet by means of mobile		as a single unit. It is connected to the Internet by means of mobile
	routers (MRs). Nodes behind the MR primarily comprise fixed nodes		routers (MRs). Nodes behind the MR primarily comprise fixed nodes
	(nodes unable to change their point of attachment while maintaining		(nodes unable to change their point of attachment while maintaining
	ongoing sessions), and additionally mobile nodes (nodes able to		ongoing sessions), and additionally mobile nodes (nodes able to
	change their point of attachment while maintaining ongoing sessions).		change their point of attachment while maintaining ongoing sessions).
	In most cases, the internal structure of the mobile network will in		In most cases, the internal structure of the mobile network will in
	effect be relatively stable (no dynamic change of the topology), but		effect be relatively stable (no dynamic change of the topology), but
	this is not a general assumption.		this is not a general assumption.
	____		____
	| |		| |
	| CN |		| CN |
	|____|		|____|
	___|____________________		___|____________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	__|_ __|_		__|_ __|_
	| | Access | |		| | Access | |
	| AR | Router | AR |		| AR | Router | AR |
	|____| |____|		|____| |____|
	______|__ foreign __|_____________ home		______|__ foreign __|_____________ home
	link __|_ link		link __|_ link
	| |		| |
	| MR | Mobile Router		| MR | Mobile Router
	|____|		|____|
	_________|_______ internal		_________|_______ NEMO-link
	__|__ __|__ link		__|__ __|__
	| | | |		| | | |
	| MNN | | MNN | Mobile Network Nodes		| MNN | | MNN | Mobile Network Nodes
	|_____| |_____|		|_____| |_____|
	Fig.1: Architecture Components		Fig.1: Architecture Components
	At the network layer, MRs get access to the global Internet from		At the network layer, MRs get access to the global Internet from the
	the Access Routers (ARs) on the visited link. The MR maintains the		Access Routers (ARs) on the visited link. The MR maintains the
	Internet connectivity for the entire mobile network. It has one or		Internet connectivity for the entire mobile network. It has one or
	more egress interface(s) and one or more ingress interface(s).		more egress interface(s) and one or more ingress interface(s). When
	When forwarding a packet to the Internet the packet is transmitted		forwarding a packet to the Internet the packet is transmitted
	upstream through one of the MR's egress interfaces to the AR; when		upstream through one of the MR's egress interfaces to the AR; when
	forwarding a packet from the AR down to the mobile network, the		forwarding a packet from the AR down to the mobile network, the
	packet is transmitted downstream through one of the MR's ingress		packet is transmitted downstream through one of the MR's ingress
	interfaces.		interfaces.
	________________________		3. Functional Terms
	| |
	| |
	| Internet |
	| |
	|________________________|
	__|_
	Access | |
	Router | AR |
	|____|
	foreign _____|_____________
	link |
	| 'e'
	__|__
	| 'i'| |
	|____| MR | Mobile Router
	| |_____|
	| |'i'
	| |
	| ____|________________ internal
	| __|__ __|__ link 1
	_____ | | | | |
	| |__| | MNN | | MNN |
	| MNN | | |_____| |_____|
	|_____| |
	| internal 'i': MR ingress interface
	link 2 'e': MR egress interface
	Fig.2: Larger Mobile Network with 2 subnets		________________________
			| |
			| |
			| Internet |
			| |
			|________________________|
			__|_
			Access | |
			Router | AR |
			|____|
			foreign _____|_____________
			link |
			| 'e'
			__|__
			| 'i'| |
			|____| MR | Mobile Router
			| |_____|
			| |'i'
			| |
			| ____|________________ NEMO-link 1
			| __|__ __|__
			_____ | | | | |
			| |__| | MNN | | MNN |
			| MNN | | |_____| |_____|
			|_____| |
			| NEMO-link 2 'i': MR's ingress interface
			'e': MR's egress interface
	3. Functional Terms		Fig.2: Larger Mobile Network with 2 subnets
	Within the term Mobile Network Node (MNN), we can distinguish between		Within the term Mobile Network Node (MNN), we can distinguish between
	LFN, VMN and LMN. The distinction is a property of how different		LFN, VMN and LMN. The distinction is a property of how different
	types of nodes can move in the topology and is necessary to discuss		types of nodes can move in the topology and is necessary to discuss
	issues related to mobility management and access control, but does		issues related to mobility management and access control, but does
	not preclude that mobility should be handled differently. Nodes are		not preclude that mobility should be handled differently. Nodes are
	classified according to their function and capabilities with the		classified according to their function and capabilities with the
	rationale that nodes with different properties (may) have different		rationale that nodes with different properties (may) have different
	requirements.		requirements.
	Local Fixed Node (LFN)		3.1 Mobile Network
	A fixed node (FN), either a host or a router, that belongs to the		As defined in [2])
	mobile network and which doesn't move topologically with respect
	to the MR.
	Local Mobile Node (LMN)		3.2 NEMO
	A mobile node (MN), either a host or a router who can move		An abbreviation either for "NEtwork MObility" or for " a NEtwork that
	topologically with respect to the MR and whose home link belongs		is MObile". It the former, it refers to the concept of "network
	to the mobile network.		mobility" like in "NEMO Basic Support" and is also the working
			group's name. In the latter, it is used as a noun, e.g. "a NEMO"
			meaning "a mobile network".
	Visiting Mobile Node (VMN)		3.3 MONET [DEPRECIATED]
			An abbreviation for MObile NETwork. MONET can be used as a noun, e.g.
			a MONET" meaning "a mobile network". Not to be confused with MANET
			(Mobile Ad-hoc NETwork)
	A mobile node (MN), either a host or a router who can move		3.4 Mobile Router (MR)
	topologically with respect to the MR and whose home link doesn't
	belong to the mobile network. A VMN that gets attached to a
	foreign link within the mobile network obtains an address on that
	link.
	NEMO-enabled (NEMO-node)		As defined in [2])
	A node that has been extended with network mobility support		3.5 Egress Interface (E-face)
	capabilities and that may take special actions based on that
	(details of the capabilities are not known yet, but it may be
	implementing some sort of Route Optimization).
	MIPv6-enabled (MIPv6-node)		As defined in [2])
	A node which has been extended with host mobility support		3.6 Ingress Interface (I-face)
	capabilities as defined in [MIPv6] and that may take special
	actions based on that
	________________________
	| |
	| |
	| Internet |
	| |
	|________________________|
	__|_ __|_
	| | Access | |
	| AR | Router | AR |
	|____| |____|
	__|_ _____|_____________ foreign
	| | _|__ link
	| MN | | | |
	|____| _____ |__| MR | Mobile Router
	| |__| |____|
	|--> | LMN | | __|_____________ internal
	| |_____| | __|__ | link 1
	| _____ | | |
	| | |__| | LFN |
	| | LFN | | |_____| |
	| |_____| | |
	| | internal |
	| link 2 |
	|------------------------------|
	Fig.3: LFN and LMN: LMN changing subnet		As defined in [2])
	4. Nested Mobility		3.7 NEMO-prefix (MNP)
			An acronym for Mobile Network Prefix (as defined in [2])
			3.8 NEMO-link
			A link (subnet) located within the mobile network.
			3.9 Mobile Network Node (MNN)
			As defined in [2]). May be either a LFN, LMN, or a VMN.
			3.10 Node behind the MR
			Any MNN located in a mobile network, beside the MRs connecting the
			mobile network to the Internet.
			3.11 Local Fixed Node (LFN)
			A fixed node (FN), either a host or a router, that belongs to the
			mobile network and which doesn't move topologically with respect to
			the MR. It's address is taken from a NEMO-prefix.
			3.12 Local Mobile Node (LMN)
			A mobile node (MN), either a host or a router which can move
			topologically with respect to the MR and whose home link belongs to
			the mobile network. It's address is taken from a NEMO-prefix.
			3.13 Visiting Mobile Node (VMN)
			A mobile node (MN), either a host or a router which can move
			topologically with respect to the MR and whose home link doesn't
			belong to the mobile network. A VMN that gets temporarily attached to
			a NEMO-link (used as a foreign link) obtains an address on that link
			(i.e. taken from a NEMO-prefix).
			3.14 NEMO-enabled (NEMO-node)
			A node that has been extended with network mobility support
			capabilities and that may take special actions based on that (details
			of the capabilities are not known yet, but it may be implementing
			some sort of Route Optimization).
			________________________
			| |
			| |
			| Internet |
			| |
			|________________________|
			__|_ __|_
			| | Access | |
			| AR | Router | AR |
			|____| |____|
			__|_ _____|_____________ foreign
			| | _|__ link
			| MN | | | |
			|____| _____ |__| MR | Mobile Router
			| |__| |____|
			|--> | LMN | | __|_____________ NEMO-link 1
			| |_____| | __|__ |
			| _____ | | |
			| | |__| | LFN |
			| | LFN | | |_____| |
			| |_____| | |
			| | NEMO-link 2 |
			| |
			|------------------------------|
			Fig.3: LFN and LMN: LMN changing from NEMO-link 1 to NEMO-link 2
			3.15 NEMO-enabled MR
			A mobile router that has been extended with network mobility support
			capabilities and that may take special actions based on that (for
			instance as the ones defined in NEMO Basic Support [3]
			3.16 MIPv6-enabled (MIPv6-node)
			A node which has been extended with host mobility support
			capabilities as defined in [1] and that may take special actions
			based on that
			3.17 Correspondent Node (CN)
			Any node that is communicating with one or more MNNs. A CN could
			either be located in the fixed network or within the mobile network,
			and could be either fixed or mobile.
			4. Nested Mobility Terms
	Nested mobility occurs when there are more than one level of		Nested mobility occurs when there are more than one level of
	mobility. A MNN acts as an Access Router (AR) and allows visiting		mobility. A MNN acts as an Access Router (AR) and allows visiting
	nodes to get attached to it. There are two cases of nested mobility:		nodes to get attached to it. There are two cases of nested mobility:
	- when the attaching node is a single node: VMN (see figure 4).		o when the attaching node is a single node: VMN (see figure 4). For
	For instance, when a passenger carrying a mobile phone gets		instance, when a passenger carrying a mobile phone gets Internet
	Internet access from the public access network deployed into a		access from the public access network deployed into a bus.
	bus.
	- when the attaching node is a router with nodes behind it, i.e. a		o when the attaching node is a router with nodes behind it, i.e. a
	mobile network (see figure 5). For instance, when a passenger		mobile network (see figure 5). For instance, when a passenger
	carrying a PAN gets Internet access from the public access network		carrying a PAN gets Internet access from the public access network
	deployed in the bus.		deployed in the bus.
	For the second case, we introduce the following terms:		For the second case, we introduce the following terms:
	Nested Mobile Network		4.1 Nested Mobile Network
	A mobile network is said to be nested when a mobile network is		A mobile network is said to be nested when a mobile network is
	getting attached to a larger mobile network. The aggregated		getting attached to a larger mobile network. The aggregated hierarchy
	hierarchy of mobile networks becomes a single nested mobile		of mobile networks becomes a single nested mobile network.
	network.
	________________________		4.2 root-NEMO
	| |
	| |
	| Internet |
	| |
	|________________________|
	__|_ __|_
	| | Access | |
	| AR | Router | AR |
	|____| |____|
	_____|_____________ home
	| _|__ link
	| | | |
	| _____ |__| MR | Mobile Router
	| | |__| |____|
	----------> | VMN | | __|_____________ internal
	|_____| | __|__ __|__ link 1
	_____ | | | | |
	| |__| | LFN | | LMN |
	| LFN | | |_____| |_____|
	|_____| |
	| internal link 2
	Fig.4: Nested Mobility: single VMN attached to a mobile network		The mobile network at the top of the hierarchy connecting the
			aggregated nested mobile network to the Internet.
	root-NEMO		4.3 parent-NEMO
	The mobile network at the top of the hierarchy connecting the		The upstream mobile network providing Internet access to a mobile
	aggregated nested mobile network to the Internet.		network down the hierarchy.
	parent-NEMO		4.4 sub-NEMO
	The upstream mobile network providing Internet access to a mobile		The downstream mobile network attached to a mobile network up the
	network down the hierarchy.		hierarchy. It becomes a subservient of the parent-NEMO. The sub-NEMO
			is getting Internet access through the parent-NEMO and does not
			provide Internet access to the parent-NEMO.
	sub-NEMO		4.5 root-MR (or TLMR, but depreciated)
	The downstream mobile network attached to a mobile network up the		The MR(s) of the root-NEMO used to connect the nested mobile network
	hierarchy. It becomes a subservient of the parent-NEMO. The sub-		to the fixed Internet. Was referred to as "TMLR" (Top-Level Mobile
	NEMO is getting Internet access through the parent-NEMO and does		Router) in former versions of this document.
	not provide Internet access to the parent-NEMO.
	________________________		4.6 parent-MR
	| |
	| |
	| Internet |
	| |
	|________________________|
	__|__ __|__
	| | | |
	| AR1 | | AR2 |
	|_____| |_____|
	_____|_____________ foreign
	__|__ link
	| |
	| _____ |__| MR1 | root-MR
	|__| |__| |_____|
	| | MR2 | | __|_____________ internal
	| |_____| | __|__ __|__ link 1
	_____ | | | | | |
	| | | sub-MR | | LFN | | LMN |
	| LFN |__| | |_____| |_____|
	|_____| | |
	| | internal
	link 2
	<-------------------> <--------------------------->
	sub-NEMO root-NEMO
	Fig.5: Nested Mobility: sub-NEMO attached to a larger mobile network		The MR(s) of the parent-NEMO.
	root-MR		4.7 sub-MR
	The MR(s) of the root-NEMO used to connect the nested mobile		The MR(s) of the sub-NEMO connected to a parent-NEMO
	network to the fixed Internet.
	parent-MR		________________________
			| |
			| |
			| Internet |
			| |
			|________________________|
			__|_ __|_
			| | Access | |
			| AR | Router | AR |
			|____| |____|
			_____|_____________ home
			| _|__ link
			| | | |
			| _____ |__| MR | Mobile Router
			| | |__| |____|
			----------> | VMN | | __|_____________ NEMO-link 1
			|_____| | __|__ __|__
			_____ | | | | |
			| |__| | LFN | | LMN |
			| LFN | | |_____| |_____|
			|_____| |
			| NEMO-link 2
	The MR(s) of the parent-NEMO.		Fig.4: Nested Mobility: single VMN attached to a mobile network
			________________________
			| |
			| |
			| Internet |
			| |
			|________________________|
			__|__ __|__
			| | | |
			| AR1 | | AR2 |
			|_____| |_____|
			_____|_____________ foreign
			__|__ link
			| |
			| _____ |__| MR1 | root-MR
			|__| |__| |_____|
			| | MR2 | | __|_____________ NEMO-link 1
			| |_____| | __|__ __|__
			_____ | | | | | |
			| | | sub-MR | | LFN | | LMN |
			| LFN |__| | |_____| |_____|
			|_____| | |
			| | NEMO-link 2
	sub-MR		|-------------------| |---------------------------|
			sub-NEMO root-NEMO
	The MR(s) of the sub-NEMO connected to a parent-NEMO		Fig.5: Nested Mobility: sub-NEMO attached to a larger mobile network
	5. Multihoming		5. Multihoming Terms
	Multihoming, as currently defined by the IETF, covers site-		Multihoming, as currently defined by the IETF, covers
	multihoming [MULTI6] and host multihoming.		site-multihoming [8] and host multihoming.
	Multihomed Host		5.1 Multihomed Host
	Within host-multihoming, a host may either be:		Within host-multihoming, a host may either be:
	- multi-addressed: multiple source addresses to choose between		o multi-addressed: multiple source addresses to choose between on a
	on a given interface; all IPv6 nodes are multi-addressed due to		given interface; all IPv6 nodes are multi-addressed due to the
	the presence of link-local addresses on all interfaces.		presence of link-local addresses on all interfaces.
	- multi-interfaced: multiple interfaces to choose between, on		o multi-interfaced: multiple interfaces to choose between, on the
	the same link or not.		same link or not.
	- multi-linked: multiple links to choose between (just like		o multi-linked: multiple links to choose between (just like
	multi-interfaced but all interfaces are NOT connected to the		multi-interfaced but all interfaces are NOT connected to the same
	same link)		link)
	- multi-sited: when using IPv6 site-local address and attached		o multi-sited: when using IPv6 site-local address and attached to
	to different sites		different sites
	Multihomed Mobile Router		5.2 Multihomed Mobile Router
	A MR is multihomed when it has simultaneously more than one active		A MR is multihomed when it has simultaneously more than one active
	connection to the Internet, that is when it is either:		connection to the Internet, that is when it is either:
	- multi-egress-addressed MR: the MR has simultaneously multiple		o multi-egress-addressed MR: the MR has simultaneously multiple
	active addresses to choose between on a given egress interface		active addresses to choose between on a given egress interface
	- multi-egress-interfaced MR: the MR has simultaneously		o multi-egress-interfaced MR: the MR has simultaneously multiple
	multiple active egress intefaces on the same link or not		active egress interfaces on the same link or not
	- multi-egress-linked MR: the MR has simultaneously multiple		o multi-egress-linked MR: the MR has simultaneously multiple active
	active egress interfaces on distinct links		egress interfaces on distinct links
	- multi-egress-sited MR: the MR is simultaneously attached to		o multi-egress-sited MR: the MR is simultaneously attached to
	different sites (possible distinct ISPs).		different sites (possible distinct ISPs).
	Multihomed Mobile Network		________________________
			| |
			| |
			| Internet |
			| |
			|________________________|
			__|__ __|__
			| | | |
			| AR1 | | AR2 |
			|_____| |_____|
			foreign ______|_____ _____|______ foreign
			link 1 | ____ | link 2
			| | | |
			|___| MR |___|
			|____|
			______|_____ NEMO-link
			__|__
			| |
			| LFN |
			|_____|
	A mobile network is multihomed when there more than one active		Fig.6: Multihomed Mobile Network: MR has multiple egress interfaces
	interface connected to the global Internet, that is when either:
	- a MR is multihomed, or		5.3 Multihomed Mobile Network
	- mutlti-MR: the mobile network has more than one MR to choose		A mobile network is multihomed when there more than one active egress
	between		interface connected to the global Internet, that is when either:
	________________________		o a MR is multihomed, or
	| |
	| |
	| Internet |
	| |
	|________________________|
	__|__ __|__
	| | | |
	| AR1 | | AR2 |
	|_____| |_____|
	foreign ______|_____ _____|______ foreign
	link 1 | ____ | link 2
	| | | |
	|___| MR |___|
	|____|
	______|_____ internal
	__|__ link 1
	| |
	| LFN |
	|_____|
	Fig.6: Multihomed Mobile Network: multi-interfaced MR		o multi-MR-NEMO: the mobile network has more than one MR to choose
			between
	________________________		________________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|________________________|		|________________________|
	__|__ __|__		__|__ __|__
	| | | |		| | | |
	| AR1 | | AR2 |		| AR1 | | AR2 |
	|_____| |_____|		|_____| |_____|
	foreign ______|_____ _____|______ foreign		foreign ______|_____ _____|______ foreign
	link 1 __|__ __|__ link 2		link 1 __|__ __|__ link 2
	| | | |		| | | |
	| MR1 | | MR2 |		| MR1 | | MR2 |
	|_____| |_____|		|_____| |_____|
	_____|__________|_____ internal		_____|__________|_____ NEMO-link
	__|__ link 1		__|__
	| |		| |
	| LFN |		| LFN |
	|_____|		|_____|
	Fig.7: Multihomed Mobile Network: multi-MR		Fig.7: Multihomed Mobile Network: NEMO with multiple MRs
	Multihomed Nested Mobile Network		5.4 Multihomed and Nested Mobile Network
	A nested mobile network is multihomed when there more than one		A nested mobile network is multihomed when there are more than one
	active interface connected to the global Internet, that is when		active interface connected to the global Internet, that is when
	either:		either:
	- a root-MR is multihomed, or		o a root-MR is multihomed, or
	- multi-root: there are more than one root-MR to choose between		o multi-rooted-NEMO: there are more than one root-MR to choose
			between
	Illustration		5.5 Illustration
	Fig.6 and 7 show two examples of multihomed mobile networks.		Fig.6 and 7 show two examples of multihomed mobile networks. Fig.8.
	Fig.8. shows two independent mobile networks. mobile_network_1 is		shows two independent mobile networks. NEMO-1 is single-homed to the
	single-homed to the Internet through MR1. mobile_network_2 is		Internet through MR1. NEMO-2 is multihomed to the Internet through
	multihomed to the Internet through MR2a and MR2b.		MR2a and MR2b. Both mobile networks offer access to visiting nodes
			and networks through an AR.
	Let's consider the two following nested scenarios:		Let's consider the two following nested scenarios in Fig.8:
	Scenario 1: what happens when MR2a attaches to AR1 ?		Scenario 1: what happens when MR2a's egress interfaced is attached to
			AR1 ?
	- mobile_network_2 becomes a subservient of mobile_network_1		* NEMO-2 becomes a subservient of NEMO-11
	- mobile_network_1 is the parent-NEMO (and also the root-		* NEMO-1 becomes the parent-NEMO for NEMO-2 and the root-NEMO for
	NEMO)		the aggregated nested mobile network
	- mobile_network_2 is the sub-NEMO		* NEMO-2 becomes the sub-NEMO
	- MR1 is the root-MR for the aggregated nested mobile		* MR1 is the root-MR for the aggregated nested mobile network
	network
	- MR2a is a sub-MR in the aggregated nested mobile network		* MR2a is a sub-MR in the aggregated nested mobile network
	- mobile_network_2 is still multihomed to the Internet, but		* NEMO-2 is still multihomed to the Internet through AR1 and ARz
	to AR1 and ARz
	- the aggregated nested mobile network is not multihomed		* The aggregated nested mobile network is not multihomed since
			NEMO-2 cannot be used as a transit network for NEMO-1
	Scenario 2: what happens when MR1 attaches to AR2 ?		Scenario 2: what happens when MR1's egress interface is attached to
			AR2 ?
	- mobile_network_1 becomes a subservient of mobile_network_2		* NEMO-1 becomes a subservient of NEMO-2
	- mobile_network_1 is the sub-NEMO		* NEMO-1 becomes the sub-NEMO
	- mobile_network_2 is the parent_NEMO (and also the root-		* NEMO-2 becomes the parent_NEMO for NEMO-1 and also the
	NEMO)		root-NEMO for the aggregated nested mobile network)
	- MR2a and MR2b are both root_MRs for the aggregated nested
	mobile network
	- MR1 is a sub-MR in the aggregated nested mobile network		* MR2a and MR2b are both root-MRs for the aggregated nested
			mobile network
	- mobile_network_1 is not multihomed		* MR1 is a sub-MR in the aggregated nested mobile network
			* NEMO-1 is not multihomed
	- the aggregated nested mobile network is multihomed		* The aggregated nested mobile network is multihomed
	_____________________________		_____________________________
	| |		| |
	| |		| |
	| Internet |		| Internet |
	| |		| |
	|_____________________________|		|_____________________________|
	__|__ __|__ __|__		__|__ __|__ __|__
	| | | | | |		| | | | | |
	| ARx | | ARy | | ARz |		| ARx | | ARy | | ARz |
	|_____| |_____| |_____|		|_____| |_____| |_____|
	______|__ ____|____ ___|____		______|__ ____|____ ___|____
	__|__ __|___ __|___		__|__ __|___ __|___
	| | | | | |		| | | | | |
	| MR1 | | MR2a | | MR2b |		| MR1 | | MR2a | | MR2b |
	|_____| |______| |______|		|_____| |______| |______|
	mobile _____|____ ___|__________|___ mobile		NEMO-1 _____|____ ___|__________|___ NEMO-2
	network1 __|__ __|__ network2		__|__ __|__
	| | | |		| | | |
	| LFN | AR1 | LFN | AR2		| LFN | AR1 | LFN | AR2
	|_____| |_____|		|_____| |_____|
	Fig.8: Multihomed Nested Mobile Network		Fig.8: Multihomed Nested Mobile Network
	6. Miscellaneous Terms		6. Mobility Support Terms
	Host mobility support		6.1 Host mobility support
	Host Mobility Support is a mechanmism which maintains session		Host Mobility Support is a mechanism which maintains session
	continuity between mobile nodes and their correspondents upon the		continuity between mobile nodes and their correspondents upon the
	mobile host's change of point of attachment. It could be achieved		mobile host's change of point of attachment. It could be achieved by
	by Mobile IPv6.		Mobile IPv6.
	Network Mobility support (NEMO Support)		6.2 Network Mobility support (NEMO Support)
	Network Mobility Support is a mechanism which maintains session
	continuity between mobile network nodes and their correspondent
	upon a mobile router's change of point of attachment. Solutions
	for this problem are classified into NEMO Basic Support, and NEMO
	Extended Support.
	NEMO Basic Support		Network Mobility Support is a mechanism which maintains session
	NEMO Basic support is to preserve session continuity by means of		continuity between mobile network nodes and their correspondent upon
	bidirectional tunneling much like what is done using [MIPv6] for		a mobile router's change of point of attachment. Solutions for this
	mobile nodes.		problem are classified into NEMO Basic Support, and NEMO Extended
			Support.
	NEMO Extended Support		6.3 NEMO Basic Support
	NEMO Extended support is to provide the necessary optimization,
	including routing optimization between arbitrary MNNs and CNs.
	Node behind the MR		NEMO Basic Support is a solution to preserve session continuity by
	Any MNN in a mobile network, beside the MRs connecting the mobile		means of bidirectional tunneling much like what is done using [1] for
	network to the Internet.		mobile nodes. The solution for doing this is solely specified in [3].
	Correspondent Node (CN)		6.4 NEMO Extended Support
	Any node that is communicating with one or more MNNs. A CN could
	either be located in the fixed network or within the mobile
	network, and could be either fixed or mobile.
	MNP		NEMO Extended support is to provide the necessary optimization,
	An acronym for Mobile Network Prefix (defined in [Mobility])		including routing optimization between arbitrary MNNs and CNs.
	Idle MNN		7. New Text From Usage Draft
	A MNN that does not engage in any communication.
	Idle Mobile Network		The text in this section is taken from [5] and is subject to
			discussion on the mailing list.
	A mobile network that does not engage in any communication outside		7.1 Home Link
	the network may be considered idle from the global Internet. This
	doesn't preclude that MNNs are themselves idle. Internal traffic
	between any two MNNs located in the same mobile network is not
	concerned by this statement.
	7. Changes since draft-ernst-nemo-terminology-01.txt		The link attached to the interface at the Home Agent on which the
			Home Prefix is configured. The interface can be a virtual interface,
			in which case the Home Link is a virtual Home Link.
	- removed terms "inter-domain mobility" and "intra-domain mobility".		7.2 Home Network
	Those are replaced with terms "Global mobility" and "Local mobility"
	from [Mobility]
	- removed terms "access router", "mobile network prefix", "home		The Network formed by the application of the Home Prefix on the Home
	subnet prefix", "foreign subnet prefix", "fixed node", "mobile node",		Link. With Nemo, the concept of Home Network is extended as explained
	"mobile network", "mobile network node". "ingress interface", "egress		below.
	interface" to avoid redundancy with [Mobility] where those terms are
	defined.
	- MIPv6-enabled not anymore restricted to the MN Operation		7.3 Home Address
	- removed section "applications" to avoid redundancy with		With Mobile IPv6, a Home Address is derived from the Home Network
	[Requirements]		prefix. This is generalized in Nemo, with some limitations: A Home
			Address can be either derived from the Home Network or from one of
			the Mobile Router's Mobile Network prefixes.
	- more text for multi-homing		7.4 MRHA Tunnel
	A. Acknowledgments		The bi-directional tunnel between a Mobile Router and its Home Agent
			7.5 Mobile Aggregated Prefix
			An aggregation of Mobile Network Prefixes.
			7.6 Aggregated Home Network
			The Home Network associated with a Mobile Aggregated Prefix. This
			Aggregation is advertised as a subnet on the Home Link, and thus used
			as Home Network for Nemo purposes.
			7.7 Extended Home Network
			The network associated with the aggregation of one or more Home
			Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home
			Network that is a subnet, the extended Home Network is an aggregation
			and is further subnetted.
			7.8 Virtual Home Network
			The Home Network associated with a Virtual Network. The Extended Home
			Network and the Aggregated Home Network can be configured as Virtual
			Home Network.
			8. Miscellaneous Terms
			8.1 Idle MNN
			A MNN that does not engage in any communication.
			8.2 Idle Mobile Network
			A mobile network that does not engage in any communication outside
			the network may be considered idle from the global Internet. This
			doesn't preclude that MNNs are themselves idle. Internal traffic
			between any two MNNs located in the same mobile network is not
			concerned by this statement.
			9. Changes since draft-nemo-terminology-00.txt
			- NEMO will be used either as the concept for NEtwork MObility and a
			noun meaning "NEtwork that is MObile"
			- Added TMLR as depreciated term (everyone should use root-MR
			instead)
			- Added NEMO-prefix
			- Added NEMO-link
			- Added NEMO-enabled MR
			- Precision that IP address of LFN, LMN, or VMN is taken from a
			NEMO-prefix
			- Added abbreviation E-face (Egress interface) and I-face (Ingress
			interface)
			- Some re-ordering of terms, and a few typos.
			- Added some text from the usage draft [5]
			10. Acknowledgments
	The material presented in this document takes most of the text from		The material presented in this document takes most of the text from
	our former internet-drafts submitted to MobileIP WG and to the former		our former internet-drafts submitted to MobileIP WG and to the former
	MONET BOF. Authors would therefore like to thank both Motorola Labs		MONET BOF. Authors would therefore like to thank both Motorola Labs
	Paris and INRIA (PLANETE team, Grenoble, France), for the opportunity		Paris and INRIA (PLANETE team, Grenoble, France), for the opportunity
	to bring this terminology to the IETF, and particularly Claude		to bring this terminology to the IETF, and particularly Claude
	Castelluccia (INRIA) for his advices, suggestions, and direction,		Castelluccia (INRIA) for his advices, suggestions, and direction,
	Alexandru Petrescu (Motorola) and Christophe Janneteau (Motorola). We		Alexandru Petrescu (Motorola) and Christophe Janneteau (Motorola).
	also acknowledge the input from Hesham Soliman (Ericsson), Mattias
	Petterson (Ericsson), and numerous other people on the NEMO mailing
	list.
	B. References		We also acknowledge the input from Hesham Soliman (Ericsson), Mattias
			Petterson (Ericsson), and numerous other people from the NEMO Working
			Group
	[Requirements] Thierry Ernst		References
	"Network Mobility Support Requirements"
	draft-ietf-nemo-requirements.txt
	Work in progress.
	[MIPv6] David B. Johnson and C. Perkins.		[1] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in
	"Mobility Support in IPv6".		IPv6", draft-ietf-mobileip-ipv6-24 (work in progress), July
	Internet Draft draft-ietf-mobileip-ipv6.txt,		2003.
	Work in progress.
	[Mobility] J. Manner and M. Kojo		[2] Manner, J. and M. Kojo, "Mobility Related Terminology",
	"Mobility Related Terminology		draft-ietf-seamoby-terminology-04 (work in progress), April
	draft-ietf-seamoby-mobility-terminology.txt		2003.
	Work in progress
	[MULTI6] B. Black, V. Gill and J. Abley		[3] Devarapalli, V., "Network Mobility Basic Support Protocol",
	"Requirements for IPv6 Site-Multihoming Architectures"		draft-ietf-nemo-basic-support-02 (work in progress), December
	draft-ietf-multi6-multihoming-requirements.txt		2003.
	Work in progress
	[IPv6-NODE] John Loughney		[4] Ernst, T., "Network Mobility Support Requirements",
	"IPv6 Node Requirements"		draft-ietf-nemo-requirements-02 (work in progress), February
	draft-ietf-ipv6-node-requirements.txt		2004.
	Work in progress.
	[Perkins] C. E. Perkins.		[5] Thubert, P., Wakikawa, R. and V. Devarapalli, "Examples of Basic
	"Mobile IP, Design Principles and Practices."		NEMO Usage", draft-thubert-nemo-basic-usages (work in progress),
	Wireless Communications Series.		February 2004.
	Addison-Wesley, 1998. ISBN 0-201-63469-4.
	[RFC1726] C. Partridge		[6] Perkins, C., "IP Mobility support", IETF RFC 2002, October 1996.
	"Technical Criteria for Choosing IP the Next
	Generation",
	IETF RFC 1726 section 5.15, December 1994.
	[RFC2460] S. Deering and R. Hinden.		[7] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)",
	"Internet Protocol Version 6 (IPv6) Specification".		IETF RFC 2460, December 1998.
	IETF RFC 2460, December 1998.
	[RFC2002] C. Perkins (Editor).		[8] Abley, J., Black, B. and V. Gill, "Goals for IPv6
	"IP Mobility Support".		Site-Multihoming Architectures", IETF RFC 3582, August 2003.
	IETF RFC 2002,October 1996.
	C. Contact Address		Authors' Addresses
	Questions about this document can be directed to the authors:		Ernst Thierry
			WIDE at Keio University
			Jun Murai Lab., Keio University.
			K-square Town Campus, 1488-8 Ogura, Saiwa-Ku
			Kawasaki, Kanagawa 212-0054
			Japan
	Thierry Ernst,		Phone: +81-44-580-1600
	Keio University.		Fax: +81-44-580-1437
	5322 Endo, Fujisawa-shi,		EMail: ernst@sfc.wide.ad.jp
	Kanagawa 252-8520, Japan.		URI: http://www.sfc.wide.ad.jp/~ernst/
	Phone : +81-466-49-1100
	Fax : +81-466-49-1395
	Email : ernst@sfc.wide.ad.jp
	Hong-Yon Lach		Hong-Yon Lach
	Motorola Labs Paris, Lab Manager,		Motorola Labs Paris
	Networking and Applications Lab (NAL)		Espace Technologique - Saint Aubin
	Espace Technologique - Saint Aubin		Gif-sur-Yvette Cedex, 91 193
	91193 Gif-sur-Yvette Cedex, France		France
	Phone: +33-169-35-25-36
	Email: Hong-Yon.Lach@crm.mot.com
	D. Full Copyright Statement		Phone: +33-169-35-25-36
			Fax:
			EMail: hong-yon.lach@motorola.com
			URI:
	Copyright (C) The Internet Society (2002). All Rights Reserved.		Intellectual Property Statement
			The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			pertain to the implementation or use of the technology described in
			this document or the extent to which any license under such rights
			might or might not be available; neither does it represent that it
			has made any effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in BCP-11. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			Full Copyright Statement
			Copyright (C) The Internet Society (2004). All Rights Reserved.
	This document and translations of it may be copied and furnished to		This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it		others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published and		or assist in its implementation may be prepared, copied, published
	distributed, in whole or in part, without restriction of any kind,		and distributed, in whole or in part, without restriction of any
	provided that the above copyright notice and this paragraph are		kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this		included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing		document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other		the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of developing		Internet organizations, except as needed for the purpose of
	Internet standards in which case the procedures for copyrights defined		developing Internet standards in which case the procedures for
	in the Internet Standards process must be followed, or as required to		copyrights defined in the Internet Standards process must be
	translate it into languages other than English.		followed, or as required to translate it into languages other than
			English.
	The limited permissions granted above are perpetual and will not be		The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assigns.		revoked by the Internet Society or its successors or assignees.
	This document and the information contained herein is provided on an		This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING		"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT		TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN		BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF		HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Funding for the RFC editor function is currently provided by the		Acknowledgment
			Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 148 change blocks.
	506 lines changed or deleted		642 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/