draft-ietf-dhc-userclass-05.txt		draft-ietf-dhc-userclass-06.txt
	Internet Engineering Task Force Glenn Stump, IBM		Internet Engineering Task Force Glenn Stump, IBM
	INTERNET DRAFT Ralph Droms, Bucknell University		INTERNET DRAFT Ralph Droms, Bucknell University
	Date: February 2000 Ye Gu, Ramesh Vyaghrapuri,		Date: April 2000 Ye Gu, Ramesh Vyaghrapuri,
	Expires: July 2000 Ann Demirtjis, Microsoft		Expires: September 2000 Ann Demirtjis, Microsoft
	Burcak Beser, 3Com		Burcak Beser, 3Com
	Jerome Privat, BT		Jerome Privat, BT
	The User Class Option for DHCP		The User Class Option for DHCP
	<draft-ietf-dhc-userclass-05.txt>		<draft-ietf-dhc-userclass-06.txt>
	Status of this Memo		Status of this Memo
	The document is an Internet-Draft and is in full conformance with all		The document is an Internet-Draft and is in full conformance with all
	of the provisions of Section 10 of RFC 2026.		of the provisions of Section 10 of RFC 2026.
	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
	other groups may also distribute working documents as		other groups may also distribute working documents as
	Internet-Drafts.		Internet-Drafts.
	skipping to change at line 81		skipping to change at line 81
	differential services, such as network reachibility.		differential services, such as network reachibility.
	A DHCP server can also use the information contained in the User		A DHCP server can also use the information contained in the User
	Class to allocate other configuration parameters than the IP		Class to allocate other configuration parameters than the IP
	address. For example, a DHCP server receiving a request from a		address. For example, a DHCP server receiving a request from a
	client with the User Class set to "accounting auditors" may return		client with the User Class set to "accounting auditors" may return
	an option with the address of a particular database server.		an option with the address of a particular database server.
	Indeed a DHCP server may have a single pool of addresses and		Indeed a DHCP server may have a single pool of addresses and
	only use the user class to select parameters other than IP		only use the user class to select parameters other than IP
	addresses.		addresses.
	Note:
	This document combines ideas from draft-ietf-dhc-userclass-03.txt
	and draft-ietf-dhc-useraddr-00.txt. It has been published as a
	revision to draft-ietf-dhc-userclass-03.txt.
	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 RFC 2119 [3].		document are to be interpreted as described in RFC 2119 [3].
	3. DHCP Terminology		3. DHCP Terminology
	o "DHCP client"		o "DHCP client"
	skipping to change at line 125		skipping to change at line 120
	pool it allocates an address from and/or to select any other		pool it allocates an address from and/or to select any other
	configuration option.		configuration option.
	This option is a DHCP option [1, 2].		This option is a DHCP option [1, 2].
	This option MAY carry multiple User Classes.		This option MAY carry multiple User Classes.
	The code for this option is TBD.		The code for this option is TBD.
	Each User Class value is indicated in an opaque field and is		Each User Class value is indicated in an opaque field and is
	preceded by a one-byte field giving its length.		preceded by a one-byte field giving its length.
	If i is the number of User Classes carried in the option,		The length of the option as specified in Len must be the sum
	its total length N is equal to i + sum(Li).		of the lengths of each of the class names, starting with Len1
			through to the length of the last class.
	Code Len Len1 Len2		Code Len Len1 Len2
	+-----+-----+-----+----------+-----+--------------+----		+-----+-----+-----+----------+-----+--------------+----
	| TBD | N | L1 | class 1 | L2 | class 2 |...		| TBD | N | L1 | class 1 | L2 | class 2 |...
	+-----+-----+-----+----------+-----+--------------+----		+-----+-----+-----+----------+-----+--------------+----
	Servers not equipped to interpret the user class specified by		A server that is not equiped to interpret any given user class
	a client MUST ignore it (although it may be reported).		specified by a client MUST ignore it (although it may be reported).
			If a server recognizes one or more user classes specified by the
			client, but does not recognize one or more other user classes
			specified by the client, the server MAY use the user classes it
			recognizes.
	DHCP clients implementing this option SHOULD allow users to enter		DHCP clients implementing this option SHOULD allow users to enter
	their User Class.		one or more user class values.
	5. Security Considerations		5. Security Considerations
	DHCP currently provides no authentication or security		DHCP currently provides no authentication or security
	mechanisms. Potential exposures to attack are discussed		mechanisms. Potential exposures to attack are discussed
	is section 7 of the protocol specification [1].		is section 7 of the protocol specification [1].
	6. References		6. References
	[1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,		[1] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
	skipping to change at line 162		skipping to change at line 162
	[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," RFC 2119, March 1997.		Levels," RFC 2119, March 1997.
	7. Acknowledgments		7. Acknowledgments
	This document combines ideas from draft-ietf-dhc-userclass-03.txt		This document combines ideas from draft-ietf-dhc-userclass-03.txt
	(by Glenn Stump and Ralph Droms) and		(by Glenn Stump and Ralph Droms) and
	draft-ietf-dhc-useraddr-00.txt (by Ye Gu, Ramesh Vyaghrapuri and		draft-ietf-dhc-useraddr-00.txt (by Ye Gu, Ramesh Vyaghrapuri and
	Burcak Beser). It has been published as a revision to		Burcak Beser). It has been published as a revision to
	draft-ietf-dhc-userclass-03.txt.		draft-ietf-dhc-userclass-05.txt.
			Thanks to Ted Lemon, Steve Gonczi, and Barr Hibbs for their
			comments and suggestions.
	8. Author Information		8. Author Information
	Glenn Stump		Glenn Stump
	IBM Networking Software		IBM Networking Software
	P.O. Box 12195		P.O. Box 12195
	RTP, NC 27709		RTP, NC 27709
	Phone: (919) 301-4277		Phone: (919) 301-4277
	Email: stumpga@us.ibm.com		Email: stumpga@us.ibm.com
	skipping to change at line 218		skipping to change at line 220
	Jerome Privat		Jerome Privat
	BT Advanced Communications Technology Centre		BT Advanced Communications Technology Centre
	Adastral Park, Martlesham Heath, IP5 3RE		Adastral Park, Martlesham Heath, IP5 3RE
	UK		UK
	Phone: +44 1473 648910		Phone: +44 1473 648910
	Email: jerome.privat@bt.com		Email: jerome.privat@bt.com
	9. Expiration		9. Expiration
	This document will expire on July 2000.		This document will expire on September 2000.
			Copyright Statement
			Copyright (c) The Internet Society (1999). All Rights Reserved.
			This document and translations of it may be copied and furnished to
			others, and derivative works that comment on or otherwise explain it
			or assist in its implementation may be prepared, copied, published
			and distributed, in whole or in part, without restriction of any
			kind, provided that the above copyright notice and this paragraph are
			included on all such copies and derivative works. However, this
			document itself may not be modified in any way, such as by removing
			the copyright notice or references to the Internet Society or other
			Internet organizations, except as needed for the purpose of
			developing Internet standards in which case the procedures for
			copyrights defined in the Internet Standards process must be
			followed, or as required to translate it into languages other than
			English.
			The limited permissions granted above are perpetual and will not be
			revoked by the Internet Society or its successors or assigns.
			This document and the information contained herein is provided on an
			"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
			TASK FORCE DISCLAIMS 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.
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/