< draft-ietf-nemo-terminology-05.txt		draft-ietf-nemo-terminology-06.txt >
	NEMO Working Group T. Ernst		NEMO Working Group T. Ernst
	Internet-Draft Keio University / WIDE		Internet-Draft INRIA
	Expires: September 7, 2006 H-Y. Lach		Intended status: Informational H-Y. Lach
	Motorola Labs		Expires: May 13, 2007 Motorola Labs
	March 6, 2006		November 9, 2006
	Network Mobility Support Terminology		Network Mobility Support Terminology
	draft-ietf-nemo-terminology-05		draft-ietf-nemo-terminology-06
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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://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.
	This Internet-Draft will expire on September 7, 2006.		This Internet-Draft will expire on May 13, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document defines a terminology for discussing network mobility		This document defines a terminology for discussing network mobility
	issues and solution requirements.		(NEMO) issues and solution requirements.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Architectural Components . . . . . . . . . . . . . . . . . . . 5		2. Architectural Components . . . . . . . . . . . . . . . . . . . 5
	2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 6		2.1. Mobile Network (NEMO) . . . . . . . . . . . . . . . . . . 7
	2.2. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . 7		2.2. Mobile Subnet . . . . . . . . . . . . . . . . . . . . . . 7
	2.3. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 7		2.3. Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . 7
	2.4. Egress Interface . . . . . . . . . . . . . . . . . . . . . 7		2.4. Egress Interface . . . . . . . . . . . . . . . . . . . . . 7
	2.5. Ingress Interface . . . . . . . . . . . . . . . . . . . . 7		2.5. Ingress Interface . . . . . . . . . . . . . . . . . . . . 8
	2.6. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 8		2.6. Mobile Network Prefix (MNP) . . . . . . . . . . . . . . . 8
	2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 8		2.7. Mobile Network Node (MNN) . . . . . . . . . . . . . . . . 8
	2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 8		2.8. Correspondent Node (CN) . . . . . . . . . . . . . . . . . 8
	2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 8		2.9. Correspondent Router (CR) . . . . . . . . . . . . . . . . 8
	2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 8		2.10. Correspondent Entity (CE) . . . . . . . . . . . . . . . . 8
	3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 9		3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . . 9
	3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 10		3.1. Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . 10
	3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 10		3.2. Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . 10
	3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 10		3.3. Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . 10
	skipping to change at page 2, line 43 ¶		skipping to change at page 2, line 48 ¶
	4.5. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 11		4.5. Root-MR . . . . . . . . . . . . . . . . . . . . . . . . . 11
	4.6. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 12		4.6. Parent-MR . . . . . . . . . . . . . . . . . . . . . . . . 12
	4.7. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12		4.7. Sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	4.8. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . 12		4.8. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . 12
	5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 13		5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . . 13
	5.1. Multihomed host or MNN . . . . . . . . . . . . . . . . . . 13		5.1. Multihomed host or MNN . . . . . . . . . . . . . . . . . . 13
	5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 13		5.2. Multihomed Mobile Router . . . . . . . . . . . . . . . . . 13
	5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 14		5.3. Multihomed Mobile Network (multihomed-NEMO) . . . . . . . 14
	5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 14		5.4. Nested Multihomed Mobile Network . . . . . . . . . . . . . 14
	5.5. Split NEMO . . . . . . . . . . . . . . . . . . . . . . . . 14		5.5. Split-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 14
	5.6. Illustration . . . . . . . . . . . . . . . . . . . . . . . 14		5.6. Illustration . . . . . . . . . . . . . . . . . . . . . . . 14
	6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 17		6. Home Network Model Terms . . . . . . . . . . . . . . . . . . . 17
	6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 17		6.1. Home Link . . . . . . . . . . . . . . . . . . . . . . . . 17
	6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 17		6.2. Home Network . . . . . . . . . . . . . . . . . . . . . . . 17
	6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 17		6.3. Home Address . . . . . . . . . . . . . . . . . . . . . . . 17
	6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 17		6.4. Mobile Home Network . . . . . . . . . . . . . . . . . . . 17
	6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 17		6.5. Distributed Home Network . . . . . . . . . . . . . . . . . 17
	6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 17		6.6. Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . 18
	6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 17		6.7. Aggregated Home Network . . . . . . . . . . . . . . . . . 18
	6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 18		6.8. Extended Home Network . . . . . . . . . . . . . . . . . . 18
	6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 18		6.9. Virtual Home Network . . . . . . . . . . . . . . . . . . . 18
	7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 19		7. Mobility Support Terms . . . . . . . . . . . . . . . . . . . . 19
	7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 19		7.1. Host Mobility Support . . . . . . . . . . . . . . . . . . 19
	7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 19		7.2. Network Mobility Support (NEMO Support) . . . . . . . . . 19
	7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 19		7.3. NEMO Basic Support . . . . . . . . . . . . . . . . . . . . 19
	7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 19		7.4. NEMO Extended Support . . . . . . . . . . . . . . . . . . 19
	7.5. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . 19		7.5. NEMO Routing Optimization (NEMO RO) . . . . . . . . . . . 19
	7.6. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 19		7.6. MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . 19
	7.7. Pinball Route . . . . . . . . . . . . . . . . . . . . . . 19		7.7. Pinball Route . . . . . . . . . . . . . . . . . . . . . . 20
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 21		8. Security Considerations . . . . . . . . . . . . . . . . . . . 21
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
	10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24		11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
	11.1. Normative References . . . . . . . . . . . . . . . . . . . 24		11.1. Normative References . . . . . . . . . . . . . . . . . . . 24
	11.2. Informative References . . . . . . . . . . . . . . . . . . 24		11.2. Informative References . . . . . . . . . . . . . . . . . . 24
	Appendix A. Change Log From Earlier Versions . . . . . . . . . . 25		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
	A.1. Changes since draft-nemo-terminology-04.txt . . . . . . . 25		Intellectual Property and Copyright Statements . . . . . . . . . . 26
	A.2. Changes since draft-nemo-terminology-03.txt . . . . . . . 26
	A.3. Changes since draft-nemo-terminology-02.txt . . . . . . . 26
	A.4. Changes since draft-nemo-terminology-01.txt . . . . . . . 26
	A.5. Changes since draft-nemo-terminology-00.txt . . . . . . . 27
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
	Intellectual Property and Copyright Statements . . . . . . . . . . 29
	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. This arises when a router connecting a network to		an entire network. This arises when a router connecting a network to
	the Internet dynamically changes its point of attachment to the fixed		the Internet dynamically changes its point of attachment to the fixed
	infrastructure, thereby causing the reachability of the entire		infrastructure, thereby causing the reachability of the entire
	network to be changed in relation to the fixed Internet topology.		network to be changed in relation to the fixed Internet topology.
	Such a network is referred to as a mobile network. Without		Such a network is referred to as a mobile network. Without
	appropriate mechanisms to support network mobility, sessions		appropriate mechanisms to support network mobility, sessions
	skipping to change at page 5, line 39 ¶		skipping to change at page 5, line 39 ¶
	_ | |-| _ | _		_ | |-| _ | _
	|-|_|-|_____| |-|_|-|-|_|<- HA (Home Agent)		|-|_|-|_____| |-|_|-|-|_|<- HA (Home Agent)
	| \ | _		| \ | _
	foreign link ->| ^ |-|_|<- MR (Mobile Router)		foreign link ->| ^ |-|_|<- MR (Mobile Router)
	.. AR (access ___|___		.. AR (access ___|___
	router) _| |_		router) _| |_
	|_| |_|		|_| |_|
	^ ^		^ ^
	MNN1 MNN2		MNN1 MNN2
	Figure 1: Mobile Network on the Home Link		Figure 1: Mobile Network on the Home Link
	Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger		Figure 2 shows a single mobile subnet. Figure 3 illustrates a larger
	mobile network comprising several subnetworks, attached to a foreign		mobile network comprising several subnetworks, attached to a foreign
	link.		link.
	_		_
	CN ->|_|-|		CN ->|_|-|
	| _____		| _____
	_ | |-| | |<- home link		_ | |-| | |<- home link
	|_|-| _ | _ | |-| _ | _		|_|-| _ | _ | |-| _ | _
	2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA		2 MNNs -> _ |-|_|-|-|_|-|_____| |-|_|-|-|_|<- HA
	|_|-| . | \ \ |		|_|-| . | \ \ |
	| . |<- foreign ^AR		| . |<- foreign ^AR
	mobile subnet -> . link		mobile subnet -> . link
	.		.
	^ MR		^ MR
	Figure 2: Single Mobile Subnet on a Foreign Link		Figure 2: Single Mobile Subnet on a Foreign Link
	_		_
	CN->|_|-|		CN->|_|-|
	mobile subnet->| | _____		mobile subnet->| | _____
	_ | |-| | |<- home link		_ | |-| | |<- home link
	MNN1->|_|-|'i'_'e'| _ | |-| _ | _		MNN1->|_|-|'i'_'e'| _ | |-| _ | _
	|--|_|--|-|_|-|_____| |-|_|-|-|_|<- HA		|--|_|--|-|_|-|_____| |-|_|-|-|_|<- HA
	'i'| | \ |		'i'| | \ |
	____|__ |		____|__ |
	mobile subnet-^ _| . |<- foreign		mobile subnet-^ _| . |<- foreign
	|_| . link		|_| . link
	MNN2 -^ .		MNN2 -^ .
	^		^
	MR		MR
	'i': MR's ingress interface		'i': MR's ingress interface
	'e': MR's egress interface		'e': MR's egress interface
	Figure 3: Larger Mobile Network Made of 2 Mobile Subnets		Figure 3: Larger Mobile Network Made of 2 Mobile Subnets
	At the network layer, MRs get access to the global Internet from the		At the network layer, MRs get access to the global Internet from the
	Access Router(s) (AR) on a visited link. An MR maintains the		Access Router(s) (AR) on a visited link. An MR maintains the
	Internet connectivity for the entire mobile network. A given MR has		Internet connectivity for the entire mobile network. A given MR has
	one or more egress interface and one or more ingress interface. When		one or more egress interface and one or more ingress interface. 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.
	skipping to change at page 9, line 38 ¶		skipping to change at page 9, line 38 ¶
	++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_|		++++>|_|-| \ |--|_|--|-|_|-|_____|-|-|_|
	| | ^ | \ | HA_VMN		| | ^ | \ | HA_VMN
	VMN _ | MR |		VMN _ | MR |
	|_|-| |-VMN		|_|-| |-VMN
	^ mobile subnet 2 +		^ mobile subnet 2 +
	+ +		+ +
	++++++++<<<+++++++++++++++++++++++++		++++++++<<<+++++++++++++++++++++++++
	+++>>>+++ = changing point of attachment		+++>>>+++ = changing point of attachment
	Figure 4: LFN vs LMM vs VMN		Figure 4: LFN vs LMM vs VMN
	In a typical use case of NEMO Basic Support [5], only the MR and the		In a typical use case of NEMO Basic Support [5], only the MR and the
	HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-enabled.		HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-enabled.
	On the other hand, a VMN or a LMN acting as a mobile router may be		On the other hand, a VMN or a LMN acting as a mobile router may be
	NEMO-enabled whereas a VMN or a LMN acting as a mobile node may be		NEMO-enabled whereas a VMN or a LMN acting as a mobile node may be
	MIPv6-enabled.		MIPv6-enabled.
	For NEMO Extended Support, details of the capabilities are not known		For NEMO Extended Support, details of the capabilities are not known
	yet at the time of this writing, but NEMO-enabled nodes may be		yet at the time of this writing, but NEMO-enabled nodes may be
	expected to implement some sort of Route Optimization.		expected to implement some sort of Route Optimization.
	skipping to change at page 12, line 18 ¶		skipping to change at page 12, line 18 ¶
	4.7. Sub-MR		4.7. Sub-MR
	The MR(s) of the sub-NEMO which is connected to a parent-NEMO		The MR(s) of the sub-NEMO which is connected to a parent-NEMO
	4.8. Depth		4.8. Depth
	In a nested NEMO indicates the number of sub-MRs a packet has to		In a nested NEMO indicates the number of sub-MRs a packet has to
	cross between a MNN and the root-MR.		cross between a MNN and the root-MR.
	A MNN in the root-NEMO is a depth 1. If there are multiple root-		A MNN in the root-NEMO is at depth 1. If there are multiple root-
	NEMOs, a different depth is computed from each root-MR.		NEMOs, a different depth is computed from each root-MR.
	_____		_____
	_ | _ | |		_ | _ | |
	_ |-|_|-| _ |-|_|-|-| |-| _		_ |-|_|-| _ |-|_|-|-| |-| _
	_ |-|_|-| \ |-|_|-| \ | |_____| | _ |-|_|		_ |-|_|-| \ |-|_|-| \ | |_____| | _ |-|_|
	_ |-|_|-| | | | |-|_|-|		_ |-|_|-| | | | |-|_|-|
	|_|-| \ | \ |		|_|-| \ | \ |
	|		|
	MNN AR sub-MR AR root-MR AR AR HA		MNN AR sub-MR AR root-MR AR AR HA
	<--------------><----------><----><---------><-------->		<--------------><----------><----><---------><-------->
	sub-NEMO root-NEMO fl Internet Home Network		sub-NEMO root-NEMO fl Internet Home Network
	Figure 5: Nested Mobility: a sub-NEMO attached to a larger mobile		Figure 5: Nested Mobility: a sub-NEMO attached to a larger mobile
	network		network
	5. Multihoming Terms		5. Multihoming Terms
	Multihoming, as currently defined by the IETF, covers site-		Multihoming, as currently defined by the IETF, covers site-
	multihoming [10] and host multihoming. We enlarge this terminology		multihoming [10] and host multihoming. We enlarge this terminology
	to include "multihomed mobile router" and "multihomed mobile		to include "multihomed mobile router" and "multihomed mobile
	network". The specific configurations and issues pertaining to		network". The specific configurations and issues pertaining to
	multihomed mobile networks are covered in [6].		multihomed mobile networks are covered in [6].
	5.1. Multihomed host or MNN		5.1. Multihomed host or MNN
	A host (e.g. an MNN) is multihomed when it has several addresses to		A host (e.g. an MNN) is multihomed when it has several addresses to
	choose between, i.e. in the following cases when it is either:		choose between, i.e. in the following cases when it is either:
	Multi-prefixed: multiple prefixes are advertised on the link(s)		o Multi-prefixed: multiple prefixes are advertised on the link(s)
	the host is attached to, or		the host is attached to, or
	Multi-interfaced: the host has multiple interfaces to choose		o Multi-interfaced: the host has multiple interfaces to choose
	between, on the same link or not.		between, on the same link or not.
	5.2. Multihomed Mobile Router		5.2. Multihomed Mobile Router
	From the definition of a multihomed host, it follows that a mobile		From the definition of a multihomed host, it follows that a mobile
	router is multihomed when it has several addresses to choose between,		router is multihomed when it has several addresses to choose between,
	i.e. in the following cases when the MR is either:		i.e. in the following cases when the MR is either:
	Multi-prefixed: multiple prefixes are advertised on the link(s) an		o Multi-prefixed: multiple prefixes are advertised on the link(s) an
	MR's egress interface is attached to, or.		MR's egress interface is attached to, or.
	Multi-interfaced: the MR has multiple egress interfaces to choose		o Multi-interfaced: the MR has multiple egress interfaces to choose
	between, on the same link or not (see Figure 6).		between, on the same link or not (see Figure 6).
	_____		_____
	_ _ | |		_ _ | |
	|_|-| _ |-|_|-| |-| _		|_|-| _ |-|_|-| |-| _
	_ |-|_|=| \ |_____| | _ |-|_|		_ |-|_|=| \ |_____| | _ |-|_|
	|_|-| | |-|_|-|		|_|-| | |-|_|-|
	\ |		\ |
	MNNs MR AR Internet AR HA		MNNs MR AR Internet AR HA
	Figure 6: Multihoming: MR with multiple E-faces		Figure 6: Multihoming: MR with multiple E-faces
	5.3. Multihomed Mobile Network (multihomed-NEMO)		5.3. Multihomed Mobile Network (multihomed-NEMO)
	A mobile network is multihomed when either a MR is multihomed or		A mobile network is multihomed when either a MR is multihomed or
	there are multiple MRs to choose between (see the corresponding		there are multiple MRs to choose between (see the corresponding
	analysis in [6]).		analysis in [6]).
	MR1		MR1
	_ |		_ |
	_ |-|_|-| _____		_ |-|_|-| _____
	|_|-| |-| |		|_|-| |-| |
	MNNs _ | | |-| _		MNNs _ | | |-| _
	|_|-| _ |-|_____| | _ |-|_|		|_|-| _ |-|_____| | _ |-|_|
	|-|_|-| |-|_|-|		|-|_|-| |-|_|-|
	| |		| |
	MR2		MR2
	Figure 7: Multihoming: NEMO with Multiple MRs		Figure 7: Multihoming: NEMO with Multiple MRs
	5.4. Nested Multihomed Mobile Network		5.4. Nested Multihomed Mobile Network
	A nested mobile network is multihomed when either a root-MR is		A nested mobile network is multihomed when either a root-MR is
	multihomed or there are multiple root-MRs to choose between.		multihomed or there are multiple root-MRs to choose between.
	5.5. Split NEMO		5.5. Split-NEMO
	TBD. See the "issue" web page http://www.sfc.wide.ad.jp/~ernst/nemo/		Split-NEMO refers to the case where a mobile network becomes two or
			more independent mobile networks due to the separation of Mobile
			Routers which are handling the same MNP (or MNPs) in the original
			mobile network before the separation.
	5.6. Illustration		5.6. Illustration
	Figure 6 and Figure 7 show two examples of multihomed mobile		Figure 6 and Figure 7 show two examples of multihomed mobile
	networks. Figure 8 shows two independent mobile networks. NEMO-1 is		networks. Figure 8 shows two independent mobile networks. NEMO-1 is
	single-homed to the Internet through MR1. NEMO-2 is multihomed to		single-homed to the Internet through MR1. NEMO-2 is multihomed to
	the Internet through MR2a and MR2b. Both mobile networks offer		the Internet through MR2a and MR2b. Both mobile networks offer
	access to visiting nodes and networks through an AR.		access to visiting nodes and networks through an AR.
	Let's consider the two following nested scenarios in Figure 8:		Let's consider the two following nested scenarios in Figure 8:
	skipping to change at page 16, line 17 ¶		skipping to change at page 16, line 17 ¶
	|_|-| ARx | |-| _		|_|-| ARx | |-| _
	AR1 \ | | _ | | | _ |-|_|		AR1 \ | | _ | | | _ |-|_|
	_ |-|_|-| | |-|_|-|		_ |-|_|-| | |-|_|-|
	_ |-|_|-| ARy | | |		_ |-|_|-| ARy | | |
	|_|-| MR2a _ | |		|_|-| MR2a _ | |
	NEMO-2 MNNs _ | |-|_|-| |		NEMO-2 MNNs _ | |-|_|-| |
	|_|-| _ | ARz |_____|		|_|-| _ | ARz |_____|
	\ |-|_|-|		\ |-|_|-|
	AR2 MR2b		AR2 MR2b
	Figure 8: Nested Multihomed NEMO		Figure 8: Nested Multihomed NEMO
	6. Home Network Model Terms		6. Home Network Model Terms
	The terms in this section are useful to describe the possible		The terms in this section are useful to describe the possible
	configurations of mobile networks at the home. For a better		configurations of mobile networks at the home. For a better
	understanding of the definitions, the reader is recommended to read		understanding of the definitions, the reader is recommended to read
	[7] where such configurations are detailed		[7] where such configurations are detailed
	6.1. Home Link		6.1. Home Link
	skipping to change at page 17, line 33 ¶		skipping to change at page 17, line 33 ¶
	6.3. Home Address		6.3. Home Address
	With Mobile IPv6, a Home Address is derived from the Home Network		With Mobile IPv6, a Home Address is derived from the Home Network
	prefix. This is generalized in NEMO, with some limitations: A Home		prefix. This is generalized in NEMO, with some limitations: A Home
	Address can be derived either from the Home Network or from one of		Address can be derived either from the Home Network or from one of
	the Mobile Router's MNPs.		the Mobile Router's MNPs.
	6.4. Mobile Home Network		6.4. Mobile Home Network
	A Mobile Network that hosts a Home Agent and mobile nodes. The		A Mobile Network (NEMO) that is also a Home Network. The MR or one
	Mobile Network serves as the Home Network for the mobile nodes in the		of the MR(s) that owns the MNP may act as the Home Agent for the
	Mobile Network. The MR that owns the MNP acts as the Home Agent for		mobile nodes in the Mobile Home Network.
	the Mobile Home Network.
	6.5. Distributed Home Network		6.5. Distributed Home Network
	A Distributed Home Network is a collection of geographically		A Distributed Home Network is a Home Network that is distributed
	distributed Home Networks each served by a Home Agent. The same home		geographically between sites. The aggregated Home Prefix is
	prefix is advertised in all the Home Networks. The distributed Home		partitioned between the sites and advertised by all sites.
	Networks maybe connected using a mesh of IPsec protected tunnels.
			This aggregated Home Prefix can be further aggregated within a
			service provider network or between service providers, to form a
			prefix that is announced into the Internet by the service provider(s)
			from multiple points.
			The sites may be connected using a mesh of private links and tunnels.
			A routing protocol is used within and between sites to exchange
			routes to the subnets associated to the sites, and, eventually, to
			Mobile Routers registered off-site.
	6.6. Mobile Aggregated Prefix		6.6. Mobile Aggregated Prefix
	An aggregation of Mobile Network Prefixes that is in turn advertised		An aggregation of Mobile Network Prefixes.
	as the Home Link Prefix.
	6.7. Aggregated Home Network		6.7. Aggregated Home Network
	The Home Network associated with a Mobile Aggregated Prefix. This		The Home Network associated with a Mobile Aggregated Prefix. This
	Aggregation is advertised as a subnet on the Home Link, and thus used		Aggregation is advertised as a subnet on the Home Link, and thus used
	as Home Network for NEMO purposes.		as Home Network for NEMO purposes.
	6.8. Extended Home Network		6.8. Extended Home Network
	The network associated with the aggregation of one or more Home		The network associated with the aggregation of one or more Home
	skipping to change at page 19, line 28 ¶		skipping to change at page 19, line 28 ¶
	a mobile router's change of point of attachment. Solutions for this		a mobile router's change of point of attachment. Solutions for this
	problem are classified into NEMO Basic Support, and NEMO Extended		problem are classified into NEMO Basic Support, and NEMO Extended
	Support.		Support.
	7.3. NEMO Basic Support		7.3. NEMO Basic Support
	NEMO Basic Support is a solution to preserve session continuity by		NEMO Basic Support is a solution to preserve session continuity by
	means of bi-directional tunneling between MRs and their HAs much like		means of bi-directional tunneling between MRs and their HAs much like
	what is done with Mobile IPv6 [4] for mobile nodes when Routing		what is done with Mobile IPv6 [4] for mobile nodes when Routing
	Optimization is not used. Only the HA and the MR are NEMO-enabled.		Optimization is not used. Only the HA and the MR are NEMO-enabled.
	The solution for doing this is solely specified in [5].
			RFC 3963 [5] is the solution specified by the NEMO Working Group for
			NEMO Basic Support.
	7.4. NEMO Extended Support		7.4. NEMO Extended Support
	NEMO Extended support is to provide the necessary optimization,		NEMO Extended support is to provide the necessary optimization,
	including routing optimization between arbitrary MNNs and CNs.		including routing optimization between arbitrary MNNs and CNs.
	7.5. NEMO Routing Optimization (NEMO RO)		7.5. NEMO Routing Optimization (NEMO RO)
	The term "Route Optimization" is accepted in a broader sense than		The term "Route Optimization" is accepted in a broader sense than
	already defined for IPv6 Host Mobility in [4] to loosely refer to any		already defined for IPv6 Host Mobility in [4] to loosely refer to any
	skipping to change at page 20, line 8 ¶		skipping to change at page 20, line 12 ¶
	The bi-directional tunnel between a Mobile Router and its Home Agent.		The bi-directional tunnel between a Mobile Router and its Home Agent.
	7.7. Pinball Route		7.7. Pinball Route
	A pinball route refers to the non-direct path taken by packets, which		A pinball route refers to the non-direct path taken by packets, which
	are routed via one or more Home Agents, as they transit between a		are routed via one or more Home Agents, as they transit between a
	Mobile Network Node and a Correspondent Node.		Mobile Network Node and a Correspondent Node.
	A packet following a pinball route would appear like a ball bouncing		A packet following a pinball route would appear like a ball bouncing
	off one or more home agents before reaching its final destination.		off one or more Home Agents before reaching its final destination.
	8. Security Considerations		8. Security Considerations
	As this document only provides terminology and describes neither a		As this document only provides terminology and describes neither a
	protocol nor an implementation or a procedure, there are no security		protocol nor an implementation or a procedure, there are no security
	considerations associated with it.		considerations associated with it.
	9. IANA Considerations		9. IANA Considerations
	This document requires no IANA actions.		This document requires no IANA actions.
	skipping to change at page 24, line 10 ¶		skipping to change at page 24, line 10 ¶
	Petterson, Marcelo Bagnulo, TJ Kniveton, Masafumi Watari, Chan-Wah		Petterson, Marcelo Bagnulo, TJ Kniveton, Masafumi Watari, Chan-Wah
	Ng, JinHyeock Choi and numerous other people from the NEMO Working		Ng, JinHyeock Choi and numerous other people from the NEMO Working
	Group. The Home Network Model section is contributed by Pascal		Group. The Home Network Model section is contributed by Pascal
	Thubert, Ryuji Wakikawa and Vijay Devaparalli.		Thubert, Ryuji Wakikawa and Vijay Devaparalli.
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[1] Ernst, T., "Network Mobility Support Goals and Requirements",		[1] Ernst, T., "Network Mobility Support Goals and Requirements",
	draft-ietf-nemo-requirements-05 (work in progress),		draft-ietf-nemo-requirements-06 (work in progress),
	October 2005.		November 2006.
	[2] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)",		[2] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)",
	IETF RFC 2460, December 1998.		RFC 2460, December 1998.
	[3] Manner, J. and M. Kojo, "Mobility Related Terminology",		[3] Manner, J. and M. Kojo, "Mobility Related Terminology",
	RFC 3753, June 2004.		RFC 3753, June 2004.
	[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[5] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,		[5] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,
	"Network Mobility (NEMO) Basic Support Protocol", RFC 3963,		"Network Mobility (NEMO) Basic Support Protocol", RFC 3963,
	January 2005.		January 2005.
	[6] Ng, C., "Analysis of Multihoming in Network Mobility Support",		[6] Ng, C., Paik, Ernst, and C. Bagnulo, "Analysis of Multihoming in
	draft-ietf-nemo-multihoming-issues-05 (work in progress),		Network Mobility Support", draft-ietf-nemo-multihoming-issues-06
	February 2006.		(work in progress), June 2006.
	[7] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home		[7] Thubert, P., Wakikawa, R., and V. Devarapalli, "NEMO Home
	Network Models", draft-ietf-nemo-home-network-models-05 (work in		Network Models", draft-ietf-nemo-home-network-models-06 (work in
	progress), June 2005.		progress), February 2006.
	[8] Ng, C., Pascal, P., Masafumi, M., and F. Fan, "Network Mobility		[8] Ng, C., Thubert, P., Watari, M., and F. Zhao, "Network Mobility
	Route Optimization Problem Statement",		Route Optimization Problem Statement",
	draft-ietf-nemo-ro-problem-statement-01 (work in progress),		draft-ietf-nemo-ro-problem-statement-03 (work in progress),
	October 2005.		September 2006.
	[9] Ng, C., Fan, F., Masafumi, M., and P. Pascal, "Network Mobility		[9] Ng, C., Zhao, F., Watari, M., and P. Thubert, "Network Mobility
	Route Optimization Solution Space Analysis",		Route Optimization Solution Space Analysis",
	draft-ietf-nemo-ro-space-analysis-01 (work in progress),		draft-ietf-nemo-ro-space-analysis-03 (work in progress),
	October 2005.		September 2006.
	11.2. Informative References		11.2. Informative References
	[10] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-		[10] Abley, J., Black, B., and V. Gill, "Goals for IPv6 Site-
	Multihoming Architectures", RFC 3582, August 2003.		Multihoming Architectures", RFC 3582, August 2003.
	[11] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis. ,		[11] Ernst, T., "Network Mobility Support in IPv6", PhD's Thesis. ,
	Universite Joseph Fourier, Grenoble, France , October 2001.		Universite Joseph Fourier, Grenoble, France , October 2001.
	Appendix A. Change Log From Earlier Versions
	The discussions behind the changes in the lattest versions of this
	documents are reflected in the "issue" web page:
	http://www.sfc.wide.ad.jp/~ernst/nemo/
	A.1. Changes since draft-nemo-terminology-04.txt
	In Section 3, added in the introduction a note about NEMO-enabled and
	MIP6-enabled (part of this text was in the definition of NEMO-
	enabled):
	Removed Abbreviation "i-face" and "e-face"
	Replaced "HA" with "home link located outside the mobile network" in
	the definition of VMN
	Replaced "address located within a MNP" with "address taken from a
	MNP" [or derived is better ?] in the definitions of LFN and LMN
	Replaced term NEMO-Link with Mobile Subnet
	Figure 4 illustrates a VMN changing its point of attachment from
	its home link located outside the mobile network to within a
	mobile network. The figure also illustrates a LMN changing its
	point of attachment within the mobile network.
	In a typical use case of NEMO Basic Support [5], only the MR and
	the HA are NEMO-enabled. LFNs are not MIPv6-enabled nor NEMO-
	enabled. On the other hand, a VMN or a LMN acting as a mobile
	router may be NEMO-enabled whereas a VMN or a LMN acting as a
	mobile node may be MIPv6-enabled.
	For NEMO Extended Support, details of the capabilities are not
	known yet at the time of this writing, but NEMO-enabled nodes may
	be expected to implement some sort of Route Optimization.
	Removed this note from the definition of "root-MR": "note: this term
	was referred to as Top-Level Mobile Router, or TLMR in short in
	former versions of this document).".
	Added term "Depth"
	Removed "IPv6" in front of "address" in the definition of a
	multihomed host and a multihomed mobile router
	Removed "or multiple prefixes are advertised in the mobile network"
	from the definition of a multihomed NEMO (5.3) and nested multihomed
	NEMO (5.4)
	Added definition for "Routing Optimization" (see Section 7.5).
	Added definition "Pinball Route" following the discussion on the ML
	in Dec.05
	Added reference to [11] in the ACK section
	A.2. Changes since draft-nemo-terminology-03.txt
	Updated the Home Network Model section with new definitions provided
	by Vijay
	Added definitions of CR and CE as suggested by the RO PB Statement
	and Analysis authors [8]
	Completed figure improvement
	A.3. Changes since draft-nemo-terminology-02.txt
	- Issue A18: Redesigned Figure 3
	- Issue A22: The follolwing comment added in the definition of
	"Mobile Network": "Re-arrangement of the mobile network and changing
	the attachment point of the egress interface to the foreign link are
	orthogonal processes and do no affect each other." (as suggested by
	TJ)
	- Issue A23: Clarified in definition of "NEMO-link" that the link may
	comprise the mobile network: "A link (subnet) which comprises, or is
	located within, the mobile network." (as suggested by TJ)
	- Issue A24: Removed definition of CR (as suggested by TJ)
	- Issue A25: Removed the miscellaneous terms "Idle MNN" and "Idle
	mobile network" (as suggested by TJ)
	- Issue A26: English brush up.
	A.4. Changes since draft-nemo-terminology-01.txt
	- Shorten abstract.
	- Reshaped some figures.
	- LFN, VMN, LMN: said that the node is able/unable to move while
	maintaining/not maintaining ongoing sessions. Text already
	appareared in the document, but not in the definition itself.
	- NEMO-enabled: said that MR and HA are the only NEMO-enabled nodes
	in NEMO Basic Support
	- Removed "NEMO-enabled MR" as this definition is self-contained into
	"NEMO-enabled Node"
	- Rephrased the definition of "multihomed host", "multihomed router",
	"multihomed mobile network" and removed the terms multi-addressed and
	multi-sited, multi-rooted-NEMO, etc. Such terms were not so useful,
	and somewhat too long.
	- Added the case "multiple MNPs are advertised" to the definition of
	mobile network
	- Copy-pasted terms defined from RFC 3753 so that the document is
	self-contained
	- Updated References
	- Added new term "Correspondent Router"
	- Permanently removed NEMO-Prefix. Only MNP will be used
	- Added terms "Mobile Home Network" and "Distributed Home Network" in
	the Home Network Model section. These 2 terms were provided by
	Pascal Thubert on July 30th 2004
	A.5. 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"
	- Deprecated TLMR and MONET.
	- Added NEMO-prefix, NEMO-link, NEMO-enabled MR.
	- Precision that IP address of LFN, LMN, or VMN is taken from a MNP
	- 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-thubert-usages (now home
	network model draft-ietf-nemo-home-network-models)
	Authors' Addresses		Authors' Addresses
	Thierry Ernst		Thierry Ernst
	Keio University / WIDE		INRIA
	Jun Murai Lab., Keio University.		INRIA Rocquencourt
	K-square Town Campus, 1488-8 Ogura, Saiwa-Ku		Domaine de Voluceau B.P. 105
	Kawasaki, Kanagawa 212-0054		Le Chesnay, 78153
	Japan		France
	Phone: +81-44-580-1600		Phone: +33 1 39 63 59 30
	Fax: +81-44-580-1437		Fax: +33 1 39 63 54 91
	Email: ernst@sfc.wide.ad.jp		Email: thierry.ernst@inria.fr
	URI: http://www.sfc.wide.ad.jp/~ernst/		URI: http://www-rocq.inria.fr/imara
	Hong-Yon Lach		Hong-Yon Lach
	Motorola Labs Paris		Motorola Labs Paris
	Espace Technologique - Saint Aubin		Espace Technologique - Saint Aubin
	Gif-sur-Yvette Cedex, 91 193		Gif-sur-Yvette Cedex, 91 193
	France		France
	Phone: +33-169-35-25-36		Phone: +33-169-35-25-36
	Fax:		Fax:
	Email: hong-yon.lach@motorola.com		Email: hong-yon.lach@motorola.com
	URI:		URI:
	Intellectual Property Statement		Full Copyright Statement
			Copyright (C) The Internet Society (2006).
			This document is subject to the rights, licenses and restrictions
			contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
			This document and the information contained herein are provided on an
			"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
			OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
			ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
			INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
			INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
			WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 29, line 29 ¶		skipping to change at page 26, line 45 ¶
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement
	Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 44 change blocks.
	234 lines changed or deleted		95 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/