< draft-ietf-nemo-home-network-models-05.txt		draft-ietf-nemo-home-network-models-06.txt >
	Network Mobility P. Thubert		Network Mobility P. Thubert
	Internet-Draft Cisco		Internet-Draft Cisco
	Expires: April 13, 2006 R. Wakikawa		Expires: August 21, 2006 R. Wakikawa
	Keio University		Keio University
	V. Devarapalli		V. Devarapalli
	Nokia		Nokia
	October 10, 2005		February 17, 2006
	NEMO Home Network models		NEMO Home Network models
	draft-ietf-nemo-home-network-models-05		draft-ietf-nemo-home-network-models-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 37 ¶		skipping to change at page 1, line 37 ¶
	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 April 13, 2006.		This Internet-Draft will expire on August 21, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This paper documents some usage patterns and the associated issues		This paper documents some usage patterns and the associated issues
	when deploying a Home Network for NEMO-enabled Mobile Routers,		when deploying a Home Network for NEMO-enabled Mobile Routers,
	conforming the NEMO Basic Support draft [8]. The aim here is		conforming the NEMO Basic Support. The aim here is specifically to
	specifically to provide some examples of organization of the Home		provide some examples of organization of the Home Network, as they
	Network, as they were discussed in NEMO related mailing lists.		were discussed in NEMO related mailing lists.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology and concepts . . . . . . . . . . . . . . . . . . . 4		2. Terminology and concepts . . . . . . . . . . . . . . . . . . . 4
	3. General Expectations . . . . . . . . . . . . . . . . . . . . . 5		3. General Expectations . . . . . . . . . . . . . . . . . . . . . 5
	4. MIP Home Network . . . . . . . . . . . . . . . . . . . . . . . 6		4. MIP Home Network . . . . . . . . . . . . . . . . . . . . . . . 6
	5. NEMO Extended Home Network . . . . . . . . . . . . . . . . . . 7		5. NEMO Extended Home Network . . . . . . . . . . . . . . . . . . 7
	5.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 7		5.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 7
	5.2 Returning Home . . . . . . . . . . . . . . . . . . . . . . 8		5.2 Returning Home . . . . . . . . . . . . . . . . . . . . . . 8
	5.3 Home Address from MNP . . . . . . . . . . . . . . . . . . 8		5.3 Home Address from MNP . . . . . . . . . . . . . . . . . . 8
	5.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 9		5.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 9
	5.4.1 Mobile Router side . . . . . . . . . . . . . . . . . . 9		5.4.1 Mobile Router side . . . . . . . . . . . . . . . . . . 9
	5.5 Applicability . . . . . . . . . . . . . . . . . . . . . . 9		5.5 Applicability . . . . . . . . . . . . . . . . . . . . . . 9
	6. NEMO Aggregated Home Network . . . . . . . . . . . . . . . . . 10		6. NEMO Aggregated Home Network . . . . . . . . . . . . . . . . . 10
	6.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 10		6.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 10
	6.2 Returning Home . . . . . . . . . . . . . . . . . . . . . . 10		6.2 Returning Home . . . . . . . . . . . . . . . . . . . . . . 10
	6.2.1 Returning Home with the Egress interface . . . . . . . 11		6.2.1 Returning Home with the Egress interface . . . . . . . 11
	6.2.2 Returning Home with the Ingress interface . . . . . . 12		6.2.2 Returning Home with the Ingress interface . . . . . . 11
	6.3 Applicability . . . . . . . . . . . . . . . . . . . . . . 12		6.3 Applicability . . . . . . . . . . . . . . . . . . . . . . 12
	6.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 12		6.4 Deployment Caveats . . . . . . . . . . . . . . . . . . . . 12
	6.4.1 Home Agent Side . . . . . . . . . . . . . . . . . . . 12		6.4.1 Home Agent Side . . . . . . . . . . . . . . . . . . . 12
	6.4.2 Mobile Router side . . . . . . . . . . . . . . . . . . 13		6.4.2 Mobile Router side . . . . . . . . . . . . . . . . . . 13
	7. Virtual Home Network . . . . . . . . . . . . . . . . . . . . . 14		7. Virtual Home Network . . . . . . . . . . . . . . . . . . . . . 14
	7.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 14		7.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 14
	7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 15		7.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 15
	8. Mobile Home . . . . . . . . . . . . . . . . . . . . . . . . . 16		8. Mobile Home . . . . . . . . . . . . . . . . . . . . . . . . . 16
	8.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 16		8.1 Configuration . . . . . . . . . . . . . . . . . . . . . . 16
	8.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 18		8.2 Applicability . . . . . . . . . . . . . . . . . . . . . . 18
	9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 18		9. IANA considerations . . . . . . . . . . . . . . . . . . . . . 18
	10. Security Considerations . . . . . . . . . . . . . . . . . . 18		10. Security Considerations . . . . . . . . . . . . . . . . . . 18
	11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 19		11. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 19
	11.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 19		11.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 19
	11.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 19		11.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 19
	11.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 19		11.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 19
	11.4 Changes from version 03 to 04 . . . . . . . . . . . . . . 19		11.4 Changes from version 03 to 04 . . . . . . . . . . . . . . 19
	11.5 Changes from version 04 to 05 . . . . . . . . . . . . . . 19		11.5 Changes from version 04 to 05 . . . . . . . . . . . . . . 19
	12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20		11.6 Changes from version 05 to 06 (IESG review) . . . . . . . 19
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 20		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
	13.1 normative reference . . . . . . . . . . . . . . . . . . . 20		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
	13.2 informative reference . . . . . . . . . . . . . . . . . . 21		13.1 normative reference . . . . . . . . . . . . . . . . . . . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 21		13.2 informative reference . . . . . . . . . . . . . . . . . . 22
	Intellectual Property and Copyright Statements . . . . . . . . 22		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
			Intellectual Property and Copyright Statements . . . . . . . . 23
	1. Introduction		1. Introduction
	This document assumes that the reader is familiar with IPv6 Mobility		This document assumes that the reader is familiar with IPv6 Mobility
	as defined in [7], with the NEMO Basic Support [8]. In order to read		as defined by Mobile IPv6 and the NEMO Basic Support. In order to
	this document properly, it is important to realize that in NEMO, the		read this document properly, it is important to realize that in NEMO,
	Home Network can encompass much more than the Home Link, as it spans		the Home Network can encompass much more than the Home Link, as it
	the Home Link and all the Links that the Mobile Routers carry with		spans the Home Link and all the Links that the Mobile Routers (MRs)
	them. Exactly how the two concepts relate in a given deployment		carry with them. Exactly how the two concepts relate in a given
	depend on the organization of the Home Network, as described below.		deployment depend on the organization of the Home Network, as
			described below.
	Five different organizations of the Home Network including a		Five different organizations of the Home Network including a
	hierarchical construction are documented:		hierarchical construction are documented:
	MIPv6 Home Network: A short reminder of what the Home Network is with		MIPv6 Home Network: A short reminder of what the Home Network is with
	Mobile IP, in order to help the reader figure out the evolution		Mobile IP, in order to help the reader figure out the evolution
	towards NEMO.		towards NEMO.
	NEMO Extended Home Network: In this arrangement, the Home Network is		NEMO Extended Home Network: In this arrangement, the Home Network is
	only one subnet of a larger aggregation that encompasses the		only one subnet of a larger aggregation that encompasses the
	skipping to change at page 3, line 39 ¶		skipping to change at page 3, line 40 ¶
	actually overlaps with the Mobile Networks. When at Home, a		actually overlaps with the Mobile Networks. When at Home, a
	Mobile Router acts as a bridge between the Home Link and the		Mobile Router acts as a bridge between the Home Link and the
	Mobile Networks. More in Section 6.		Mobile Networks. More in Section 6.
	Virtual Home Network: In this arrangement, there is no physical Home		Virtual Home Network: In this arrangement, there is no physical Home
	Link at all for the Mobile Routers to come back Home to. More in		Link at all for the Mobile Routers to come back Home to. More in
	Section 7.		Section 7.
	NEMO Mobile Home Network: In this arrangement, there is a bitwise		NEMO Mobile Home Network: In this arrangement, there is a bitwise
	hierarchy of Home Networks. A global Home Network is advertised		hierarchy of Home Networks. A global Home Network is advertised
	to the infrastructure by a head Home Agent and further subnetted		to the infrastructure by a head Home Agent (HA) and further
	into Mobile Networks. Each subnet is owned by a Mobile Router		subnetted into Mobile Networks. Each subnet is owned by a Mobile
	that registers it in a NEMO fashion while acting as a Home Agent		Router that registers it in a NEMO fashion while acting as a Home
	for that network. More in Section 8.		Agent for that network. More in Section 8.
	In all cases, the Home Agents collectively advertise only the		In all cases, the Home Agents collectively advertise only the
	aggregation of the Mobile Networks. The subnetting is kept within		aggregation of the Mobile Networks. The subnetting is kept within
	the Home Agents and the Mobile Routers, as opposed to advertised by		the Home Agents and the Mobile Routers, as opposed to advertised by
	means of routing protocols to other parties.		means of routing protocols to other parties.
	The examples provided here aim at illustrating the NEMO Basic Support		The examples provided here aim at illustrating the NEMO Basic Support
	[8] but do not aim at limiting its scope of application, and		[8] but do not aim at limiting its scope of application, and
	additional cases may be added in the future.		additional cases may be added in the future.
	2. Terminology and concepts		2. Terminology and concepts
	The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,		The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
	SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be		SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be
	interpreted as described in RFC2119 [1].		interpreted as described in RFC2119 [1].
	The following terms used in this document are defined in the IPv6
	Addressing Architecture document [5]:
	link-local unicast address
	link-local scope multicast address
	Most of the mobility related terms used in this document are defined		Most of the mobility related terms used in this document are defined
	in the Mobility Related Terminology document [6] and in the Mobile		in the Mobility Related Terminology document [6] and in the Mobile
	IPv6 (MIP6) specification [7].		IPv6 (MIP6) specification [7].
	Additionally, some terms were created or extended for NEMO. These		Additionally, some terms were created or extended for NEMO. These
	specific terms are defined in the Mobile Network Terminology document		specific terms are defined in the Mobile Network Terminology document
	[9]:		[9]:
	Home Link		Home Link
	skipping to change at page 5, line 16 ¶		skipping to change at page 5, line 16 ¶
	With Mobile IPv6, the Home Network is generally a physical network		With Mobile IPv6, the Home Network is generally a physical network
	interconnecting the Home Agents, and the Mobile Nodes that are at		interconnecting the Home Agents, and the Mobile Nodes that are at
	Home. NEMO extends the concept of Home so that it is not only a flat		Home. NEMO extends the concept of Home so that it is not only a flat
	subnet composed of Home Addresses but an aggregation that is itself		subnet composed of Home Addresses but an aggregation that is itself
	subnetted in mobile and Home Networks. This aggregation is still		subnetted in mobile and Home Networks. This aggregation is still
	referred to as Home.		referred to as Home.
	As an example, considering the case where the aggregation has a		As an example, considering the case where the aggregation has a
	global routing prefix of m = 48 bits (A:B:C::/48), with subnet ID		global routing prefix of m = 48 bits (A:B:C::/48), with subnet ID
	size of n = 16 bits ( n + m = 64).		size of n = 16 bits ( n + m = 64):
	When a Mobile Router, MR1, owns the MNP A:B:C:1::/64 with the NEMO		When a Mobile Router, MR1, uses the Mobile Network Prefix (MNP) A:B:
	Basic Support, MR1 may register using a Home Address from the Home		C:1::/64 with the NEMO Basic Support, MR1 may register using a Home
	network (i.e. A:B:C:0::1) or a Home Address from one of its MNPs		Address from the Home network (i.e. A:B:C:0::1) or a Home Address
	(i.e. A:B:C:1::1) depending on the deployment.		from one of its MNPs (i.e. A:B:C:1::1) depending on the deployment.
	In a given deployment, one subnet may be reserved for the Home Link		In a given deployment, one subnet may be reserved for the Home Link
	(A:B:C:0::/64) while the others are attributed to Mobile Routers as		(A:B:C:0::/64) while the others are attributed to Mobile Routers as
	Mobile Networks (as A:B:C:1::/64 for MR1). Another approach could be		Mobile Networks (as A:B:C:1::/64 for MR1). Another approach could be
	to configure the Aggregation of Mobile Networks as the subnet on the		to configure the Aggregation of Mobile Networks as the subnet on the
	Home Link, and let the Mobile Routers manage the overlapping		Home Link, and let the Mobile Routers manage the overlapping
	networks. Finally, the aggregation could be configured on a virtual		networks. Finally, the aggregation could be configured on a virtual
	network, with no physical Home Link at all, in which case Home means		network, with no physical Home Link at all, in which case Home means
	topologically and administratively close to the Home Agent that owns		topologically and administratively close to the Home Agent that
	the virtual network.		advertises the virtual network.
	The following sections provide additional information on these forms		The following sections provide additional information on these forms
	of Home Network.		of Home Network.
	4. MIP Home Network		4. MIP Home Network
	In the Mobile IPv6 (MIP6) specification [7] Mobile Nodes are at Home		In the Mobile IPv6 (MIP6) specification [7] Mobile Nodes are at Home
	when they are connected to their Home Link, where they recognize		when they are connected to their Home Link, where they recognize
	their Home Prefix in Router Advertisement messages. Also, a binding		their Home Prefix in Router Advertisement messages. Also, a binding
	is checked using Duplicate Address Detection on the Home Link, and		is checked using Duplicate Address Detection on the Home Link, and
	skipping to change at page 9, line 18 ¶		skipping to change at page 9, line 18 ¶
	5.4 Deployment Caveats		5.4 Deployment Caveats
	5.4.1 Mobile Router side		5.4.1 Mobile Router side
	In explicit mode, the routing to the MNP via the Mobile Router must		In explicit mode, the routing to the MNP via the Mobile Router must
	be restored when the Mobile Router is at Home. This is normally		be restored when the Mobile Router is at Home. This is normally
	performed by the Mobile Router by means of the existing IGP. In that		performed by the Mobile Router by means of the existing IGP. In that
	case, a specific support is required on the Mobile Router to control		case, a specific support is required on the Mobile Router to control
	the routing protocol operation, enabling the participation in the IGP		the routing protocol operation, enabling the participation in the IGP
	if and only if the Mobile Router is at home. This support might not		if and only if the Mobile Router is at home.
	be present in all implementations.
			The NEMO Basic Support does not mandate a specific routing protocol
			though the support for some well known routing protocols can be
			expected from many implementations. An implementation might provide
			an automatic toggle to start/stop routing on an egress interface when
			the mobile router comes back/leaves Home. When such a toggle is
			unavailable, then a specific interface should be reserved to attach
			to Home with the appropriate settings for security and routing.
	5.5 Applicability		5.5 Applicability
	The Extended Home Network keeps the MIP6 concept of a Home Network		The Extended Home Network keeps the MIP6 concept of a Home Network
	for both Mobile Nodes and Mobile Routers to take their Home Address		for both Mobile Nodes and Mobile Routers to take their Home Address
	from. Since there is no overlap between the prefixes that are		from. Since there is no overlap between the prefixes that are
	assigned to MNPs and prefix(es) that are dedicated to the Home Link,		assigned to MNPs and prefix(es) that are dedicated to the Home Link,
	it is possible for MNs and Mobile Routers to coexist with that model.		it is possible for MNs and Mobile Routers to coexist with that model.
	Also, when the Home Address is derived from the prefix on the Home		Also, when the Home Address is derived from the prefix on the Home
	skipping to change at page 11, line 9 ¶		skipping to change at page 11, line 9 ¶
	6.2 Returning Home		6.2 Returning Home
	The Aggregated Home Prefix is configured on a physical interface of		The Aggregated Home Prefix is configured on a physical interface of
	the Home Agent, the Home Link. As a consequence, the Home Agent has		the Home Agent, the Home Link. As a consequence, the Home Agent has
	a connected route to the Aggregated Home Network over the Home Link.		a connected route to the Aggregated Home Network over the Home Link.
	A Mobile Router returns Home by connecting directly to the Home Link,		A Mobile Router returns Home by connecting directly to the Home Link,
	and dropping the MRHA tunnel. The Mobile Router recognizes its Home		and dropping the MRHA tunnel. The Mobile Router recognizes its Home
	Link by a prefix match with its Home Agent.		Link by a prefix match with its Home Agent.
	Since the Home Network prefix is an aggregation that encompasses all		When the Mobile Router forms its Home Address out of one of its MNPs,
	the MNPs, the Home Address that an MR forms from one of its Mobile		since the Home Network prefix is an aggregation that encompasses all
	Network Prefixes will actually match both the Home Network prefix and		the MNPs, the Home Address actually matches both prefixes. To
	its Mobile Network prefix. To properly identify the Home Network,		properly identify the Home Network as it returns Home, the MR must
	the MR must expect a shorter prefix than that of the Mobile Network		expect a shorter prefix length than that of the MNP from which the
	from which the Home Address was formed.		Home Address was formed.
	When the Mobile Router forms its Home Address out of one of its
	Mobile Network Prefixes, since the Home Network prefix is an
	aggregation that encompasses all the MNPs, the Home Address actually
	matches both prefixes. As a result, the MR must expect a shorter
	prefix than that of the Mobile Network from which the Home Address
	was formed.
	6.2.1 Returning Home with the Egress interface		6.2.1 Returning Home with the Egress interface
	A Mobile Router coming Home via its Egress interface sees overlapping		A Mobile Router coming Home via its Egress interface sees overlapping
	prefixes between the Ingress and the Egress interface and some		prefixes between the Ingress and the Egress interface and some
	specific support may be needed:		specific support may be needed:
	When a Mobile Router connects to the Home Link using its Egress		When a Mobile Router connects to the Home Link using its Egress
	interface, it might set up a bridge between its Ingress interface(s)		interface, it might set up a bridge between its Ingress interface(s)
	and the Home Link, if the interfaces are compatible.		and the Home Link, if the interfaces are compatible.
	Alternatively, the Mobile Router might perform ND proxying for all		Alternatively, the Mobile Router might perform ND proxying for all
	addresses in its MNPs, between the Egress and the related Ingress		addresses in its MNPs, between the Egress and the related Ingress
	interface, as described in [12]. Since the prefixes on the Egress		interface, as described in [12]. Since the prefixes on the Egress
	and Ingress interfaces are overlapping, routing is disallowed.		and Ingress interfaces are overlapping, routing is disallowed.
	The Mobile Router does not need to join the local IGP when returning		The Mobile Router does not need to join the local IGP when returning
	Home, even if it is using the explicit Prefix Mode. When the Mobile		Home, even if it is using the explicit Prefix Mode. When the Mobile
	Router is not registered, the Home Agent simply expects that all MNNs		Router is not registered, the Home Agent simply expects that all
	will be reachable over the Home Link.		Mobile Network Nodes (MNNs) will be reachable over the Home Link.
	HA		HA
	|		|
	-------+--+--- /56		-------+--+--- /56
	|		|
	Egress |		Egress |
	MR at Home		MR at Home
	|		|
	--+--- /64		--+--- /64
	skipping to change at page 12, line 49 ¶		skipping to change at page 12, line 43 ¶
	includes the Aggregated Home Network prefix might use that prefix for		includes the Aggregated Home Network prefix might use that prefix for
	Address Autoconfiguration. Such a node would also install a		Address Autoconfiguration. Such a node would also install a
	connected route to the Aggregated Home Network over the Home Link.		connected route to the Aggregated Home Network over the Home Link.
	As a result, unless the node has a better (longest match) route to a		As a result, unless the node has a better (longest match) route to a
	given Mobile Network Prefix, it would lookup all MNNs on that MNP		given Mobile Network Prefix, it would lookup all MNNs on that MNP
	using Neighbor Discovery over its interface to the Home Link, and		using Neighbor Discovery over its interface to the Home Link, and
	fail.		fail.
	Thus, on the Home Link, the Home Agent must intercept all the packets		Thus, on the Home Link, the Home Agent must intercept all the packets
	to ALL the Mobile Network Nodes on the registered prefixes. In order		for ALL the Mobile Network Nodes on the registered prefixes - that is
	to do so, the Home Agent might perform some form of ND proxying for		for ALL nodes attached to Mobile Routers that are away from Home.
	all addresses in all registered Mobile Network Prefixes. The Home		This should be a layer 2 operation, rather than layer 3. The Home
	Agent must also protect the MNP space from autoconfiguration by		agent might, for example, perform some form of ND proxying for all
	uncontrolled visitors at Neighbor Discovery level.		addresses in all registered Mobile Network Prefixes.
	Alternatives based on a routing protocol or ICMP redirect may apply		The Home Agent must also protect the MNP space from autoconfiguration
	in some cases.		by uncontrolled visitors at Neighbor Discovery level.
	In any case, there is a need to provide a specific configuration on		There is a need to provide a specific configuration on the Home Agent
	the Home Agent to specify that it operates in Aggregated Mode. If a		to specify that it operates in Aggregated Mode. If a Home Agent
	Home Agent implementation is simply derived from that of MIP, then		implementation is simply derived from that of MIP, then the
	the capability to perform the required proxying might not exist, and		capability to perform the required proxying might not exist, and the
	the Aggregated Mode will not operate properly for nodes on the Home		Aggregated Mode will not operate properly for nodes on the Home Link.
	Link.
	6.4.2 Mobile Router side		6.4.2 Mobile Router side
	If the Mobile Router returns Home by Egress, a specific support is		If the Mobile Router returns Home by Egress, a specific support is
	required to control the bridging operation depending on whether a		required to control the bridging operation depending on whether a
	Mobile Router is at Home or not. This support might not be present		Mobile Router is at Home or not. This support might not be present
	in all implementations.		in all implementations.
			The NEMO Basic Support does not mention a specific behavior for
			bridging though Bridging capabilities can be expected from many
			implementations. An implementation might provide an automatic toggle
			to start/stop bridging on an egress interface when the mobile router
			comes back/leaves Home. When such a toggle is unavailable, then a
			specific interface should be reserved to attach to Home with the
			appropriate settings for security and bridging.
	Also, note that NEMO authorizes multiple registrations for a same MNP		Also, note that NEMO authorizes multiple registrations for a same MNP
	by different Mobile Routers. This is a case of multihoming, and it		by different Mobile Routers. This is a case of multihoming, and it
	normally means that the Mobile Routers are interconnected by the		normally means that the Mobile Routers are interconnected by the
	Ingress network that bears the common MNP. But there is no provision		Ingress network that bears the common MNP. But there is no provision
	in NEMO basic support to test that this condition is met at binding		in NEMO basic support to test that this condition is met at binding
	time and maintained over time.		time and maintained over time.
	It is thus possible for 2 different Mobile Routers to register the		It is thus possible for 2 different Mobile Routers to register the
	same prefix with different Home Addresses, and this will cause an		same prefix with different Home Addresses, and this will cause an
	undetected problem if the corresponding Ingress interfaces are not		undetected problem if the corresponding Ingress interfaces are not
	skipping to change at page 15, line 34 ¶		skipping to change at page 15, line 34 ¶
	Virtual Home Network have been proposed, but this topic is outside of		Virtual Home Network have been proposed, but this topic is outside of
	the scope of this document.		the scope of this document.
	7.2 Applicability		7.2 Applicability
	NEMO operations rely on ND extensions over the Home Link for the Home		NEMO operations rely on ND extensions over the Home Link for the Home
	Agent to Home Agent communication.		Agent to Home Agent communication.
	Making the Home Link virtual bars the deployment of multiple Home		Making the Home Link virtual bars the deployment of multiple Home
	Agents, which may be desirable for reasons of load balancing. Please		Agents, which may be desirable for reasons of load balancing. Please
	refer to the NEMO multihoming issues [13] draft for more on this.		refer to the NEMO multihoming issues [13] for more on this.
	Yet, for a deployment where a single Home Agent is enough, making the		Yet, for a deployment where a single Home Agent is enough, making the
	Home Link virtual reduces the vulnerability to some attacks and to		Home Link virtual reduces the vulnerability to some attacks and to
	some hardware failures, while making the Home Agent operation faster.		some hardware failures, while making the Home Agent operation faster.
	One should check with the product specifications of an Home Agent to		Note that NEMO basic does not mandate the support of Virtual Home
	see whether the implementation actually supports a Virtual Home		Networks.
	Network, and if so, whether in that cases, it is optimized for faster
	DAD-less bindings.
	8. Mobile Home		8. Mobile Home
	8.1 Configuration		8.1 Configuration
	In this arrangement, there is a bitwise hierarchy of Home Networks.		In this arrangement, there is a bitwise hierarchy of Home Networks.
	A global Home Network is advertised to the infrastructure by a head		A global Home Network is advertised to the infrastructure by a head
	Home Agent(s) and further subnetted into Mobile Networks. As a		Home Agent(s) and further subnetted into Mobile Networks. As a
	result, only the Home Agent(s) responsible for the most global		result, only the Home Agent(s) responsible for the most global
	(shortest prefix) aggregation receive all the packets for all the		(shortest prefix) aggregation receive all the packets for all the
	MNPs, which are leaves in the hierarchy tree.		MNPs, which are leaves in the hierarchy tree.
	Each subnet is owned by a Mobile Router that registers it in a NEMO		Each subnet is owned by a Mobile Router that registers it in a NEMO
	fashion while acting as a Home Agent for that network. This Mobile		fashion while acting as a Home Agent for that network This Mobile
	Router is at Home at the upper level of hierarchy. This		Router is at Home at the upper level of hierarchy. This
	configuration is referred to as Mobile Home.		configuration is referred to as Mobile Home.
	An example of this is the Cab Co configuration. Cab Co is a taxi		An example of this is the Cab Co configuration. Cab Co is a taxi
	Company that owns a /32 prefix, this prefix being advertised by the		Company that uses a /32 prefix for its Home Network, this prefix
	company Head Quarters. Regional offices are deployed around the		being advertised by the company Head Quarters. Regional offices are
	world. Even though these regional offices are relatively stable in		deployed around the coutry. Even though these regional offices are
	terms of location and prefix requirement -say this changes every few		relatively stable in terms of location and prefix requirement -say
	years- making them mobile allows a simpler management when a move has		this changes every few years- making them mobile allows a simpler
	to take place, or should the ISP service change.		management when a move has to take place, or should the ISP service
			change.
	global Home Network CAB:C0::/32 owned by HQ		To illustrate this configuration, we make up the prefixes to reflect
			their role, like CAB:C0::/32 for the Home Network:
			global Home Network CAB:C0::/32 advertised by HQ
	<------------------------------------------------------------------>		<------------------------------------------------------------------>
	HQ Extended Home Net Mobile Home for SFO office		HQ Extended Home Net Mobile Home for SFO office
	(casa)		(casa)
	CAB:C0:CA5A::/48 CAB:C0:5F0::/48		CAB:C0:CA5A::/48 CAB:C0:5F0::/48
	<----------------------------> ... <------------------------------->		<----------------------------> ... <------------------------------->
	|		|
	Home for offices HQ |		Home for offices HQ |
	CAB:C0:CA5A:CA5A::/64 MN |		CAB:C0:CA5A:CA5A::/64 MN |
	<----------------------><----> |		<----------------------><----> |
	skipping to change at page 19, line 12 ¶		skipping to change at page 19, line 12 ¶
	concerns. Please see [RFC3963] for security considerations for the		concerns. Please see [RFC3963] for security considerations for the
	NEMO Basic Support protocol.		NEMO Basic Support protocol.
	11. Changes		11. Changes
	An issue list is maintained at http://www.mobilenetworks.org/		An issue list is maintained at http://www.mobilenetworks.org/
	~pthubert/draft-ietf-nemo-home-network-models-issues.html .		~pthubert/draft-ietf-nemo-home-network-models-issues.html .
	11.1 Changes from version 00 to 01		11.1 Changes from version 00 to 01
	Removed terminology (moved to the Nemo terminology draft).		Removed terminology (moved to the Nemo terminology).
	Added an applicability statement for all documented cases		Added an applicability statement for all documented cases
	11.2 Changes from version 01 to 02		11.2 Changes from version 01 to 02
	Issue 1: Editorial		Issue 1: Editorial
	Issue 2: Added a caveat part in Extended and Aggregated Home Network		Issue 2: Added a caveat part in Extended and Aggregated Home Network
	sections. Also added a MIP Home Network section prior to those.		sections. Also added a MIP Home Network section prior to those.
	skipping to change at page 20, line 5 ¶		skipping to change at page 19, line 43 ¶
	11.5 Changes from version 04 to 05		11.5 Changes from version 04 to 05
	Issue 7: Virtual Home discussion		Issue 7: Virtual Home discussion
	Issue 8: Whether to recommend not to form a Home Address from MNP in		Issue 8: Whether to recommend not to form a Home Address from MNP in
	Extended HN.		Extended HN.
	Jari and Henrik's reviews Editorial changes		Jari and Henrik's reviews Editorial changes
			11.6 Changes from version 05 to 06 (IESG review)
			Issue 9: "Alternatives based on a routing protocol or ICMP redirect
			may apply in some cases." is not clear
			Issue 10: in a number of places text says "present in ...
			implementations" .. but what about the specifications?.
			Other review comments Editorial changes
	12. Acknowledgements		12. Acknowledgements
	The authors wish to thank:		The authors wish to thank:
	Erik Nordmark, Jari Arkko, Henrik Levkowetz, Kent Leung, Thierry		Erik Nordmark, Jari Arkko, Henrik Levkowetz, Scott Hollenbeck, Ted
	Ernst, TJ Kniveton, Patrick Wetterwald, Alexandru Petrescu and David		Hardie, David Kessens, Pekka Savola, Kent Leung, Thierry Ernst, TJ
	Binet for their contributions.		Kniveton, Patrick Wetterwald, Alexandru Petrescu and David Binet for
			their contributions.
	13. References		13. References
	13.1 normative reference		13.1 normative reference
	[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)		[2] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
	Specification", RFC 2460, December 1998.		Specification", RFC 2460, December 1998.
	skipping to change at page 20, line 43 ¶		skipping to change at page 21, line 44 ¶
	RFC 3753, June 2004.		RFC 3753, June 2004.
	[7] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[7] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[8] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,		[8] 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.
	[9] Ernst, T. and H. Lach, "Network Mobility Support Terminology",		[9] Ernst, T. and H. Lach, "Network Mobility Support Terminology",
	draft-ietf-nemo-terminology-03 (work in progress),		draft-ietf-nemo-terminology-04 (work in progress),
	February 2005.		October 2005.
	[10] Ernst, T., "Network Mobility Support Goals and Requirements",		[10] Ernst, T., "Network Mobility Support Goals and Requirements",
	draft-ietf-nemo-requirements-04 (work in progress),		draft-ietf-nemo-requirements-05 (work in progress),
	February 2005.		October 2005.
	13.2 informative reference		13.2 informative reference
	[11] Ng, C., "Network Mobility Route Optimization Problem		[11] Ng, C., "Network Mobility Route Optimization Problem
	Statement", draft-ietf-nemo-ro-problem-statement-00 (work in		Statement", draft-ietf-nemo-ro-problem-statement-02 (work in
	progress), July 2005.		progress), December 2005.
	[12] Thaler, D., "Neighbor Discovery Proxies (ND Proxy)",		[12] Thaler, D., "Neighbor Discovery Proxies (ND Proxy)",
	draft-ietf-ipv6-ndproxy-03 (work in progress), July 2005.		draft-ietf-ipv6-ndproxy-04 (work in progress), October 2005.
	[13] Ng, C., "Analysis of Multihoming in Network Mobility Support",		[13] Ng, C., "Analysis of Multihoming in Network Mobility Support",
	draft-ietf-nemo-multihoming-issues-03 (work in progress),		draft-ietf-nemo-multihoming-issues-04 (work in progress),
	July 2005.		October 2005.
	Authors' Addresses		Authors' Addresses
	Pascal Thubert		Pascal Thubert
	Cisco Systems		Cisco Systems
	Village d'Entreprises Green Side		Village d'Entreprises Green Side
	400, Avenue de Roumanille		400, Avenue de Roumanille
	Batiment T3		Batiment T3
	Biot - Sophia Antipolis 06410		Biot - Sophia Antipolis 06410
	FRANCE		FRANCE
	skipping to change at page 22, line 41 ¶		skipping to change at page 23, line 41 ¶
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject		Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		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 currently provided by the
	Internet Society.		Internet Society.
End of changes. 35 change blocks.
	96 lines changed or deleted		110 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/