draft-ietf-dhc-dhcpv6-remoteid-00.txt		draft-ietf-dhc-dhcpv6-remoteid-01.txt
	DHC B. Volz		DHC B. Volz
	Internet-Draft Cisco Systems, Inc.		Internet-Draft Cisco Systems, Inc.
	Expires: October 9, 2005 April 7, 2005		Expires: September 5, 2006 March 4, 2006
	DHCPv6 Relay Agent Remote ID Option		DHCPv6 Relay Agent Remote ID Option
	draft-ietf-dhc-dhcpv6-remoteid-00.txt		draft-ietf-dhc-dhcpv6-remoteid-01.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 33		skipping to change at page 1, line 33
	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 9, 2005.		This Internet-Draft will expire on September 5, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This memo defines a new Relay Agent Remote-ID option for the Dynamic		This memo defines a new Relay Agent Remote-ID option for the Dynamic
	Host Configuration Protocol for IPv6 (DHCPv6). This option is the		Host Configuration Protocol for IPv6 (DHCPv6). This option is the
	DHCPv6 equivalent for the Dynamic Host Configuration Protocol for		DHCPv6 equivalent for the Dynamic Host Configuration Protocol for
	IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified		IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified
	in RFC 3046.		in RFC 3046.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3		2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3
	3. The Relay Agent Remote-ID Option . . . . . . . . . . . . . . . 3		3. The Relay Agent Remote-ID Option . . . . . . . . . . . . . . . 3
	4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . 4		4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4
	5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4		5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 5
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 4		6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5		9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	9.1 Normative References . . . . . . . . . . . . . . . . . . . 5		9.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	9.2 Informative References . . . . . . . . . . . . . . . . . . 5		9.2. Informative References . . . . . . . . . . . . . . . . . . 6
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
	Intellectual Property and Copyright Statements . . . . . . . . 6		Intellectual Property and Copyright Statements . . . . . . . . . . 8
	1. Introduction		1. Introduction
	DHCPv6 [1] provides IP addresses and configuration information for		DHCPv6 [1] provides IP addresses and configuration information for
	IPv6 clients. It includes a relay agent capability, in which		IPv6 clients. It includes a relay agent capability, in which
	processes within the network infrastructure receive multicast		processes within the network infrastructure receive multicast
	messages from clients and relay them to DHCPv6 servers. In some		messages from clients and relay them to DHCPv6 servers. In some
	network environments, it will be useful for the relay agent to add		network environments, it will be useful for the relay agent to add
	information to the DHCPv6 message before relaying it.		information to the DHCPv6 message before relaying it.
	skipping to change at page 3, line 32		skipping to change at page 3, line 32
	2. Requirements Terminology		2. Requirements 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 [3].		document are to be interpreted as described in [3].
	3. The Relay Agent Remote-ID Option		3. The Relay Agent Remote-ID Option
	This option MAY be added by DHCPv6 relay agents which terminate		This option MAY be added by DHCPv6 relay agents which terminate
	switched or permanent circuits and have mechanisms to identify the		switched or permanent circuits and have mechanisms to identify the
	remote host end of the circuit. The remote-id field MAY be used to		remote host end of the circuit.
	encode, for instance:
	o a "caller ID" telephone number for dial-up connection
	o a "user name" prompted for by a Remote Access Server
	o a remote caller ATM address
	o a "modem ID" of a cable data modem
	o the remote IP address of a point-to-point link
	o a remote X.25 address for X.25 connections
	o an interface identity, which might be the switch's DUID [1]
	suffixed by the interface-id from the DHCPv6 Interface-Id option.
	The remote ID MUST be globally unique.
	The format of the DHCPv6 Relay Agent Remote-ID option is shown below:		The format of the DHCPv6 Relay Agent Remote-ID option is shown below:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OPTION_REMOTE_ID | option-len |		| OPTION_REMOTE_ID | option-len |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| enterprise-number |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	. .		. .
	. remote-id .		. remote-id .
	. .		. .
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	option-code OPTION_REMOTE_ID (TBD)		option-code OPTION_REMOTE_ID (TBD)
	option-len length, in octets, of the remote-id field.		option-len 4 + the length, in octets, of the remote-id
	The minimum length is 1 octet.		field. The minimum option-len is 5 octets.
	remote-id The opaque value for the globally unique		enterprise-number The vendor's registered Enterprise Number as
			registered with IANA [5].
			remote-id The opaque value for the remote-id.
			The definition of the remote-id carried in this option is vendor
			specific. The vendor is indicated in the enterprise-number field.
			The remote-id field MAY be used to encode, for instance:
			o a "caller ID" telephone number for dial-up connection
			o a "user name" prompted for by a Remote Access Server
			o a remote caller ATM address
			o a "modem ID" of a cable data modem
			o the remote IP address of a point-to-point link
			o a remote X.25 address for X.25 connections
			o an interface or port identifier
			Each vendor MUST assure that the remote-id is unique for their
			enterprise-number, as the octet sequence of enterprise-number
			followed by remote-id MUST be globally unique. One way to achieve
			uniqueness might be to include the relay agent's DUID [1] in the
	remote-id.		remote-id.
	4. DHCPv6 Relay Agent Behavior		4. DHCPv6 Relay Agent Behavior
	DHCPv6 relay agents MAY be configured to include a Remote-ID option		DHCPv6 relay agents MAY be configured to include a Remote-ID option
	in relayed (RELAY-FORW) DHCPv6 messages.		in relayed (RELAY-FORW) DHCPv6 messages.
	5. DHCPv6 Server Behavior		5. DHCPv6 Server Behavior
	This option provides additional information to the DHCPv6 server.		This option provides additional information to the DHCPv6 server.
	The DHCPv6 server, if it is configured to support this option, MAY		The DHCPv6 server, if it is configured to support this option, MAY
	use this information to select parameters specific to particular		use this information to select parameters specific to particular
	users, hosts, or subscriber modems. The remote-id SHOULD be		users, hosts, or subscriber modems. The combined enterprise-number
	considered an opaque value, with policies based on exact string match		and remote-id SHOULD be considered an opaque value, with policies
	only; that is, the option SHOULD NOT be internally parsed by the		based on exact string match only; that is, the remote-id field SHOULD
	server.		NOT be internally parsed by the server.
	There is no requirement that a server return this option and its data		There is no requirement that a server return this option and its data
	in a RELAY-REPLY message.		in a RELAY-REPLY message.
	6. Security Considerations		6. Security Considerations
	See [1] section 21.1, on securing DHCPv6 messages sent between		See [1] section 21.1, on securing DHCPv6 messages sent between
	servers and relay agents, and section 23, on general DHCPv6 security		servers and relay agents, and section 23, on general DHCPv6 security
	considerations. [2] discusses how this information can be used to		considerations. [2] discusses how this information can be used to
	enhance trust in some environments.		enhance trust in some environments.
			Note that even if the DHCP server trusts the relay agent not to
			modify information provided in this option, the confidence in that
			information is no higher than the confidence that the relay agent has
			in the information it puts in the option. For example, in some
			protocols it may be possible for a DHCP client to spoof or otherwise
			choose port identifiers, caller ID information, or other information
			carried in this option. Sites should consider such possible spoofing
			and how likely it is in their environment when deciding what uses of
			this option are appropriate.
	7. IANA Considerations		7. IANA Considerations
	IANA is requested to assign a DHCPv6 option code for the Relay Agent		IANA is requested to assign a DHCPv6 option code for the Relay Agent
	Remote-ID Option.		Remote-ID Option.
	8. Acknowledgements		8. Acknowledgements
	Thanks to Michael Patrick for [2], from which I've liberally borrowed		Thanks to Michael Patrick for [2], from which I've liberally borrowed
	text.		text.
	9. References		9. References
	9.1 Normative References		9.1. Normative References
	[1] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M.		[1] 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.
	[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,		[2] Patrick, M., "DHCP Relay Agent Information Option", RFC 3046,
	January 2001.		January 2001.
	[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[3] 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.
	9.2 Informative References		9.2. Informative References
	[4] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host		[4] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host
	Configuration Protocol (DHCP) version 6", RFC 3633,		Configuration Protocol (DHCP) version 6", RFC 3633,
	December 2003.		December 2003.
			[5] "IANA. Private Enterprise Numbers.",
			<http://www.iana.org/assignments/enterprise-numbers.html>.
	Author's Address		Author's Address
	Bernard Volz		Bernard Volz
	Cisco Systems, Inc.		Cisco Systems, Inc.
	1414 Massachusetts Ave.		1414 Massachusetts Ave.
	Boxborough, MA 01719		Boxborough, MA 01719
	USA		USA
	Phone: +1 978 936 0382		Phone: +1 978 936 0382
	Email: volz@cisco.com		Email: volz@cisco.com
	skipping to change at page 6, line 41		skipping to change at page 8, 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. 16 change blocks.
	36 lines changed or deleted		59 lines changed or added
This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/