draft-ietf-dna-protocol-pre00.txt		draft-ietf-dna-protocol-00.txt
	DNA Working Group J. Kempf		DNA Working Group J. Kempf
	Internet-Draft DoCoMo Communications Labs USA		Internet-Draft DoCoMo Communications Labs USA
	Expires: June 11, 2006 S. Narayanan		Expires: August 30, 2006 S. Narayanan
	Panasonic		Panasonic
	E. Nordmark		E. Nordmark
	Sun Microsystems		Sun Microsystems
	B. Pentland, Ed.		B. Pentland, Ed.
	Monash University CTIE		Monash University CTIE
	J. Choi		JH. Choi
	Samsung AIT		Samsung AIT
	December 8, 2005		February 26, 2006
	Detecting Network Attachment in IPv6 Networks (DNAv6)		Detecting Network Attachment in IPv6 Networks (DNAv6)
	draft-ietf-dna-protocol-pre00.txt		draft-ietf-dna-protocol-00.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 41		skipping to change at page 1, line 41
	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 June 11, 2006.		This Internet-Draft will expire on August 30, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	Efficient detection of network attachment in IPv6 needs the following		Efficient detection of network attachment in IPv6 needs the following
	two components: a method for the host to query routers on the link to		two components: a method for the host to query routers on the link to
	identify the link (Link Identification) and a method for the routers		identify the link (Link Identification) and a method for the routers
	on the link to consistently respond to such a query with minimal		on the link to consistently respond to such a query with minimal
	delay (Fast RA). Solving the link identification based strictly on		delay (Fast RA). Solving the link identification based strictly on
	RFC 2461 is difficult because of the flexibility offered to routers		RFC 2461 is difficult because of the flexibility offered to routers
	in terms of prefixes advertised in a router advertisement (RA)		in terms of prefixes advertised in a router advertisement (RA)
	skipping to change at page 3, line 17		skipping to change at page 3, line 17
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
	2. Terms and Abbreviations . . . . . . . . . . . . . . . . . . 5		2. Terms and Abbreviations . . . . . . . . . . . . . . . . . . 5
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.1 Link Identification . . . . . . . . . . . . . . . . . . . 5		3.1 Link Identification . . . . . . . . . . . . . . . . . . . 5
	3.2 Fast Router Advertisement . . . . . . . . . . . . . . . . 7		3.2 Fast Router Advertisement . . . . . . . . . . . . . . . . 7
	4. Message Formats . . . . . . . . . . . . . . . . . . . . . . 8		4. Message Formats . . . . . . . . . . . . . . . . . . . . . . 8
	4.1 Router Advertisement . . . . . . . . . . . . . . . . . . . 8		4.1 Router Advertisement . . . . . . . . . . . . . . . . . . . 8
	4.2 Prefix Information Option LinkID Flag . . . . . . . . . . 9		4.2 Prefix Information Option LinkID Bit . . . . . . . . . . . 9
	4.3 Landmark Option . . . . . . . . . . . . . . . . . . . . . 10		4.3 Landmark Option . . . . . . . . . . . . . . . . . . . . . 10
	4.4 Learned Prefix Option . . . . . . . . . . . . . . . . . . 12		4.4 Learned Prefix Option . . . . . . . . . . . . . . . . . . 12
	5. DNA Operation . . . . . . . . . . . . . . . . . . . . . . . 13		5. DNA Operation . . . . . . . . . . . . . . . . . . . . . . . 13
	5.1 DNA Router Operation . . . . . . . . . . . . . . . . . . . 13		5.1 DNA Router Operation . . . . . . . . . . . . . . . . . . . 13
	5.1.1 Data Structures . . . . . . . . . . . . . . . . . . . 14		5.1.1 Data Structures . . . . . . . . . . . . . . . . . . . 14
	5.1.2 Router Configuration Variables . . . . . . . . . . . . 15		5.1.2 Router Configuration Variables . . . . . . . . . . . . 15
	5.1.3 Bootstrapping DNA Data Structures . . . . . . . . . . 16		5.1.3 Bootstrapping DNA Data Structures . . . . . . . . . . 16
	5.1.4 Processing Router Advertisements . . . . . . . . . . . 16		5.1.4 Processing Router Advertisements . . . . . . . . . . . 16
	5.1.5 Processing Router Solicitations . . . . . . . . . . . 17		5.1.5 Processing Router Solicitations . . . . . . . . . . . 17
	5.1.6 Complete Router Advertisements . . . . . . . . . . . . 18		5.1.6 Complete Router Advertisements . . . . . . . . . . . . 18
	5.1.7 LinkID Prefix . . . . . . . . . . . . . . . . . . . . 18		5.1.7 LinkID . . . . . . . . . . . . . . . . . . . . . . . . 18
	5.1.8 Scheduling Fast Router Advertisements . . . . . . . . 19		5.1.8 Scheduling Fast Router Advertisements . . . . . . . . 19
	5.1.9 Scheduling Unsolicited Router Advertisements . . . . . 20		5.1.9 Scheduling Unsolicited Router Advertisements . . . . . 20
	5.1.10 Removing a Prefix from an Interface . . . . . . . . 20		5.1.10 Removing a Prefix from an Interface . . . . . . . . 20
	5.1.11 Prefix Reassignment . . . . . . . . . . . . . . . . 21		5.1.11 Prefix Reassignment . . . . . . . . . . . . . . . . 21
	5.2 DNA Host Operation . . . . . . . . . . . . . . . . . . . . 21		5.2 DNA Host Operation . . . . . . . . . . . . . . . . . . . . 21
	5.2.1 Data Structures . . . . . . . . . . . . . . . . . . . 21		5.2.1 Data Structures . . . . . . . . . . . . . . . . . . . 21
	5.2.2 Host Configuration Variables . . . . . . . . . . . . . 22		5.2.2 Host Configuration Variables . . . . . . . . . . . . . 22
	5.2.3 Selection of a Landmark Prefix . . . . . . . . . . . . 22		5.2.3 Selection of a Landmark Prefix . . . . . . . . . . . . 22
	5.2.4 Sending Router Solicitations . . . . . . . . . . . . . 23		5.2.4 Sending Router Solicitations . . . . . . . . . . . . . 23
	5.2.5 Processing Router Advertisements . . . . . . . . . . . 23		5.2.5 Processing Router Advertisements . . . . . . . . . . . 23
	skipping to change at page 8, line 35		skipping to change at page 8, line 35
	routers on the link.		routers on the link.
	4. Message Formats		4. Message Formats
	This memo defines two new flags for inclusion in the router		This memo defines two new flags for inclusion in the router
	advertisement message and two new options.		advertisement message and two new options.
	4.1 Router Advertisement		4.1 Router Advertisement
	DNAv6 modifies the format of the Router Advertisement message by		DNAv6 modifies the format of the Router Advertisement message by
	adding a flag bit to indicate that the router sending the message is		defining a bit to indicate that the router sending the message is
	participating in the DNAv6 protocol as well as a flag to indicate the		participating in the DNAv6 protocol as well as a flag to indicate the
	completeness of the set of prefixes included in the Router		completeness of the set of prefixes included in the Router
	Advertisement. The new message format is as follows:		Advertisement. The new message format is as follows:
	0 1 2 3		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		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 | Code | Checksum |		| Type | Code | Checksum |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Cur Hop Limit |M|O|H|Pr |F|C|R| Router Lifetime |		| Cur Hop Limit |M|O|H|Pr |F|C|R| Router Lifetime |
	skipping to change at page 9, line 38		skipping to change at page 9, line 38
	contains PIOs for all prefixes explicitly configured on the		contains PIOs for all prefixes explicitly configured on the
	sending router, and, if other routers on the link are advertising		sending router, and, if other routers on the link are advertising
	additional prefixes, a Learned Prefix Option containing all		additional prefixes, a Learned Prefix Option containing all
	additional prefixes that the router has heard from other routers		additional prefixes that the router has heard from other routers
	on the link.		on the link.
	Reserved (R)		Reserved (R)
	The reserved field is reduced from 3 bits to 1 bit.		The reserved field is reduced from 3 bits to 1 bit.
	4.2 Prefix Information Option LinkID Flag		4.2 Prefix Information Option LinkID Bit
	DNAv6 modifies the format of the Prefix Information Option by adding		DNAv6 modifies the format of the Prefix Information Option by
	a flag bit to indicate that the enclosed prefix is currently being		defining a bit to indicate that the enclosed prefix is currently
	used as the Link Identifier. The new message format is as follows:		being used as the Link Identifier. The new message format is as
			follows:
	0 1 2 3		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		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 | Length | Prefix Length |L|A|I|Reserved1|		| Type | Length | Prefix Length |L|A|I|Reserved1|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Valid Lifetime |		| Valid Lifetime |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Preferred Lifetime |		| Preferred Lifetime |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 17, line 46		skipping to change at page 17, line 46
	5.1.5.1 Space Optimized Advertisements		5.1.5.1 Space Optimized Advertisements
	If the Router Solicitation contains a Landmark Option whose prefix is		If the Router Solicitation contains a Landmark Option whose prefix is
	included in DNARouterPrefixList or AdvPrefixList AND the		included in DNARouterPrefixList or AdvPrefixList AND the
	corresponding Router Advertisement will be unicast, the router MAY		corresponding Router Advertisement will be unicast, the router MAY
	send an abbreviated Router Advertisement.		send an abbreviated Router Advertisement.
	The abbreviated advertisement includes only the Landmark Option, with		The abbreviated advertisement includes only the Landmark Option, with
	the "Y" flag set, plus the base RA header and any SEND options as		the "Y" flag set, plus the base RA header and any SEND options as
	appropriate. The Complete flag MUST NOT be set. This is the one		appropriate. The Complete flag MUST NOT be set. This is the one
	exception where the LinkID prefix MAY be omitted as the Y flag		exception where the LinkID MAY be omitted as the Y flag implies that
	implies that link change has not occured.		link change has not occured.
	Some prefixes may also be omitted from unsolicited Router		Some prefixes may also be omitted from unsolicited Router
	Advertisements, as described in Section 5.1.9.		Advertisements, as described in Section 5.1.9.
	5.1.6 Complete Router Advertisements		5.1.6 Complete Router Advertisements
	A CompleteRA is formed as follows:		A CompleteRA is formed as follows:
	Starting with a Router Advertisement with all fixed options (MTU,		Starting with a Router Advertisement with all fixed options (MTU,
	Advertisement Interval, flags, etc.), the FastRA flag is set. As		Advertisement Interval, flags, etc.), the FastRA flag is set. As
	skipping to change at page 18, line 32		skipping to change at page 18, line 32
	If it is not possible to generate a Complete RA but the Router		If it is not possible to generate a Complete RA but the Router
	Solicitation that this Router Advertisement is in response to, if		Solicitation that this Router Advertisement is in response to, if
	any, includes a Landmark Option containing a prefix that is not in		any, includes a Landmark Option containing a prefix that is not in
	the router's DNARouterPrefixList and not in the router's		the router's DNARouterPrefixList and not in the router's
	AdvPrefixList then the router SHOULD include a Landmark Option with		AdvPrefixList then the router SHOULD include a Landmark Option with
	the "N" flag set. If there are known to be prefixes that are not		the "N" flag set. If there are known to be prefixes that are not
	included in the Router Advertisement, then the Complete flag MUST NOT		included in the Router Advertisement, then the Complete flag MUST NOT
	be set.		be set.
	Note that although it may not be possible to fit all of the prefixes		Note that although it may not be possible to fit all of the prefixes
	into an RA, the LinkID prefix MUST be included.		into an RA, the LinkID MUST be included.
	5.1.7 LinkID Prefix		5.1.7 LinkID
	One of the prefixes in use on a link is chosen to be the LinkID.		One of the prefixes in use on a link is chosen to be the LinkID.
	The LinkID is the numerically smallest prefix stored in either of		The LinkID is the numerically smallest prefix stored in either of
	DNARouterPrefixList or AdvPrefixList whose lifetime is greater than		DNARouterPrefixList or AdvPrefixList whose lifetime is greater than
	1.5 hours. For comparing prefixes, they are padded to the right with		1.5 hours. For comparing prefixes, they are padded to the right with
	zeros to make them 128 bit unsigned integers.		zeros to make them 128 bit unsigned integers.
	The prefix may be included in the RA in either a PIO or LPO as		The prefix may be included in the RA in either a PIO or LPO as
	appropriate. If the prefix is included in a PIO, then the "I" flag		appropriate. If the prefix is included in a PIO, then the "I" flag
	skipping to change at page 19, line 24		skipping to change at page 19, line 24
	advertisement is time T, then by T + 1 hour at least three such		advertisement is time T, then by T + 1 hour at least three such
	advertisements will have been made and all routers can be assumed to		advertisements will have been made and all routers can be assumed to
	have received it. Thus by time T + 1.5 hours, all routers on the		have received it. Thus by time T + 1.5 hours, all routers on the
	link should have also sent at least one advertisement with the new		link should have also sent at least one advertisement with the new
	LinkID.		LinkID.
	1.5 hours after first sending an advertisement with a new LinkID it		1.5 hours after first sending an advertisement with a new LinkID it
	is safe to consider the old LinkID gone and omit the corresponding		is safe to consider the old LinkID gone and omit the corresponding
	prefix from RAs if desired.		prefix from RAs if desired.
	Following a change of LinkID, the old LinkID prefix MUST be included		Following a change of LinkID, the old LinkID MUST be included in RAs
	in RAs for the following 1.5 hours.		for the following 1.5 hours.
	5.1.7.1.1 Non-Prefix LinkIDs		5.1.7.1.1 Non-Prefix LinkIDs
	Although this memo only discusses LinkIDs that are prefixes, a future		Although this memo only discusses LinkIDs that are prefixes, a future
	specification or ammendment may describe a mechanism to select a		specification or ammendment may describe a mechanism to select a
	LinkID that is not a prefix.		LinkID that is not a prefix.
	Information from the Learned Prefix Option is only stored in		Information from the Learned Prefix Option is only stored in
	DNAHostPrefixList, and is only used for DNA purposes. Because a		DNAHostPrefixList, and is only used for DNA purposes. Because a
	length field is used, it is possible to carry any variable length		length field is used, it is possible to carry any variable length
	identifier less than or equal to 128 bits in an LPO and store it in		identifier less than or equal to 128 bits in an LPO and store it in
	DNAHostPrefixList (Section 5.2.1).		DNAHostPrefixList (Section 5.2.1).
	Following a change of LinkID, the old LinkID prefix MUST be included		Following a change of LinkID, the old LinkID MUST be included in RAs
	in RAs in an LPO for the following 1.5 hours.		in an LPO for the following 1.5 hours.
	Future specifications MUST NOT treat the information in an LPO as		Future specifications MUST NOT treat the information in an LPO as
	prefixes such as they would the prefixes found in a Prefix		prefixes such as they would the prefixes found in a Prefix
	Information Option. Future specifications MUST NOT assume that the		Information Option. Future specifications MUST NOT assume that the
	entries in a host's DNAHostPrefixList are actaul prefixes in use on		entries in a host's DNAHostPrefixList are actaul prefixes in use on
	the link.		the link.
	5.1.8 Scheduling Fast Router Advertisements		5.1.8 Scheduling Fast Router Advertisements
	RAs may need to be delayed to avoid collisions in the case that there		RAs may need to be delayed to avoid collisions in the case that there
	skipping to change at page 20, line 37		skipping to change at page 20, line 37
	Complete RA, if it is not one already, and scheduled for multicast		Complete RA, if it is not one already, and scheduled for multicast
	transmission as in RFC 2461.		transmission as in RFC 2461.
	5.1.9 Scheduling Unsolicited Router Advertisements		5.1.9 Scheduling Unsolicited Router Advertisements
	Unsolicited router advertisements MUST be scheduled as per RFC 2461.		Unsolicited router advertisements MUST be scheduled as per RFC 2461.
	The "F" flag in the RA header MUST be set.		The "F" flag in the RA header MUST be set.
	They MAY be Complete RAs or MAY include only a subset of the		They MAY be Complete RAs or MAY include only a subset of the
	configured prefixes, but MUST include the LinkID prefix.		configured prefixes, but MUST include the LinkID.
	This ensures that there will be overlap in the sets of prefixes		This ensures that there will be overlap in the sets of prefixes
	contained in consecutive RAs on a link from DNA routers, and thus an		contained in consecutive RAs on a link from DNA routers, and thus an
	absence of that overlap can be used to infer link change.		absence of that overlap can be used to infer link change.
	5.1.10 Removing a Prefix from an Interface		5.1.10 Removing a Prefix from an Interface
	When a prefix is to stop being advertised in a PIO in RAs by an		When a prefix is to stop being advertised in a PIO in RAs by an
	interface before the expiry of the prefix's valid lifetime, then the		interface before the expiry of the prefix's valid lifetime, then the
	router should treat it as though it has just learned a prefix that is		router should treat it as though it has just learned a prefix that is
	skipping to change at page 23, line 23		skipping to change at page 23, line 23
	5.2.4 Sending Router Solicitations		5.2.4 Sending Router Solicitations
	Upon the occurrence of a Layer 2 link-up event notification, hosts		Upon the occurrence of a Layer 2 link-up event notification, hosts
	SHOULD send a Router Solicitation. Hosts SHOULD apply rate limiting		SHOULD send a Router Solicitation. Hosts SHOULD apply rate limiting
	and/or hysteresis to this behaviour as appropriate to the link		and/or hysteresis to this behaviour as appropriate to the link
	technology subject to the reliability of the hints.		technology subject to the reliability of the hints.
	Hosts SHOULD include a Landmark Option (LO) in the RS message with		Hosts SHOULD include a Landmark Option (LO) in the RS message with
	the landmark prefix chosen based on the rules in Section 5.2.3.		the landmark prefix chosen based on the rules in Section 5.2.3.
	Hosts MUST include a tentative source link layer address option		Hosts SHOULD include a tentative source link layer address option
	(TSLLAO) in the RS message [7]. The router solicitation message is		(TSLLAO) in the RS message [7]. The router solicitation message is
	sent to the All_Routers_Multicast address and the source address MUST		sent to the All_Routers_Multicast address and the source address MUST
	be the link local address of the host.		be the link local address of the host.
	The host MUST consider its link local address to be in the		The host MUST consider its link local address to be in the
	"Optimistic" state for duplicate address detection [6] until either		"Optimistic" state for duplicate address detection [6] until either
	the returned RA confirms that the host has not switched to a new link		the returned RA confirms that the host has not switched to a new link
	or, if an link change has occurred, the host has performed optimistic		or, if an link change has occurred, the host has performed optimistic
	duplicate address detection for the address.		duplicate address detection for the address.
	skipping to change at page 24, line 33		skipping to change at page 24, line 33
	contains no LinkID, then the host SHOULD use CPL logic to decide		contains no LinkID, then the host SHOULD use CPL logic to decide
	whether or not to reconfigure as described in [15].		whether or not to reconfigure as described in [15].
	If the destination address of the received RA is a unicast address,		If the destination address of the received RA is a unicast address,
	the host knows the router heard its RS, and hence it SHOULD mark that		the host knows the router heard its RS, and hence it SHOULD mark that
	router's Neighbor Cache Entry [3] as REACHABLE.		router's Neighbor Cache Entry [3] as REACHABLE.
	5.2.5.1 Maintaining the DNAHostPrefixList		5.2.5.1 Maintaining the DNAHostPrefixList
	If a Router Advertisement does not indicate a link change, the host		If a Router Advertisement does not indicate a link change, the host
	update its DNAHostPrefixList.		updates its DNAHostPrefixList, adding any new prefixes if necessary.
	If the Router Advertisement has the C flag set, then the host should		If the Router Advertisement has the C flag set, then the host SHOULD
	make the DNAHostPrefixList match the contents of the advertisement.		make the DNAHostPrefixList match the contents of the advertisement.
	Any new prefixes should be added and any prefixes in the list that		Any new prefixes are added and any prefixes in the list that are
	are absent in the advertisement should be removed. Expiry times on		absent in the advertisement are removed. Expiry times on prefixes
	prefixes should be updated if the prefix was contained in a PIO, but		are updated if the prefix was contained in a PIO, but not if it was
	not if it was contained in an LPO.		contained in an LPO.
	If the Router Advertisement does not have the C flag set, then the		If the Router Advertisement does not have the C flag set, then the
	host should add any new prefixes and update expiry times as above,		host SHOULD add any new prefixes and update expiry times as above,
	but should not remove any entries from DNAHostPrefixList.		but SHOULD NOT remove any entries from DNAHostPrefixList.
	When initiating reconfiguration due to link change, the host MUST		When initiating reconfiguration due to link change, the host MUST
	remove all prefixes in the DNAHostPrefixList and repopulate it with		remove all prefixes in the DNAHostPrefixList and repopulate it with
	the prefixes in the Prefix Information Options and Learned Prefix		the prefixes in the Prefix Information Options and Learned Prefix
	Option, if any, in the RA.		Option, if any, in the RA.
	5.2.6 DNA and Address Configuration		5.2.6 DNA and Address Configuration
	When a host moves to a new point of attachment, a potential exists		When a host moves to a new point of attachment, a potential exists
	for a change in the validity of its unicast and multicast addresses		for a change in the validity of its unicast and multicast addresses
	skipping to change at page 34, line 41		skipping to change at page 34, 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. 23 change blocks.
	32 lines changed or deleted		33 lines changed or added
This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/