< draft-thubert-tree-discovery-03.txt		draft-thubert-tree-discovery-04.txt >
	NEMO Working Group P. Thubert		NEMO Working Group P. Thubert
	Internet-Draft Cisco		Internet-Draft Cisco
	Expires: October 22, 2006 C. Bontoux		Expires: May 21, 2007 C. Bontoux
	Fortinet		Fortinet
	N. Montavont		N. Montavont
	LSIIT - ULP		LSIIT - ULP
	April 20, 2006		November 17, 2006
	Nested Nemo Tree Discovery		Nested Nemo Tree Discovery
	draft-thubert-tree-discovery-03.txt		draft-thubert-tree-discovery-04.txt
	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 October 22, 2006.		This Internet-Draft will expire on May 21, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	The purpose of this paper is to describe a minimum set of features		The purpose of this paper is to describe a minimum set of features
	that extends the Nemo basic support [4] in order to avoid loops in		that extends the Nemo basic support [4] in order to avoid loops in
	the nested Nemo case. As a result, Mobile Routers assemble into a		the nested Nemo case. As a result, Mobile Routers assemble into a
	skipping to change at page 2, line 24 ¶		skipping to change at page 2, line 24 ¶
	4. Router Advertisement extensions . . . . . . . . . . . . . . . 8		4. Router Advertisement extensions . . . . . . . . . . . . . . . 8
	4.1 Router Advertisement message . . . . . . . . . . . . . . . 8		4.1 Router Advertisement message . . . . . . . . . . . . . . . 8
	4.2 Tree Information Option . . . . . . . . . . . . . . . . . 8		4.2 Tree Information Option . . . . . . . . . . . . . . . . . 8
	4.3 TIO suboption . . . . . . . . . . . . . . . . . . . . . . 11		4.3 TIO suboption . . . . . . . . . . . . . . . . . . . . . . 11
	4.3.1 Format . . . . . . . . . . . . . . . . . . . . . . . . 11		4.3.1 Format . . . . . . . . . . . . . . . . . . . . . . . . 11
	4.3.2 Pad1 . . . . . . . . . . . . . . . . . . . . . . . . . 11		4.3.2 Pad1 . . . . . . . . . . . . . . . . . . . . . . . . . 11
	4.3.3 PadN . . . . . . . . . . . . . . . . . . . . . . . . . 12		4.3.3 PadN . . . . . . . . . . . . . . . . . . . . . . . . . 12
	4.3.4 Bandwidth Suboption . . . . . . . . . . . . . . . . . 12		4.3.4 Bandwidth Suboption . . . . . . . . . . . . . . . . . 12
	4.3.5 Stable time Suboption . . . . . . . . . . . . . . . . 13		4.3.5 Stable time Suboption . . . . . . . . . . . . . . . . 13
	4.3.6 Tree Group ID Suboption . . . . . . . . . . . . . . . 13		4.3.6 Tree Group ID Suboption . . . . . . . . . . . . . . . 14
			4.3.7 Path Free Medium Time Suboption . . . . . . . . . . . 14
	5. Tree Discovery . . . . . . . . . . . . . . . . . . . . . . . . 15		5. Tree Discovery . . . . . . . . . . . . . . . . . . . . . . . . 16
	5.1 tree selection . . . . . . . . . . . . . . . . . . . . . . 16		5.1 tree selection . . . . . . . . . . . . . . . . . . . . . . 17
	5.2 Sub-tree mobility . . . . . . . . . . . . . . . . . . . . 16		5.2 Sub-tree mobility . . . . . . . . . . . . . . . . . . . . 17
	5.3 Administrative depth . . . . . . . . . . . . . . . . . . . 17		5.3 Administrative depth . . . . . . . . . . . . . . . . . . . 18
	5.4 DRL entries states and stability . . . . . . . . . . . . . 17		5.4 DRL entries states and stability . . . . . . . . . . . . . 18
	5.4.1 Held-Up . . . . . . . . . . . . . . . . . . . . . . . 18		5.4.1 Held-Up . . . . . . . . . . . . . . . . . . . . . . . 19
	5.4.2 Held-Down . . . . . . . . . . . . . . . . . . . . . . 19		5.4.2 Held-Down . . . . . . . . . . . . . . . . . . . . . . 20
	5.4.3 Collision . . . . . . . . . . . . . . . . . . . . . . 19		5.4.3 Collision . . . . . . . . . . . . . . . . . . . . . . 20
	5.4.4 Instability . . . . . . . . . . . . . . . . . . . . . 20		5.4.4 Instability . . . . . . . . . . . . . . . . . . . . . 21
	5.5 Legacy Routers . . . . . . . . . . . . . . . . . . . . . . 20		5.5 Legacy Routers . . . . . . . . . . . . . . . . . . . . . . 21
	6. Directed Acyclic Graph Discovery . . . . . . . . . . . . . . . 20		6. Directed Acyclic Graph Discovery . . . . . . . . . . . . . . . 21
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 21		8. Security Considerations . . . . . . . . . . . . . . . . . . . 22
	9. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 21		9. Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
	9.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 21		9.1 Changes from version 00 to 01 . . . . . . . . . . . . . . 22
	9.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 21		9.2 Changes from version 01 to 02 . . . . . . . . . . . . . . 22
	9.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 21		9.3 Changes from version 02 to 03 . . . . . . . . . . . . . . 22
			9.4 Changes from version 03 to 04 . . . . . . . . . . . . . . 22
	10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 21		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 23
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 23		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
	11.1 Normative Reference . . . . . . . . . . . . . . . . . . . 23		11.1 Normative Reference . . . . . . . . . . . . . . . . . . . 24
	11.2 Informative Reference . . . . . . . . . . . . . . . . . . 23		11.2 Informative Reference . . . . . . . . . . . . . . . . . . 24
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 24
	Intellectual Property and Copyright Statements . . . . . . . . 25		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 25
			Intellectual Property and Copyright Statements . . . . . . . . 26
	1. Introduction		1. Introduction
	As per Nemo Basic support [4], a Mobile Router autoconfigures a		As per Nemo Basic support [4], a Mobile Router autoconfigures a
	single Care of Address (CoA) to register to its Home Agent and		single Care of Address (CoA) to register to its Home Agent and
	terminate its Mobile Router-Home Agent tunnel. That Care of Address		terminate its Mobile Router-Home Agent tunnel. That Care of Address
	is the Mobile Router point of attachment to the nested Nemo.		is the Mobile Router point of attachment to the nested Nemo.
	Consequently, if loops are avoided, the nested Nemo assumes the shape		Consequently, if loops are avoided, the nested Nemo assumes the shape
	of a tree. The nodes of the tree are Mobile Routers, the root is		of a tree. The nodes of the tree are Mobile Routers, the root is
	skipping to change at page 10, line 9 ¶		skipping to change at page 10, line 9 ¶
	Battery (B): The Battery (B) flag is indicates that a parent in the		Battery (B): The Battery (B) flag is indicates that a parent in the
	tree operates on batteries, an indication of a costly operation.		tree operates on batteries, an indication of a costly operation.
	It is set by a mobile router which operates on battery and when		It is set by a mobile router which operates on battery and when
	set, it is left set as it is propagated down the tree.		set, it is left set as it is propagated down the tree.
	Reserved: 13-bit unsigned integer set to 0 by the clusterhead.		Reserved: 13-bit unsigned integer set to 0 by the clusterhead.
	TreePreference: 8-bit unsigned integer set by the clusterhead to its		TreePreference: 8-bit unsigned integer set by the clusterhead to its
	preference and unchanged at propagation. Default is 0 (lowest		preference and unchanged at propagation. Default is 0 (lowest
	preference).		preference). The tree preference provides a mechanism to engineer
			the mesh of mobile routers, for instance indicating the most
			preferred home gateway or the communication ship in a fleet at
			sea.
	BootTimeRandom: A random value computed at boot time and recomputed		BootTimeRandom: A random value computed at boot time and recomputed
	in case of a duplication with another Attachment Router. The		in case of a duplication with another Attachment Router. The
	concatenation of the Preference and the BootTimeRandom is a 32-bit		concatenation of the Preference and the BootTimeRandom is a 32-bit
	extended preference that is used to resolve collisions. It is set		extended preference that is used to resolve collisions. It is set
	by each Mobile Router at propagation time.		by each Mobile Router at propagation time.
	Preference: The administrative preference of that (mobile) Access		Preference: The administrative preference of that (mobile) Access
	Router. Default is 0. 255 is the highest possible preference.		Router. Default is 0. 255 is the highest possible preference.
	Set by each Mobile Router at propagation time.		Set by each Mobile Router at propagation time.
	skipping to change at page 12, line 42 ¶		skipping to change at page 12, line 42 ¶
	Figure 5: Pad N		Figure 5: Pad N
	The PadN option is used to insert two or more octets of padding in		The PadN option is used to insert two or more octets of padding in
	the TIO to enable suboptions alignment. For N (N > 1) octets of		the TIO to enable suboptions alignment. For N (N > 1) octets of
	padding, the Option Length field contains the value N-2, and the		padding, the Option Length field contains the value N-2, and the
	Option Data consists of N-2 zero-valued octets. PadN Option data		Option Data consists of N-2 zero-valued octets. PadN Option data
	MUST be ignored by the receiver.		MUST be ignored by the receiver.
	4.3.4 Bandwidth Suboption		4.3.4 Bandwidth Suboption
	This suboption carries the bandwidth available up the tree via a		This suboption carries the maximum bandwidth available up the tree
	specific parent. The value is expressed in the log base 2 of the		via a specific parent. It is the lowest speed of the links on the
	speed, expressed in bps. The Bandwidth suboption does not have any		way and does not reflect the actual use of those links in run time.
	alignment requirements. Its format is as follows:		The value is expressed in the log base 2 of the speed, expressed in
			bps. The Bandwidth suboption does not have any alignment
			requirements. Its format is as follows:
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------+
	| Type = 2 | Length = 1 | Bandwidth |		| Type = 2 | Length = 1 | Bandwidth |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+---------------+
	Figure 6: Bandwidth Suboption		Figure 6: Bandwidth Suboption
	Type: Set to 2 for the Bandwidth suboption.		Type: Set to 2 for the Bandwidth suboption.
	Length: Set to 1 for the Bandwidth suboption.		Length: Set to 1 for the Bandwidth suboption.
	Bandwidth: 8-bit unsigned integer. The Log2 of the speed of the path		Bandwidth: 8-bit unsigned integer. The Log2 of the speed of the path
	expressed in bps. The clusterhead initializes that field using		expressed in bps. The clusterhead initializes that field using
	the speed of the link to the Access Router to which it is attached		the speed of the link to the Access Router to which it is attached
	or 0xFF if it is floating. An attached MR propagates it as the		or 0xFF if it is floating. An attached MR propagates it as the
	skipping to change at page 15, line 5 ¶		skipping to change at page 14, line 38 ¶
	Type: 8-bit unsigned integer. Its value is 4 for the Tree Group ID		Type: 8-bit unsigned integer. Its value is 4 for the Tree Group ID
	suboption.		suboption.
	Length: 8-bit unsigned integer. Its value is 16 for the Tree Group		Length: 8-bit unsigned integer. Its value is 16 for the Tree Group
	ID suboption.		ID suboption.
	Tree Group ID: 128-bit unsigned integer which identify a group for a		Tree Group ID: 128-bit unsigned integer which identify a group for a
	tree. This value is set by the clusterhead. It can be set		tree. This value is set by the clusterhead. It can be set
	administratively, for instance to an IPv6 multicast group.		administratively, for instance to an IPv6 multicast group.
			4.3.7 Path Free Medium Time Suboption
			This suboption carries the Free Medium Time available up the tree via
			a specific parent at a given point of time. It is an indication of
			whether bandwidth is available to place VoIP calls for instance. As
			defined by the Quality of Service (QoS) Task Group of the Wi-Fi
			Alliance, the Medium Time describes the amount of time admitted to
			access the medium, in units of 32 microsecond periods per second.
			The Free Medium Time is the amount of time left the medium, in other
			words ((1000000/32) - SIGMA(MT)). The Path Free Medium Time is the
			lowest available Free Medium Time along the way and it reflects the
			actual use of those links in run time.
			The Path Free Medium Time suboption does not have any alignment
			requirements. Its format is as follows:
			0 1 2 3
			0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Type = 5 | Length = 2 | Path Free Medium Time |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			Figure 9: Path Free Medium Time Suboption
			Type: Set to 5 for the Path Free Medium Time Suboption.
			Length: Set to 2 for the Path Free Medium Time Suboption.
			Path Free MT: 16-bit unsigned integer. The amount of Medium Time
			that is available along the path to the clusterhead in units of 32
			microsecond periods per second. The clusterhead initializes that
			field to the Free MT on the link where the TIO is issued. An
			attached MR propagates it as the minimum of the Path Free MT as
			received in the TIO from the parent and the Path Free MT on the
			link on which the TIO is propagated. As a result, the value
			received from a candidate AR is that of the bottleneck between
			that AR and the clusterhead.
	5. Tree Discovery		5. Tree Discovery
	Here follows a set of rules and definitions that MUST be followed by		Here follows a set of rules and definitions that MUST be followed by
	all Mobile Routers:		all Mobile Routers:
	1. A Mobile Router that is not attached to an Attachment Router is		1. A Mobile Router that is not attached to an Attachment Router is
	the Nemo clusterhead of its own floating tree. It's depth is 1.		the Nemo clusterhead of its own floating tree. It's depth is 1.
	2. A Mobile Router that is attached to an Attachment Router that		2. A Mobile Router that is attached to an Attachment Router that
	does not support TIO, is the clusterhead of its own grounded		does not support TIO, is the clusterhead of its own grounded
	skipping to change at page 15, line 30 ¶		skipping to change at page 16, line 30 ¶
	4. The Nemo clusterhead of a tree exposes the tree in the Router		4. The Nemo clusterhead of a tree exposes the tree in the Router
	Advertisement Tree Information Option and Mobile Routers		Advertisement Tree Information Option and Mobile Routers
	propagate the TIO down the tree with the RAs that they forward		propagate the TIO down the tree with the RAs that they forward
	over their ingress links.		over their ingress links.
	5. A Mobile Router that is already part of a tree MAY move at any		5. A Mobile Router that is already part of a tree MAY move at any
	time and with no delay in order to get closer to the clusterhead		time and with no delay in order to get closer to the clusterhead
	of its current tree - i.e. in order to reduce its own tree depth.		of its current tree - i.e. in order to reduce its own tree depth.
	But A Mobile Router MUST NOT move down the tree that it is		But A Mobile Router MUST NOT move down the tree that it is
	attached to. Mobile Routers MUST ignore RAs that are received		attached to. Mobile Routers MUST ignore RAs that are received
	from other routers located deeper or at the same depth within the		from other routers located deeper within the same tree.
	same tree.
	6. A Mobile Router may move from its current tree into any different		6. A Mobile Router may move from its current tree into any different
	tree at any time and whatever the depth it reaches in the new		tree at any time and whatever the depth it reaches in the new
	tree, but it may have to wait for a Tree Hop timer to elapse in		tree, but it may have to wait for a Tree Hop timer to elapse in
	order to do so. The Mobile Router will join that other tree if		order to do so. The Mobile Router will join that other tree if
	it is more preferable for reasons of connectivity, configured		it is more preferable for reasons of connectivity, configured
	preference, size, security, bandwidth, tree depth, or whatever		preference, free Medium Time, size, security, bandwidth, tree
	metrics the Mobile Router cares to use.		depth, or whatever metrics the Mobile Router cares to use.
	7. If a Mobile Router has selected a new attachment router but has		7. If a Mobile Router has selected a new attachment router but has
	not moved yet (because it is waiting for Tree Hop timer to		not moved yet (because it is waiting for Tree Hop timer to
	elapse), the Mobile Router is unstable and refrains from sending		elapse), the Mobile Router is unstable and refrains from sending
	Router Advertisement - Tree Information Options.		Router Advertisement - Tree Information Options.
	8. When A Mobile Router joins a tree, moves within its tree, or when		8. When A Mobile Router joins a tree, moves within its tree, or when
	it receives a modified TIO from its current attachment router,		it receives a modified TIO from its current attachment router,
	the Mobile Router sends an unsolicited Router Advertisement		the Mobile Router sends an unsolicited Router Advertisement
	message on all its mobile networks (i.e. all its ingress		message on all its mobile networks (i.e. all its ingress
	skipping to change at page 19, line 27 ¶		skipping to change at page 20, line 27 ¶
	5.4.3 Collision		5.4.3 Collision
	A race condition occurs if 2 Mobile Routers send Router Advertisement		A race condition occurs if 2 Mobile Routers send Router Advertisement
	- Tree Information Option at the same time and wish to join each		- Tree Information Option at the same time and wish to join each
	other. In order to detect the situation, Mobile Routers time stamp		other. In order to detect the situation, Mobile Routers time stamp
	the sending of Router Advertisement - Tree Information Option. Any		the sending of Router Advertisement - Tree Information Option. Any
	Router Advertisement - Tree Information Option received within a		Router Advertisement - Tree Information Option received within a
	short media-dependant period introduces a risk. To divide the risk,		short media-dependant period introduces a risk. To divide the risk,
	A 32bits extended preference is added in the TIO. The first byte is		A 32bits extended preference is added in the TIO. The first byte is
	the clusterhead preference, then the router own preference (default		the clusterhead preference, the remaining 24 bits is a boot time
	is 0 for both), the remaining 16 bits is a boot time computed		computed random.
	random.
	A Mobile Router that decides to join an Attachment Router will do so		A Mobile Router that decides to join an Attachment Router will do so
	between (Attachment Router depth) and (Attachment Router depth + 1)		between (Attachment Router depth) and (Attachment Router depth + 1)
	times the Attachment Router tree delay. But since a Mobile Router is		times the Attachment Router tree delay. But since a Mobile Router is
	unstable as soon as it receives the Router Advertisement - Tree		unstable as soon as it receives the Router Advertisement - Tree
	Information Option from the preferred Attachment Router, it will		Information Option from the preferred Attachment Router, it will
	restrain from sending a Router Advertisement - Tree Information		restrain from sending a Router Advertisement - Tree Information
	Option between the time it receives the RA and the time it actually		Option between the time it receives the RA and the time it actually
	jumps. So the crossing of RA may only happen during the propagation		jumps. So the crossing of RA may only happen during the propagation
	time between the Attachment Router and the Mobile Router, plus some		time between the Attachment Router and the Mobile Router, plus some
	skipping to change at page 21, line 45 ¶		skipping to change at page 22, line 41 ¶
	9.3 Changes from version 02 to 03		9.3 Changes from version 02 to 03
	Added suboptions for tree group, stable time and bandwidth.		Added suboptions for tree group, stable time and bandwidth.
	Added administrative depth and increment by more than 1.		Added administrative depth and increment by more than 1.
	Added words on bidirectional check using ND.		Added words on bidirectional check using ND.
	Added DAG discovery.		Added DAG discovery.
			9.4 Changes from version 03 to 04
			Added suboptions for Path Free Medium Time.
	10. Acknowledgments		10. Acknowledgments
	The authors wish to thank Marco Molteni and Patrick Wetterwald		The authors wish to thank Marco Molteni and Patrick Wetterwald
	(cisco) for their participation to this design and the review of the		(cisco) for their participation to this design and the review of the
	document, and Massimo Villari (university of Messina), for his early		document, and Massimo Villari (university of Messina), for his early
	work on simulation and research on the subject. This work is also		work on simulation and research on the subject. This work is also
	based on prior publications, in particular HMRA [8] by Hosik Cho and		based on prior publications, in particular HMRA [8] by Hosik Cho and
	Eun-Kyoung Paik from Seoul National University and other non IETF		Eun-Kyoung Paik from Seoul National University and other non IETF
	publications coauthored with Thierry Ernst and Thomas Noel. Finally,		publications coauthored with Thierry Ernst and Thomas Noel. Finally,
	thanks to Marcelo Bagnulo Braun for his constructive review.		thanks to Marcelo Bagnulo Braun for his constructive review.
	skipping to change at page 23, line 23 ¶		skipping to change at page 24, line 23 ¶
	Autoconfiguration", RFC 2462, December 1998.		Autoconfiguration", RFC 2462, December 1998.
	[3] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[3] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[4] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. Thubert,		[4] 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.
	[5] Ernst, T., "Network Mobility Support Goals and Requirements",		[5] 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.
	[6] Ernst, T. and H. Lach, "Network Mobility Support Terminology",		[6] Ernst, T. and H. Lach, "Network Mobility Support Terminology",
	draft-ietf-nemo-terminology-05 (work in progress), March 2006.		draft-ietf-nemo-terminology-06 (work in progress),
			November 2006.
	[7] Draves, R. and D. Thaler, "Default Router Preferences and More-		[7] Draves, R. and D. Thaler, "Default Router Preferences and More-
	Specific Routes", draft-ietf-ipv6-router-selection-07 (work in		Specific Routes", RFC 4191, November 2005.
	progress), January 2005.
	11.2 Informative Reference		11.2 Informative Reference
	[8] Cho, H., "Hierarchical Mobile Router Advertisement for nested		[8] Cho, H., "Hierarchical Mobile Router Advertisement for nested
	mobile networks", draft-cho-nemo-hmra-00 (work in progress),		mobile networks", draft-cho-nemo-hmra-00 (work in progress),
	January 2004.		January 2004.
	[9] Ng, C., "Analysis of Multihoming in Network Mobility Support",		[9] Ng, C., "Analysis of Multihoming in Network Mobility Support",
	draft-ietf-nemo-multihoming-issues-05 (work in progress),		draft-ietf-nemo-multihoming-issues-06 (work in progress),
	February 2006.		June 2006.
	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
End of changes. 24 change blocks.
	46 lines changed or deleted		96 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/