draft-ietf-radext-datatypes-04.txt		draft-ietf-radext-datatypes-05.txt
	Network Working Group DeKok, Alan		Network Working Group DeKok, Alan
	INTERNET-DRAFT FreeRADIUS		INTERNET-DRAFT FreeRADIUS
	Updates: 2865,3162,6158,6572		Updates: 2865,3162,6158,6572
	Category: Standards Track		Category: Standards Track
	<draft-ietf-radext-datatypes-04.txt>		<draft-ietf-radext-datatypes-05.txt>
	22 June 2016		21 July 2016
	Data Types in the Remote Authentication		Data Types in the Remote Authentication
	Dial-In User Service Protocol (RADIUS)		Dial-In User Service Protocol (RADIUS)
	draft-ietf-radext-datatypes-04.txt		draft-ietf-radext-datatypes-05.txt
	Abstract		Abstract
	RADIUS specifications have used data types for two decades without		RADIUS specifications have used data types for two decades without
	defining them as managed entities. During this time, RADIUS		defining them as managed entities. During this time, RADIUS
	implementations have named the data types, and have used them in		implementations have named the data types, and have used them in
	attribute definitions. This document updates the specifications to		attribute definitions. This document updates the specifications to
	better follow established practice. We do this by naming the data		better follow established practice. We do this by naming the data
	types defined in RFC 6158, which have been used since at least RFC		types defined in RFC 6158, which have been used since at least RFC
	2865. We provide an IANA registry for the data types, and update the		2865. We provide an IANA registry for the data types, and update the
	skipping to change at page 1, line 48 ¶		skipping to change at page 1, line 48 ¶
	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 January 22, 2017.		This Internet-Draft will expire on February 21, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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 6, line 45 ¶		skipping to change at page 6, line 45 ¶
	fields of attributes and data types. It then becomes clear that, for		fields of attributes and data types. It then becomes clear that, for
	example, that a field called "VSA-Data" must contain different data		example, that a field called "VSA-Data" must contain different data
	than a field called "EVS-Data". Each new name is defined where it is		than a field called "EVS-Data". Each new name is defined where it is
	used.		used.
	We also define the following term:		We also define the following term:
	Attr-Data		Attr-Data
	The "Value" field of an Attribute as defined in [RFC2865]		The "Value" field of an Attribute as defined in [RFC2865]
	Section 5. The contents of this field MUST be a valid data		Section 5. The contents of this field MUST be of a valid data
	type as defined in the RADIUS Data Type registry.		type as defined in the RADIUS Data Type registry.
	We consistently use "Attr-Data" to refer to the contents of an		We consistently use "Attr-Data" to refer to the contents of an
	attribute, instead of the more ambiguous name "Value". It is		attribute, instead of the more ambiguous name "Value". It is
	RECOMMENDED that new specifications follow this practice.		RECOMMENDED that new specifications follow this practice.
	In this document, we use the term "Value" to refer to the contents of		In this document, we use the term "Value" to refer to the contents of
	a data type, where that data type cannot carry other data types. In		a data type, where that data type cannot carry other data types. In
	other cases, we refer to the contents of a data type with a type-		other cases, we refer to the contents of a data type with a type-
	specific name, in order to distinguish it from data of other types.		specific name, in order to distinguish it from data of other types.
	skipping to change at page 29, line 22 ¶		skipping to change at page 29, line 22 ¶
	complete control over the contents and format of the Ext-Data		complete control over the contents and format of the Ext-Data
	field, while at the same time recommending that good practices		field, while at the same time recommending that good practices
	be followed.		be followed.
	Further codification of the range of allowed usage of this		Further codification of the range of allowed usage of this
	field is outside the scope of this specification.		field is outside the scope of this specification.
	4. Updated Registries		4. Updated Registries
	This section defines a new IANA registry for RADIUS data types, and		This section defines a new IANA registry for RADIUS data types, and
	updates the existing RADIUS Attribute Type registry.		then updates the existing RADIUS Attribute Type registry to use the
			data types from the new registry.
	4.1. Create a Data Type Registry		4.1. Create a Data Type Registry
	This section defines a new RADIUS registry, called "Data Type".		This section defines a new RADIUS registry, called "Data Type".
	Allocation in this registry requires IETF Review. The "Registration		Allocation in this registry requires IETF Review. The "Registration
	Procedures" for this registry are "Standards Action".		Procedures" for the Data Type Registry are "Standards Action".
	The registry contains three columns of data, as follows.		The Data Type Registry contains three columns of data, as follows.
	Value		Value
	The number of the data type. The value field is an artifact of		The number of the data type. The value field is an artifact of
	the registry, and has no on-the-wire meaning.		the registry, and has no on-the-wire meaning.
	Description		Description
	The name of the data type. The name field is used only for the		The name of the data type. The name field is used only for the
	registry, and has no on-the-wire meaning.		registry, and has no on-the-wire meaning.
	skipping to change at page 30, line 30 ¶		skipping to change at page 30, line 31 ¶
	4.2. Updates to the Attribute Type Registry		4.2. Updates to the Attribute Type Registry
	This section updates the RADIUS Attribute Type Registry to have a new		This section updates the RADIUS Attribute Type Registry to have a new
	column, which is inserted in between the existing "Description" and		column, which is inserted in between the existing "Description" and
	"Reference" columns. The new column is named "Data Type". The		"Reference" columns. The new column is named "Data Type". The
	contents of that column are the name of a data type, corresponding to		contents of that column are the name of a data type, corresponding to
	the attribute in that row, or blank if the attribute type is		the attribute in that row, or blank if the attribute type is
	unassigned. The name of the data type is taken from the RADIUS Data		unassigned. The name of the data type is taken from the RADIUS Data
	Type registry, defined above.		Type registry, defined above.
			The existing registration requirements for the Attribute Type
			Registry are unchanged.
	The updated registry follows in CSV format.		The updated registry follows in CSV format.
	Value,Description,Data Type,Reference		Value,Description,Data Type,Reference
	1,User-Name,text,[RFC2865]		1,User-Name,text,[RFC2865]
	2,User-Password,string,[RFC2865]		2,User-Password,string,[RFC2865]
	3,CHAP-Password,string,[RFC2865]		3,CHAP-Password,string,[RFC2865]
	4,NAS-IP-Address,ipv4addr,[RFC2865]		4,NAS-IP-Address,ipv4addr,[RFC2865]
	5,NAS-Port,integer,[RFC2865]		5,NAS-Port,integer,[RFC2865]
	6,Service-Type,enum,[RFC2865]		6,Service-Type,enum,[RFC2865]
	7,Framed-Protocol,enum,[RFC2865]		7,Framed-Protocol,enum,[RFC2865]
End of changes. 8 change blocks.
	8 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/