draft-ietf-dhc-host-gen-id-00.txt		draft-ietf-dhc-host-gen-id-01.txt
	Network Working Group S. Jiang		Network Working Group S. Jiang
	Internet-Draft F. Xia		Internet-Draft F. Xia
	Intended status: Standards Track B. Sarikaya		Intended status: Standards Track B. Sarikaya
	Expires: November 17, 2011 Huawei Technologies		Expires: May 24, 2012 Huawei Technologies
	May 16, 2011		November 21, 2011
	Prefix Assignment in DHCPv6		Prefix Assignment in DHCPv6
	draft-ietf-dhc-host-gen-id-00.txt		draft-ietf-dhc-host-gen-id-01.txt
	Abstract		Abstract
	This document describes a procedure for configuring hosts' IPv6		This document describes a procedure for configuring hosts' IPv6
	address which the prefix is assigned from a DHCPv6 server through		address which the prefix is assigned from a DHCPv6 server through
	DHCPv6 protocol while the interface identifiers are independently		DHCPv6 protocol while the interface identifiers are independently
	generated by the hosts. The method is applicable to		generated by the hosts. The method is applicable to
	Cryptographically Generated Addresses (CGA), and other IPv6 addresses		Cryptographically Generated Addresses (CGA), and other IPv6 addresses
	with host-generated interface identifiers.		with host-generated interface identifiers.
	skipping to change at page 1, line 36		skipping to change at page 1, line 36
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on November 17, 2011.		This Internet-Draft will expire on May 24, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 48		skipping to change at page 3, line 48
	probably got through Router Advertisement message defined in		probably got through Router Advertisement message defined in
	[RFC4861], or through DHCPv6 operations defined in this document.		[RFC4861], or through DHCPv6 operations defined in this document.
	[I-D.ietf-csi-dhcpv6-cga-ps] describes potential issues in the		[I-D.ietf-csi-dhcpv6-cga-ps] describes potential issues in the
	interaction between DHCPv6 and CGA. In that document , the usage of		interaction between DHCPv6 and CGA. In that document , the usage of
	DHCPv6 for assigning prefixes is proposed to facilitate separation of		DHCPv6 for assigning prefixes is proposed to facilitate separation of
	prefix assignment and interface identifier generation.		prefix assignment and interface identifier generation.
	There are also other host-generated IPv6 addresses, which are		There are also other host-generated IPv6 addresses, which are
	combined by prefixes obtained from network configuration and		combined by prefixes obtained from network configuration and
	ingerface identifiers generated by hosts, such as modified EUI-64		ingerface identifiers generated by hosts, such as modified EUI-64
	interface identifier [EUI-64], etc. The DHCPv6 operations defined in		interface identifier [EUI-64], temporary addresses for privacy
	this document also supports such address methods.		[RFC4941],etc. The DHCPv6 operations defined in this document also
			supports such address methods.
	The DHCPv6 operations defined in this document also supports the		The DHCPv6 operations defined in this document also supports the
	assigned prefix to be shared across multiple hosts.		assigned prefix to be shared across multiple hosts.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].		document are to be interpreted as described in [RFC2119].
	skipping to change at page 8, line 28		skipping to change at page 8, line 28
	model based on the recommendations in [RFC3314]. In this model, one		model based on the recommendations in [RFC3314]. In this model, one
	prefix can only be assigned to one interface of a host (mobile		prefix can only be assigned to one interface of a host (mobile
	station) and different hosts (mobile stations) can't share a prefix.		station) and different hosts (mobile stations) can't share a prefix.
	The unique prefix can be used to identify the host. It is not		The unique prefix can be used to identify the host. It is not
	necessary for a DHCPv6 server to generate an interface identifier for		necessary for a DHCPv6 server to generate an interface identifier for
	the host. The host may generate its interface identifier as		the host. The host may generate its interface identifier as
	described in [RFC4941]. An interface identifier could even be		described in [RFC4941]. An interface identifier could even be
	generated via random number generation.		generated via random number generation.
	Modified EUI-64 interface identifier [EUI-64] is also typically		Modified EUI-64 interface identifier [EUI-64] is also typically
	generated by hosts. The DHCPv6 operations defined in this document		generated by hosts. [RFC4941] has defined temporary addresses for
	also supports such address methods.		privacy purposes. The temporary addresses is also generated by hosts
			using random algorithm. The DHCPv6 operations defined in this
			document also supports such address methods.
	7. IANA consideration		7. IANA consideration
	This document defines a new DHCPv6 [RFC3315] option, which must be		This document defines a new DHCPv6 [RFC3315] option, which must be
	assigned Option Type values within the option numbering space for		assigned Option Type values within the option numbering space for
	DHCPv6 messages:		DHCPv6 messages:
	The OPTION_IA_PA Option (TBA1), described in Section 5.1.		The OPTION_IA_PA Option (TBA1), described in Section 5.1.
	8. Security Considerations		8. Security Considerations
	Security considerations in DHCPv6 are described in [RFC3315].		Security considerations in DHCPv6 are described in [RFC3315].
	To guard against attacks through prefix assignment, a host and a		To guard against attacks through prefix assignment, a host and a
	DHCPv6 server SHOULD use DHCPv6 authentication as described in		DHCPv6 server SHOULD use DHCPv6 authentication as described in
	Section 21, "Authentication of DHCP messages" of [RFC3315] or Secure		Section 21, "Authentication of DHCP messages" of [RFC3315] or Secure
	DHCPv6 [I-D.ietf-dhc-secure-dhcpv6] .		DHCPv6 [I-D.ietf-dhc-secure-dhcpv6] .
	9. Acknowledgements		9. Acknowledgements
	The authors would like to thanks Suresh Krishnan and other members of		The authors would like to thanks Suresh Krishnan, Ted Lemon and other
	DHC WG for their valuable comments.		members of DHC WG for their valuable comments.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,		[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
	"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,		"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
	skipping to change at page 10, line 4		skipping to change at page 10, line 4
	10.2. Informative references		10.2. Informative references
	[RFC4968] Madanapalli, S., "Analysis of IPv6 Link Models for 802.16		[RFC4968] Madanapalli, S., "Analysis of IPv6 Link Models for 802.16
	Based Networks", RFC 4968, August 2007.		Based Networks", RFC 4968, August 2007.
	[RFC3314] Wasserman, M., "Recommendations for IPv6 in Third		[RFC3314] Wasserman, M., "Recommendations for IPv6 in Third
	Generation Partnership Project (3GPP) Standards",		Generation Partnership Project (3GPP) Standards",
	RFC 3314, September 2002.		RFC 3314, September 2002.
	[I-D.ietf-csi-dhcpv6-cga-ps]		[I-D.ietf-csi-dhcpv6-cga-ps]
	Jiang, S., "DHCPv6 and CGA Interaction: Problem		Jiang, S., Shen, S., and T. Chown, "DHCPv6 and CGA
	Statement", draft-ietf-csi-dhcpv6-cga-ps-06 (work in		Interaction: Problem Statement",
	progress), October 2010.		draft-ietf-csi-dhcpv6-cga-ps-07 (work in progress),
			May 2011.
	[I-D.ietf-dhc-secure-dhcpv6]		[I-D.ietf-dhc-secure-dhcpv6]
	Jiang, S., "Secure DHCPv6 Using CGAs",		Jiang, S. and S. Shen, "Secure DHCPv6 Using CGAs",
	draft-ietf-dhc-secure-dhcpv6-02 (work in progress),		draft-ietf-dhc-secure-dhcpv6-03 (work in progress),
	December 2010.		June 2011.
	[EUI-64] "Guidelines for 64-bit Global Identifier (EUI-64)		[EUI-64] "Guidelines for 64-bit Global Identifier (EUI-64)
	Registration Authority", http://standards.ieee.org/		Registration Authority", http://standards.ieee.org/
	regauth/oui/tutorials/EUI64.html", March 1997.		regauth/oui/tutorials/EUI64.html", March 1997.
	Authors' Addresses		Authors' Addresses
	Sheng Jiang		Sheng Jiang
	Huawei Technologies		Huawei Technologies
	Huawei Building, No.3 Xinxi Rd.,		Q14, Huawei Campus, No.156, BeiQing Road
	Shang-Di Information Industry Base, Hai-Dian District, Beijing 100085		Hai-Dian District, Beijing 100095
	P.R. China		P.R. China
	Email: jiangsheng@huawei.com		Email: jiangsheng@huawei.com
	Frank Xia		Frank Xia
	Huawei Technologies		Huawei Technologies
	1700 Alma Dr. Suite 500		1700 Alma Dr. Suite 500
	Plano, TX 75075		Plano, TX 75075
	Email: xiayangsong@huawei.com		Email: xiayangsong@huawei.com
End of changes. 9 change blocks.
	18 lines changed or deleted		22 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/