< draft-ietf-nemo-dhcpv6-pd-01.txt		draft-ietf-nemo-dhcpv6-pd-02.txt >
	IPv6 Group R. Droms		IPv6 Group R. Droms
	Internet-Draft P. Thubert		Internet-Draft P. Thubert
	Expires: August 31, 2006 Cisco		Intended status: Informational Cisco
	February 27, 2006		Expires: April 1, 2007 September 28, 2006
	DHCPv6 Prefix Delegation for NEMO		DHCPv6 Prefix Delegation for NEMO
	draft-ietf-nemo-dhcpv6-pd-01		draft-ietf-nemo-dhcpv6-pd-02
	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 34 ¶		skipping to change at page 1, line 34 ¶
	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 August 31, 2006.		This Internet-Draft will expire on April 1, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	One aspect of network mobility support is the assignment of a prefix		One aspect of network mobility support is the assignment of a prefix
	or prefixes to a Mobile Router (MR) for use on the links in the		or prefixes to a Mobile Router (MR) for use on the links in the
	Mobile Network. DHCPv6 prefix delegation can be used for this		Mobile Network. DHCPv6 prefix delegation can be used for this
	skipping to change at page 5, line 9 ¶		skipping to change at page 5, line 9 ¶
	A new flag (D) (Support for DHCPv6PD) is introduced in the DHAAD		A new flag (D) (Support for DHCPv6PD) is introduced in the DHAAD
	Request message, defined in [RFC3775] and [RFC 3963]. The Mobile		Request message, defined in [RFC3775] and [RFC 3963]. The Mobile
	Router sets this flag to indicate that it wants to discover Home		Router sets this flag to indicate that it wants to discover Home
	Agents participating to DHCPv6 Prefix Delegation.		Agents participating to DHCPv6 Prefix Delegation.
	A the MR which sets the 'D' flag MUST also set the 'R' flag, to		A the MR which sets the 'D' flag MUST also set the 'R' flag, to
	declare that it is a Mobile Router and asks for a HA that supports		declare that it is a Mobile Router and asks for a HA that supports
	Mobile Routers, as defined in [RFC 3963].		Mobile Routers, as defined in [RFC 3963].
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Identifier |R|D| Reserved |		| Identifier |R|D| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	DHCPv6PD Support Flag (D)		DHCPv6PD Support Flag (D)
	A one-bit flag that when set indicates that the Mobile Router		A one-bit flag that when set indicates that the Mobile Router
	wants to discover Home Agents participating to DHCPv6 Prefix		wants to discover Home Agents participating to DHCPv6 Prefix
	Delegation.		Delegation.
	For a description of the other fields in the message, see [RFC3775]		For a description of the other fields in the message, see [RFC3775]
	and [RFC 3963].		and [RFC 3963].
	3.5.2. Modified Dynamic Home Agent Address Discovery Reply		3.5.2. Modified Dynamic Home Agent Address Discovery Reply
	A new flag (D) (Support for DHCPv6PD) is introduced in the DHAAD		A new flag (D) (Support for DHCPv6PD) is introduced in the DHAAD
	Reply message, defined in [RFC3775] and [RFC 3963]. If a Home Agent		Reply message, defined in [RFC3775] and [RFC 3963]. If a Home Agent
	receives a Dynamic Home Agent Discovery request message with the		receives a Dynamic Home Agent Discovery request message with the
	DHCPv6PD Support Flag set, it MUST reply with a list of Home Agents		DHCPv6PD Support Flag set, it MUST reply with a list of Home Agents
	skipping to change at page 6, line 5 ¶		skipping to change at page 6, line 5 ¶
	HAs would support Mobile Routers while others would be participating		HAs would support Mobile Routers while others would be participating
	to DHCPv6 Prefix Delegation but none could do both.		to DHCPv6 Prefix Delegation but none could do both.
	If none of the Home Agents support DHCPv6PD, the Home Agent MAY reply		If none of the Home Agents support DHCPv6PD, the Home Agent MAY reply
	with a list of Home Agents that only support NEMO basic Mobile		with a list of Home Agents that only support NEMO basic Mobile
	Routers or Mobile IPv6 Mobile Nodes. In this case, the DHCPv6PD		Routers or Mobile IPv6 Mobile Nodes. In this case, the DHCPv6PD
	Support Flag MUST be set to 0.		Support Flag MUST be set to 0.
	The modified message format is as follows.		The modified 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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Identifier |R|D| Reserved |		| Identifier |R|D| Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	+ +		+ +
	+ +		+ +
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	DHCPv6PD Support Flag (D)		DHCPv6PD Support Flag (D)
	A one-bit flag that when set indicates that the Home Agents		A one-bit flag that when set indicates that the Home Agents
	listed in this message participate to DHCPv6 Prefix Delegation.		listed in this message participate to DHCPv6 Prefix Delegation.
	For a description of the other fields in the message, see [RFC3775]		For a description of the other fields in the message, see [RFC3775]
	and [RFC 3963].		and [RFC 3963].
	3.5.3. Modified Home Agent Information Option		3.5.3. Modified Home Agent Information Option
	A new flag (D) (Support for DHCPv6PD) is introduced in the Home Agent		A new flag (D) (Support for DHCPv6PD) is introduced in the Home Agent
	Information Option defined in [RFC3775] and [RFC 3963].		Information Option defined in [RFC3775] and [RFC 3963].
	If a Home Agent participates to DHCPv6PD, it SHOULD set the flag. If		If a Home Agent participates to DHCPv6PD, it SHOULD set the flag. If
	skipping to change at page 9, line 27 ¶		skipping to change at page 9, line 29 ¶
	[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[2] 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.
	[3] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)		[3] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
	Addressing Architecture", RFC 3513, April 2003.		Addressing Architecture", RFC 3513, April 2003.
	[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in		[4] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support in
	IPv6", RFC 3775, June 2004.		IPv6", RFC 3775, June 2004.
	[5] Ernst, T. and H. Lach, "Network Mobility Support Terminology",		[5] Ernst, T. and H. Lach, "Network Mobility Support Terminology",
	draft-ietf-nemo-terminology-04 (work in progress), October 2005.		draft-ietf-nemo-terminology-05 (work in progress), March 2006.
	[6] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.		[6] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.
	Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",		Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
	RFC 3315, July 2003.		RFC 3315, July 2003.
	[7] Ernst, T., "Network Mobility Support Goals and Requirements",		[7] Ernst, T., "Network Mobility Support Goals and Requirements",
	draft-ietf-nemo-requirements-05 (work in progress),		draft-ietf-nemo-requirements-05 (work in progress),
	October 2005.		October 2005.
	[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] Droms, R., "DHCP Relay Agent Assignment Notification Option",		[9] Droms, R., "DHCPv6 Relay Agent Assignment Notification (RAAN)
	draft-ietf-dhc-dhcpv6-agentopt-delegate-00 (work in progress),		Option", draft-ietf-dhc-dhcpv6-agentopt-delegate-01 (work in
	January 2006.		progress), August 2006.
	Authors' Addresses		Authors' Addresses
	Ralph Droms		Ralph Droms
	Cisco		Cisco
	1414 Massachusetts Avenue		1414 Massachusetts Avenue
	Boxborough, MA 01719		Boxborough, MA 01719
	USA		USA
	Phone: +1 978.936.1674		Phone: +1 978.936.1674
	skipping to change at page 11, line 5 ¶		skipping to change at page 11, line 5 ¶
	Pascal Thubert		Pascal Thubert
	Cisco		Cisco
	Village d'Entreprises Green Side		Village d'Entreprises Green Side
	400, Avenue Roumanille		400, Avenue Roumanille
	Biot - Sophia Antipolis 06410		Biot - Sophia Antipolis 06410
	FRANCE		FRANCE
	Email: pthubert@cisco.com		Email: pthubert@cisco.com
	Intellectual Property Statement		Full Copyright Statement
			Copyright (C) The Internet Society (2006).
			This document is subject to the rights, licenses and restrictions
			contained in BCP 78, and except as set forth therein, the authors
			retain all their rights.
			This document and the information contained herein are provided on an
			"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
			OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
			ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
			INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
			INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
			WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
			Intellectual Property
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	skipping to change at page 11, line 29 ¶		skipping to change at page 11, line 45 ¶
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Disclaimer of Validity
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement
	Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is provided by the IETF
	Internet Society.		Administrative Support Activity (IASA).
End of changes. 14 change blocks.
	51 lines changed or deleted		51 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/