< draft-lior-radius-prepaid-extensions-14.txt		draft-lior-radius-prepaid-extensions-15.txt >
	RADEXT A. Lior		RADEXT A. Lior
	Internet-Draft Bridgewater Systems		Internet-Draft Bridgewater Systems
	Intended status: Informational P. Yegani		Intended status: Informational P. Yegani
	Expires: January 15, 2009 Cisco		Expires: May 5, 2009 Cisco
	K. Chowdhury		K. Chowdhury
	Starent Networks		Starent Networks
	H. Tschofenig		H. Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	A. Pashalidis		A. Pashalidis
	NEC		NEC
	July 14, 2008		November 1, 2008
	Prepaid Extensions to Remote Authentication Dial-In User Service		Prepaid Extensions to Remote Authentication Dial-In User Service
	(RADIUS)		(RADIUS)
	draft-lior-radius-prepaid-extensions-14.txt		draft-lior-radius-prepaid-extensions-15.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 42 ¶		skipping to change at page 1, line 42 ¶
	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 15, 2009.		This Internet-Draft will expire on May 5, 2009.
	Abstract		Abstract
	This document specifies an extension to the Remote Authentication		This document specifies an extension to the Remote Authentication
	Dial-In User Service (RADIUS) protocol that enables service providers		Dial-In User Service (RADIUS) protocol that enables service providers
	to charge for prepaid services. The supported charging models		to charge for prepaid services. The supported charging models
	supported are volume-based, duration-based, and based on one-time		supported are volume-based, duration-based, and based on one-time
	events.		events.
	Table of Contents		Table of Contents
	skipping to change at page 37, line 15 ¶		skipping to change at page 37, line 15 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(2)		SubType : Value(1)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type String		VALUE : Data type String
	Quota Identifier (QID) SubType		Quota Identifier (QID) SubType
	4.3.2. VolumeQuota SubType		4.3.2. VolumeQuota SubType
	TVolumeQuota SubType is only present when volume-based charging is		TVolumeQuota SubType is only present when volume-based charging is
	skipping to change at page 37, line 41 ¶		skipping to change at page 37, line 41 ¶
	NOT encode a negative number or zero.		NOT encode a negative number or zero.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(3)		SubType : Value(2)
	LENGTH : variable (8 or 14)		LENGTH : variable (8 or 14)
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field either contains the		The content of the VALUE field either contains the
	Value-Digits SubType or the Value-Digits SubType plus the		Value-Digits SubType or the Value-Digits SubType plus the
	Exponent SubType. The length field indicates whether one or		Exponent SubType. The length field indicates whether one or
	both subtypes are included.		both subtypes are included.
	skipping to change at page 38, line 25 ¶		skipping to change at page 38, line 25 ¶
	SubType, if present, MUST NOT encode a negative number or zero.		SubType, if present, MUST NOT encode a negative number or zero.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(4)		SubType : Value(3)
	LENGTH : variable (8 or 14)		LENGTH : variable (8 or 14)
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field either contains the		The content of the VALUE field either contains the
	Value-Digits SubType or the Value-Digits SubType plus the		Value-Digits SubType or the Value-Digits SubType plus the
	Exponent SubType. The length field indicates whether one or		Exponent SubType. The length field indicates whether one or
	both subtypes are included.		both subtypes are included.
	skipping to change at page 39, line 15 ¶		skipping to change at page 39, line 15 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(5)		SubType : Value(4)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type string.		VALUE : Data type string.
	The content of this field contains a 32-bit unsigned integer		The content of this field contains a 32-bit unsigned integer
	(with the values 0 to +4,294,967,295).		(with the values 0 to +4,294,967,295).
	DurationQuota SubType		DurationQuota SubType
	skipping to change at page 39, line 44 ¶		skipping to change at page 39, line 44 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(6)		SubType : Value(5)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type string.		VALUE : Data type string.
	The content of this field contains a 32-bit unsigned integer		The content of this field contains a 32-bit unsigned integer
	(with the values 0 to +4,294,967,295).		(with the values 0 to +4,294,967,295).
	DurationThreshold SubType		DurationThreshold SubType
	skipping to change at page 40, line 28 ¶		skipping to change at page 40, line 28 ¶
	field).		field).
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(7)		SubType : Value(6)
	LENGTH : variable (8 or 14)		LENGTH : variable (8 or 14)
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field either contains the		The content of the VALUE field either contains the
	Value-Digits SubType or the Value-Digits SubType plus the		Value-Digits SubType or the Value-Digits SubType plus the
	Exponent SubType. The length field indicates whether one or		Exponent SubType. The length field indicates whether one or
	both subtypes are included.		both subtypes are included.
	skipping to change at page 41, line 13 ¶		skipping to change at page 41, line 13 ¶
	VolumeThreshold and DurationThreshold SubType.		VolumeThreshold and DurationThreshold SubType.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(8)		SubType : Value(7)
	LENGTH : variable (8 or 14)		LENGTH : variable (8 or 14)
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field either contains the		The content of the VALUE field either contains the
	Value-Digits SubType or the Value-Digits SubType plus the		Value-Digits SubType or the Value-Digits SubType plus the
	Exponent SubType. The length field indicates whether one or		Exponent SubType. The length field indicates whether one or
	both subtypes are included.		both subtypes are included.
	skipping to change at page 42, line 15 ¶		skipping to change at page 42, line 15 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(9)		SubType : Value(18)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type string.		VALUE : Data type string.
	The content of this field contains a 32-bit unsigned integer		The content of this field contains a 32-bit unsigned integer
	(with the values 0 to +4,294,967,295).		(with the values 0 to +4,294,967,295).
	Value-Digits SubType		Value-Digits SubType
	skipping to change at page 42, line 41 ¶		skipping to change at page 42, line 41 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(10)		SubType : Value(19)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type string.		VALUE : Data type string.
	The content of this field contains a 32-bit signed integer		The content of this field contains a 32-bit signed integer
	(with the values -2,147,483,648 to +2,147,483,647).		(with the values -2,147,483,648 to +2,147,483,647).
	Exponent SubType		Exponent SubType
	skipping to change at page 43, line 22 ¶		skipping to change at page 43, line 22 ¶
	the RADIUS Access-Accept message.		the RADIUS Access-Accept message.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE |		| SubType | LENGTH | VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(11)		SubType : Value(8)
	LENGTH : 4		LENGTH : 4
	VALUE : Data type string		VALUE : Data type string
	This field contains a 16-bit unsigned integer		This field contains a 16-bit unsigned integer
	(with the values 0 to +65,535).		(with the values 0 to +65,535).
	Update-Reason SubType		Update-Reason SubType
	skipping to change at page 44, line 25 ¶		skipping to change at page 44, line 25 ¶
	values are present, the PPC MUST NOT change their order.		values are present, the PPC MUST NOT change their order.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Address ...		| SubType | LENGTH | Address ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(12)		SubType : Value(9)
	LENGTH : variable (6 or 14)		LENGTH : variable (6 or 14)
	Address : Data type String		Address : Data type String
	For IPv4, the Address field is 4 octets based on the encoding of		For IPv4, the Address field is 4 octets based on the encoding of
	the NAS-IP-Address defined in RFC 2138. For IPv6, the Address		the NAS-IP-Address defined in RFC 2138. For IPv6, the Address
	field is 16 octets long.		field is 16 octets long.
	PrepaidServer SubType		PrepaidServer SubType
	skipping to change at page 45, line 13 ¶		skipping to change at page 45, line 13 ¶
	Service".		Service".
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Service ...		| SubType | LENGTH | Service ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(13)		SubType : Value(10)
	LENGTH : variable		LENGTH : variable
	Service : Data type String		Service : Data type String
	Service-ID SubType		Service-ID SubType
	4.3.13. Rating-Group-ID SubType		4.3.13. Rating-Group-ID SubType
	The Rating-Group-ID SubType indicates that this PPAQ attribute is		The Rating-Group-ID SubType indicates that this PPAQ attribute is
	skipping to change at page 45, line 38 ¶		skipping to change at page 45, line 38 ¶
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| VALUE |		| VALUE |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(14)		SubType : Value(11)
	LENGTH : 6		LENGTH : 6
	VALUE : Data type string		VALUE : Data type string
	Rating-Group-ID SubType		Rating-Group-ID SubType
	4.3.14. Termination-Action SubType		4.3.14. Termination-Action SubType
	The value of the type field of the Termination-Action SubType is TBD.		The value of the type field of the Termination-Action SubType is TBD.
	skipping to change at page 46, line 13 ¶		skipping to change at page 46, line 13 ¶
	additional quota. Valid actions are as follows.		additional quota. Valid actions are as follows.
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Action |		| SubType | LENGTH | Action |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(15)		SubType : Value(12)
	LENGTH : 3		LENGTH : 3
	Action : Data type string.		Action : Data type string.
	The content is an 8 bit unsigned integer (with the values 0 to +255).		The content is an 8 bit unsigned integer (with the values 0 to +255).
	Termination-Action SubType		Termination-Action SubType
	The following values for the Termination-Action SubType are defined:		The following values for the Termination-Action SubType are defined:
	skipping to change at page 47, line 13 ¶		skipping to change at page 47, line 13 ¶
	string.		string.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Poolid |		| SubType | LENGTH | Poolid |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(16)		SubType : Value(13)
	LENGTH : 6		LENGTH : 6
	Poolid : Data type string		Poolid : Data type string
	Pool-ID SubType		Pool-ID SubType
	4.3.16. Pool-Multiplier SubType		4.3.16. Pool-Multiplier SubType
	The Pool-Multiplier SubType determines the weight of resources when		The Pool-Multiplier SubType determines the weight of resources when
	skipping to change at page 47, line 36 ¶		skipping to change at page 47, line 36 ¶
	taken out of the pool by the relevant Service or Rating-Group.		taken out of the pool by the relevant Service or Rating-Group.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(17)		SubType : Value(14)
	LENGTH : variable (8 or 14)		LENGTH : variable (8 or 14)
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field either contains the		The content of the VALUE field either contains the
	Value-Digits SubType or the Value-Digits SubType plus the		Value-Digits SubType or the Value-Digits SubType plus the
	Exponent SubType. The length field indicates whether one or		Exponent SubType. The length field indicates whether one or
	both subtypes are included.		both subtypes are included.
	skipping to change at page 48, line 23 ¶		skipping to change at page 48, line 23 ¶
	indicated action is requested.		indicated action is requested.
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Action |		| SubType | LENGTH | Action |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(18)		SubType : Value(15)
	LENGTH : 3		LENGTH : 3
	Action : Data type string.		Action : Data type string.
	The content is a 8 bit unsigned integer (with the values 0 to +255)		The content is a 8 bit unsigned integer (with the values 0 to +255)
	with the values listed below.		with the values listed below.
	Requested-Action SubType		Requested-Action SubType
	skipping to change at page 49, line 16 ¶		skipping to change at page 49, line 16 ¶
	quota is reserved by the PPS.		quota is reserved by the PPS.
	0 1 2		0 1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Decision |		| SubType | LENGTH | Decision |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(19)		SubType : Value(16)
	LENGTH : 3		LENGTH : 3
	Decision : Data type string.		Decision : Data type string.
	The content is a 8 bit unsigned integer (with the values 0 to +255)		The content is a 8 bit unsigned integer (with the values 0 to +255)
	with the values listed below.		with the values listed below.
	Check-Balance-Result SubType		Check-Balance-Result SubType
	skipping to change at page 50, line 13 ¶		skipping to change at page 50, line 13 ¶
	SubType.		SubType.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | VALUE ...		| SubType | LENGTH | VALUE ...
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(20)		SubType : Value(17)
	LENGTH : variable		LENGTH : variable
	VALUE : Data type String		VALUE : Data type String
	The content of the VALUE field contains (in this order) the		The content of the VALUE field contains (in this order) the
	Value-Digits SubType, followed by the		Value-Digits SubType, followed by the
	Exponent SubType, Currency-Code SubType and the Cost-Unit SubType.		Exponent SubType, Currency-Code SubType and the Cost-Unit SubType.
	Cost-Information SubType		Cost-Information SubType
	skipping to change at page 51, line 13 ¶		skipping to change at page 51, line 13 ¶
	standard.		standard.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| SubType | LENGTH | Code |		| SubType | LENGTH | Code |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	The fields have the following meaning and encoding:		The fields have the following meaning and encoding:
	SubType : Value(21)		SubType : Value(20)
	LENGTH : 4		LENGTH : 4
	Code : Data type string		Code : Data type string
	The content of the Code field is a 16-bit unsigned integer		The content of the Code field is a 16-bit unsigned integer
	(with the values 0 to +65,535).		(with the values 0 to +65,535).
	Currency-Code SubType		Currency-Code SubType
	skipping to change at page 58, line 13 ¶		skipping to change at page 58, line 13 ¶
	accounting and improper access to the network or other services.		accounting and improper access to the network or other services.
	7. Table of Attributes		7. Table of Attributes
	The following table provides a guide which attributes may be found in		The following table provides a guide which attributes may be found in
	which RADIUS messages, and in what quantity.		which RADIUS messages, and in what quantity.
	Request Accept Reject Challenge Accounting # Attribute		Request Accept Reject Challenge Accounting # Attribute
	Request		Request
	0-1 0 0 0 0 35 PPAC		0-1 0 0 0 0 35 PPAC
	0+ 0+ 0 0 0+ 37 PPAQ
	0+ 0+ 0 0 0+ 38 PTS
	0-1 0 0 0 0 36 Session Termination		0-1 0 0 0 0 36 Session Termination
	Capability		Capability
			0+ 0+ 0 0 0+ 37 PPAQ
			0+ 0+ 0 0 0+ 38 PTS
	8. IANA Considerations		8. IANA Considerations
	This document contains a number of instructions to IANA.		This document contains a number of instructions to IANA.
	8.1. RADIUS Attributes		8.1. RADIUS Attributes
	This document does not require IANA to register the following four		This document does not require IANA to register the following four
	RADIUS attributes as the code registered by the Wimax Forum is re-		RADIUS attributes as the code registered by the Wimax Forum is re-
	used. The Wimax Forum SMI Network Management Private Enterprise Code		used. The Wimax Forum SMI Network Management Private Enterprise Code
	is 24757.		is 24757.
	Attribute Name | Attribute Type Value		Attribute Name | Attribute Type Value
	--------------------------------------+-----------------------------		--------------------------------------+-----------------------------
	Prepaid-Accounting-Capability (PPAC) | 35		Prepaid-Accounting-Capability (PPAC) | 35
			Session Termination Capability | 36
	Prepaid-Accounting-Operation (PPAQ) | 37		Prepaid-Accounting-Operation (PPAQ) | 37
	Prepaid Tariff Switching (PTS) | 38		Prepaid Tariff Switching (PTS) | 38
	Session Termination Capability | 36
	8.2. New Registry: RADIUS Prepaid SubTypes		8.2. New Registry: PPAC SubTypes
	Section 4 defines the SubTypes used within newly defined attributes.		Section 4.1 defines the SubTypes used within the PPAC attribute.
	IANA is asked to create a registry for these SubTypes. Each registry		IANA is asked to create a registry for these SubTypes. Each registry
	entry consists of a 8 bit number together with a description of the		entry consists of a 8 bit number together with a description of the
	SubType. This document creates the following SubTypes for this		PPAC SubType. This document creates the following PPAC SubTypes for
	registry:		this registry:
	Value | SubType Name		Value | SubType Name
	---------+-----------------------------		---------+-----------------------------
	0 | Reserved		0 | Reserved
	1 | AvailableInClient		1 | AvailableInClient
	2 | Quota Identifier		2..255 | **Available for IANA registration**
	3 | VolumeQuota
	4 | VolumeThreshold
	5 | DurationQuota
	6 | DurationThreshold
	7 | ResourceQuota
	8 | ResourceThreshold
	9 | Value-Digits
	10 | Exponent
	11 | Update-Reason
	12 | PrepaidServer
	13 | Service-ID
	14 | Rating-Group-ID
	15 | Termination-Action
	16 | Pool-ID
	17 | Pool-Multiplier
	18 | Requested-Action
	19 | Check-Balance-Result
	20 | Cost-Information
	21 | Currency-Code
	22 | Cost-Unit
	23 | VolumeUsedAfterTariffSwitch
	24 | TariffSwitchInterval
	25 | TimeIntervalafterTariffSwitchUpdate
	26..255 | **Available for IANA registration**
	The semantic of the above-listed SubTypes is described in Section 4.		The semantic of the above-listed SubType is described in Section 4.1.
	Following the policies outline in [RFC3575] the available SubTypes		Following the policies outline in [RFC3575] the available SubTypes
	(i.e., value 0 and values 26-255) with a description of their		(i.e., value 0 and values 2-255) with a description of their semantic
	semantic will be assigned after Expert Review initiated by the O&M		will be assigned after the expert review process. Updates can be
	Area Directors in consultation with the RADEXT working group chairs		provided based on expert approval only. Based on expert approval it
	or the working group chairs of a designated successor working group.		is possible to mark entries as "deprecated". A designated expert
	Updates can be provided based on expert approval only. A designated		will be appointed by the IESG.
	expert will be appointed by the O&M Area Directors. No mechanism to
	mark entries as "deprecated", or to delete entries from the registry
	is envisioned.
	Each registration must include a number for the SubType and the		Each registration must include a number for the SubType and the
	semantic of the SubType.		semantic of the SubType.
	8.3. New Registry: Update-Reason		8.3. New Registry: PPAQ SubTypes
			Section 4.3 defines the SubTypes used within the PPAQ attribute.
			IANA is asked to create a registry for these SubTypes. Each registry
			entry consists of a 8 bit number together with a description of the
			PPAQ SubType. This document creates the following PPAQ SubTypes for
			this registry:
			Value | SubType Name
			---------+-----------------------------
			0 | Reserved
			1 | Quota Identifier
			2 | VolumeQuota
			3 | VolumeThreshold
			4 | DurationQuota
			5 | DurationThreshold
			6 | ResourceQuota
			7 | ResourceThreshold
			8 | Update-Reason
			9 | PrepaidServer
			10 | Service-ID
			11 | Rating-Group-ID
			12 | Termination-Action
			13 | Pool-ID
			14 | Pool-Multiplier
			15 | Requested-Action
			16 | Check-Balance-Result
			17 | Cost-Information
			18 | Value-Digits
			19 | Exponent
			20 | CurrencyCode
			21 | Cost-Unit
			22..255 | **Available for IANA registration**
			The semantic of the above-listed SubTypes is described in
			Section 4.3.
			Following the policies outline in [RFC3575] the available SubTypes
			(i.e., value 0 and values 22-255) with a description of their
			semantic will be assigned after the expert review process. Updates
			can be provided based on expert approval only. Based on expert
			approval it is possible to mark entries as "deprecated". A
			designated expert will be appointed by the IESG.
			Each registration must include a number for the SubType and the
			semantic of the SubType.
			8.4. New Registry: PTS SubTypes
			Section 4.4 defines the SubTypes used within the PTS attribute. IANA
			is asked to create a registry for these SubTypes. Each registry
			entry consists of a 8 bit number together with a description of the
			PTS SubType. This document creates the following PTS SubTypes for
			this registry:
			Value | SubType Name
			---------+-----------------------------
			0 | Reserved
			1 | Quota Identifier
			2 | VolumeUsedAfterTariffSwitch
			3 | TariffSwitchInterval
			4 | TimeIntervalafterTariffSwitchUpdate
			5..255 | **Available for IANA registration**
			The semantic of the above-listed SubTypes is described in
			Section 4.4.
			Following the policies outline in [RFC3575] the available SubTypes
			(i.e., value 0 and values 5-255) with a description of their semantic
			will be assigned after the expert review process. Updates can be
			provided based on expert approval only. Based on expert approval it
			is possible to mark entries as "deprecated". A designated expert
			will be appointed by the IESG.
			Each registration must include a number for the SubType and the
			semantic of the SubType.
			8.5. New Registry: Update-Reason
	Section 4.3.10 defines the Update-Reason SubType. IANA is asked to		Section 4.3.10 defines the Update-Reason SubType. IANA is asked to
	create a registry for the values contained in the Update-Reason		create a registry for the values contained in the Update-Reason
	SubType, as shown in Figure 11. Each registry entry consists of a 16		SubType, as shown in Figure 11. Each registry entry consists of a 16
	bit number together with a description of the update reason.		bit number together with a description of the update reason.
	Following the policies outline in [RFC3575] the available values		Following the policies outline in [RFC3575] the available values
	together with a description of their semantic will be assigned after		together with a description of their semantic will be assigned after
	Expert Review initiated by the O&M Area Directors in consultation		the expert review process. Updates can be provided based on expert
	with the RADEXT working group chairs or the working group chairs of a		approval only. Based on expert approval it is possible to mark
	designated successor working group. Updates can be provided based on		entries as "deprecated". A designated expert will be appointed by
	expert approval only. A designated expert will be appointed by the		the IESG.
	O&M Area Directors. No mechanism to mark entries as "deprecated", or
	to delete entries from the registry is envisioned.
	8.4. New Registry: Termination-Action		8.6. New Registry: Termination-Action
	Section 4.3.14 defines the Termination-Action SubType. IANA is asked		Section 4.3.14 defines the Termination-Action SubType. IANA is asked
	to create a registry for the values contained in the Termination-		to create a registry for the values contained in the Termination-
	Action SubType, as shown in Figure 12. Each registry entry consists		Action SubType, as shown in Figure 12. Each registry entry consists
	of a 8 bit number together with a description of the termination		of a 8 bit number together with a description of the termination
	action.		action.
	Following the policies outline in [RFC3575] the available values		Following the policies outline in [RFC3575] the available values
	together with a description of their semantic will be assigned after		together with a description of their semantic will be assigned after
	Expert Review initiated by the O&M Area Directors in consultation		the expert review process. Updates can be provided based on expert
	with the RADEXT working group chairs or the working group chairs of a		approval only. Based on expert approval it is possible to mark
	designated successor working group. Updates can be provided based on		entries as "deprecated". A designated expert will be appointed by
	expert approval only. A designated expert will be appointed by the		the IESG.
	O&M Area Directors. No mechanism to mark entries as "deprecated", or
	to delete entries from the registry is envisioned.
	8.5. New Registry: Requested-Action		8.7. New Registry: Requested-Action
	Section 4.3.17 defines the Requested-Action SubType. IANA is asked		Section 4.3.17 defines the Requested-Action SubType. IANA is asked
	to create a registry for the values contained in the Requested-Action		to create a registry for the values contained in the Requested-Action
	SubType, as shown in Figure 13. Each registry entry consists of a 8		SubType, as shown in Figure 13. Each registry entry consists of a 8
	bit number together with a description of the requested reason.		bit number together with a description of the requested reason.
	Following the policies outline in [RFC3575] the available values		Following the policies outline in [RFC3575] the available values
	together with a description of their semantic will be assigned after		together with a description of their semantic will be assigned after
	Expert Review initiated by the O&M Area Directors in consultation		the expert review process. Updates can be provided based on expert
	with the RADEXT working group chairs or the working group chairs of a		approval only. Based on expert approval it is possible to mark
	designated successor working group. Updates can be provided based on		entries as "deprecated". A designated expert will be appointed by
	expert approval only. A designated expert will be appointed by the		the IESG.
	O&M Area Directors. No mechanism to mark entries as "deprecated", or
	to delete entries from the registry is envisioned.
	8.6. New Registry: Check-Balance-Result		8.8. New Registry: Check-Balance-Result
	Section 4.3.18 defines the Check-Balance-Result SubType. IANA is		Section 4.3.18 defines the Check-Balance-Result SubType. IANA is
	asked to create a registry for the values contained in the Check-		asked to create a registry for the values contained in the Check-
	Balance-Result SubType, as shown in Figure 14. Each registry entry		Balance-Result SubType, as shown in Figure 14. Each registry entry
	consists of a 8 bit number together with a description of the		consists of a 8 bit number together with a description of the
	requested reason.		requested reason.
	Following the policies outline in [RFC3575] the available values		Following the policies outline in [RFC3575] the available values
	together with a description of their semantic will be assigned after		together with a description of their semantic will be assigned after
	Expert Review initiated by the O&M Area Directors in consultation		the expert review process. Updates can be provided based on expert
	with the RADEXT working group chairs or the working group chairs of a		approval only. Based on expert approval it is possible to mark
	designated successor working group. Updates can be provided based on		entries as "deprecated". A designated expert will be appointed by
	expert approval only. A designated expert will be appointed by the		the IESG.
	O&M Area Directors. No mechanism to mark entries as "deprecated", or
	to delete entries from the registry is envisioned.
	9. Acknowledgements		9. Acknowledgements
	The authors would like to thank Christian Guenther, Bernard Aboba,		The authors would like to thank Christian Guenther, Bernard Aboba,
	and John Loughney for their feedback throughout the development of		and John Loughney for their feedback throughout the development of
	this document. Additionally, the authors would like to thank the		this document. Additionally, the authors would like to thank the
	members of the Wimax Forum and the members of 3GPP2 for their help		members of the Wimax Forum and the members of 3GPP2 for their help
	with this specification.		with this specification.
	10. References		10. References
End of changes. 42 change blocks.
	93 lines changed or deleted		135 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/