< draft-ietf-dime-qos-parameters-10.txt		draft-ietf-dime-qos-parameters-11.txt >
	Diameter Maintenance and J. Korhonen, Ed.		Diameter Maintenance and J. Korhonen, Ed.
	Extensions (DIME) H. Tschofenig		Extensions (DIME) H. Tschofenig
	Internet-Draft Nokia Siemens Networks		Internet-Draft Nokia Siemens Networks
	Intended status: Standards Track E. Davies		Intended status: Standards Track E. Davies
	Expires: September 10, 2009 Folly Consulting		Expires: November 26, 2009 Folly Consulting
	March 9, 2009		May 25, 2009
	Quality of Service Parameters for Usage with Diameter		Quality of Service Parameters for Usage with Diameter
	draft-ietf-dime-qos-parameters-10.txt		draft-ietf-dime-qos-parameters-11.txt
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and 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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 September 10, 2009.		This Internet-Draft will expire on November 26, 2009.
	Copyright Notice		Copyright Notice
	Copyright (c) 2009 IETF Trust and the persons identified as the		Copyright (c) 2009 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 in effect on the date of		Provisions Relating to IETF Documents in effect on the date of
	publication of this document (http://trustee.ietf.org/license-info).		publication of this document (http://trustee.ietf.org/license-info).
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 19 ¶		skipping to change at page 2, line 19 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4		2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4
	3. QoS Parameter Encoding . . . . . . . . . . . . . . . . . . . . 4		3. QoS Parameter Encoding . . . . . . . . . . . . . . . . . . . . 4
	3.1. TMOD-1 AVP . . . . . . . . . . . . . . . . . . . . . . . . 4		3.1. TMOD-1 AVP . . . . . . . . . . . . . . . . . . . . . . . . 4
	3.1.1. Token-Rate AVP . . . . . . . . . . . . . . . . . . . . 4		3.1.1. Token-Rate AVP . . . . . . . . . . . . . . . . . . . . 4
	3.1.2. Bucket-Depth AVP . . . . . . . . . . . . . . . . . . . 4		3.1.2. Bucket-Depth AVP . . . . . . . . . . . . . . . . . . . 4
	3.1.3. Peak-Traffic-Rate AVP . . . . . . . . . . . . . . . . 4		3.1.3. Peak-Traffic-Rate AVP . . . . . . . . . . . . . . . . 4
	3.1.4. Minimum-Policed-Unit AVP . . . . . . . . . . . . . . . 4		3.1.4. Minimum-Policed-Unit AVP . . . . . . . . . . . . . . . 5
	3.1.5. Maximum-Packet-Size AVP . . . . . . . . . . . . . . . 5		3.1.5. Maximum-Packet-Size AVP . . . . . . . . . . . . . . . 5
	3.2. TMOD-2 AVP . . . . . . . . . . . . . . . . . . . . . . . . 5		3.2. TMOD-2 AVP . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.3. Bandwidth AVP . . . . . . . . . . . . . . . . . . . . . . 5		3.3. Bandwidth AVP . . . . . . . . . . . . . . . . . . . . . . 5
	3.4. PHB-Class AVP . . . . . . . . . . . . . . . . . . . . . . 5		3.4. PHB-Class AVP . . . . . . . . . . . . . . . . . . . . . . 5
	3.4.1. Case 1: Single PHB . . . . . . . . . . . . . . . . . . 5		3.4.1. Case 1: Single PHB . . . . . . . . . . . . . . . . . . 5
	3.4.2. Case 2: Set of PHBs . . . . . . . . . . . . . . . . . 6		3.4.2. Case 2: Set of PHBs . . . . . . . . . . . . . . . . . 6
	3.4.3. Case 3: Experimental or Local Use PHBs . . . . . . . . 6		3.4.3. Case 3: Experimental or Local Use PHBs . . . . . . . . 6
	4. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 6		4. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 8		6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8		7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 9		8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
	8.2. Informative References . . . . . . . . . . . . . . . . . . 9		8.2. Informative References . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
	1. Introduction		1. Introduction
	This document defines a number of Quality of Service (QoS) parameters		This document defines a number of Quality of Service (QoS) parameters
	that can be reused for conveying QoS information within the Diameter		that can be reused for conveying QoS information within the Diameter
	protocol [RFC3588]. It defines an initial QoS profile containing a		protocol [RFC3588]. The current set of QoS parameters defined in
	set of Diameter encoded Attribute Value Pairs (AVPs) described using		this document are a core subset determined to be useful for a wide
	a modified version of the Augmented Backus-Naur Form (ABNF), see		range of applications. Additional parameters may be defined in
	[RFC3588]. The datatypes are also taken from [RFC3588].		future documents as the need arises and are for future study. The
			parameters are defined as Diameter encoded Attribute Value Pairs
			(AVPs) described using a modified version of the Augmented Backus-
			Naur Form (ABNF), see [RFC3588]. The datatypes are also taken from
			[RFC3588].
	The traffic model (TMOD) AVPs are containers consisting of four AVPs		The traffic model (TMOD) AVPs are containers consisting of four AVPs
	and is a way to describe the traffic source.		and is a way to describe the traffic source.
	o token rate (r)		o token rate (r)
	o bucket depth (b)		o bucket depth (b)
	o peak traffic rate (p)		o peak traffic rate (p)
	o minimum policed unit (m)		o minimum policed unit (m)
	o maximum packet size (M)		o maximum packet size (M)
	skipping to change at page 5, line 24 ¶		skipping to change at page 5, line 28 ¶
	TMOD-2 ::= < AVP Header: TBD >		TMOD-2 ::= < AVP Header: TBD >
	{ Token-Rate }		{ Token-Rate }
	{ Bucket-Depth }		{ Bucket-Depth }
	{ Peak-Traffic-Rate }		{ Peak-Traffic-Rate }
	{ Minimum-Policed-Unit }		{ Minimum-Policed-Unit }
	{ Maximum-Packet-Size }		{ Maximum-Packet-Size }
	3.3. Bandwidth AVP		3.3. Bandwidth AVP
	The Bandwidth AVP (AVP Code TBD) is of type Float32 and is measured		The Bandwidth AVP (AVP Code TBD) is of type Float32 and is measured
	in octets of IP datagrams per second.		in octets of IP datagrams per second. The Bandwidth AVP represents a
			simplified description of the following TMOD setting whereby the
			token rate (r) = peak traffic rate (p), the bucket depth (b) = large,
			minimum policed unit (m) = large when only bandwidth has to be
			expressed.
	3.4. PHB-Class AVP		3.4. PHB-Class AVP
	The PHB-Class AVP (AVP Code TBD) is of type Unsigned32.		The PHB-Class AVP (AVP Code TBD) is of type Unsigned32.
	A description of the semantic of the parameter values can be found in		A description of the semantic of the parameter values can be found in
	[RFC3140]. The registries needed for usage with [RFC3140] already		[RFC3140]. The registries needed for usage with [RFC3140] already
	exist and hence no new registry needs to be created by this document.		exist and hence no new registry needs to be created by this document.
	The encoding requires three cases need to be differentiated. All		The encoding requires three cases need to be differentiated. All
	bits indicated as "reserved" MUST be set to zero (0).		bits indicated as "reserved" MUST be set to zero (0).
	skipping to change at page 9, line 12 ¶		skipping to change at page 9, line 26 ¶
	We would like to thank Ken Carlberg, Lars Eggert, Jan Engelhardt,		We would like to thank Ken Carlberg, Lars Eggert, Jan Engelhardt,
	Francois Le Faucheur, John Loughney, An Nguyen, Dave Oran, James		Francois Le Faucheur, John Loughney, An Nguyen, Dave Oran, James
	Polk, Martin Dolly, Martin Stiemerling, and Magnus Westerlund for		Polk, Martin Dolly, Martin Stiemerling, and Magnus Westerlund for
	their feedback regarding some of the parameters in this documents.		their feedback regarding some of the parameters in this documents.
	Jerry Ash, Al Morton, Mayutan Arumaithurai and Xiaoming Fu provided		Jerry Ash, Al Morton, Mayutan Arumaithurai and Xiaoming Fu provided
	help with the semantic of some QSPEC parameters.		help with the semantic of some QSPEC parameters.
	We would like to thank Dan Romascanu for his detailed Area Director		We would like to thank Dan Romascanu for his detailed Area Director
	review comments and Scott Bradner for his Transport Area Directorate		review comments and Scott Bradner for his Transport Area Directorate
	review. Chris Newman and Pasi Eronen provided feedback during the		review. Chris Newman, Adrian Farrel and Pasi Eronen provided
	IESG review.		feedback during the IESG review.
	8. References		8. References
	8.1. Normative References		8.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.
	[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated		[RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated
	Services", RFC 2210, September 1997.		Services", RFC 2210, September 1997.
End of changes. 10 change blocks.
	15 lines changed or deleted		23 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/