Diameter Priority Attribute-Value Pairs
RFC 6735
|
| Document |
Type |
|
RFC - Proposed Standard
(October 2012; Errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-carlberg-dime-priority-avps
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Lionel Morand
|
| IESG |
IESG state |
|
RFC 6735 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Benoit Claise
|
|
IESG note |
|
Lionel Morand (lionel.morand@orange-ftgroup.com) is the document shepherd
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) K. Carlberg, Ed.
Request for Comments: 6735 G11
Category: Standards Track T. Taylor
ISSN: 2070-1721 PT Taylor Consulting
October 2012
Diameter Priority Attribute-Value Pairs
Abstract
This document defines Attribute-Value Pair (AVP) containers for
various priority parameters for use with Diameter and the
Authentication, Authorization, and Accounting (AAA) framework. The
parameters themselves are defined in several different protocols that
operate at either the network or application layer.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6735.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Carlberg & Taylor Standards Track [Page 1]
RFC 6735 Resource Priorities AVPs October 2012
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
1. Introduction
This document defines a number of Attribute-Value Pairs (AVP) that
can be used within the Diameter protocol [RFC6733] to convey a
specific set of priority parameters. These parameters are specified
in other documents, but are briefly described below. The
corresponding AVPs defined in Section 3 are extensions to those
defined in [RFC5866]. We note that all the priority fields
associated with the AVPs defined in this document are extensible and
allow for additional values beyond what may have already been defined
or registered with IANA.
Priority influences the distribution of resources and, in turn, the
QoS associated with that resource. This influence may be
probabilistic, ranging between (but not including) 0% and 100%, or it
may be in the form of a guarantee to either receive or not receive
the resource.
Another example of how prioritization can be realized is articulated
in Appendix A.3 (the Priority Bypass Model) of [RFC6401]. In this
case, prioritized flows may gain access to resources that are never
shared with non-prioritized flows.
1.1. Other Priority-Related AVPs
The 3rd Generation Partnership Project (3GPP) has defined several
Diameter AVPs that support prioritization of sessions. The following
AVPs are intended to be used for priority services (e.g., Multimedia
Priority Service):
- Reservation-Priority AVP as defined in [ETSI]
- MPS-Identifier AVP as defined in [3GPPa]
- Priority-Level AVP (as part of the Allocation Retention
Priority AVP) as defined in [3GPPb]
- Session-Priority AVP as defined in [3GPPc] and [3GPPd]
Carlberg & Taylor Standards Track [Page 2]
RFC 6735 Resource Priorities AVPs October 2012
Both the Reservation-Priority AVP and the Priority-Level AVP can
Show full document text