Diameter Priority Attribute Value Pairs
draft-ietf-dime-priority-avps-05

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Author Ken Carlberg 
Last updated 2012-03-29 (latest revision 2011-10-31)
Replaces draft-carlberg-dime-priority-avps
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Lionel Morand
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Unknown
Telechat date
Needs a YES. Needs 10 more YES or NO OBJECTION positions to pass.
Responsible AD BenoƮt Claise
IESG note Lionel Morand (lionel.morand@orange-ftgroup.com) is the document shepherd
Send notices to dime-chairs@tools.ietf.org, draft-ietf-dime-priority-avps@tools.ietf.org
Diameter Maintenance and                                K. Carlberg, Ed.
Extensions (DIME)                                                    G11
Internet-Draft                                                 T. Taylor
Intended status: Standards Track                     Huawei Technologies
                                                            Oct 31, 2011

                Diameter Priority Attribute Value Pairs
                  draft-ietf-dime-priority-avps-05.txt

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering Task
   Force (IETF).  Note that other groups may also distribute working
   documents as Internet-Drafts.  The list of current Internet-Drafts is at
   http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference material
   or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2011 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.

   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.

Carlberg & Taylor                 Expires April 26, 2012        [Page 1]
Internet Drafts          Resource Priority AVPs             Oct 31, 2012

Abstract

   This document defines Attribute-Value Pair (AVP) containers for various
   priority parameters for use with Diameter and the AAA framework.  The
   parameters themselves are defined in several different protocols that
   operate at either the network or application layer.

1.  Introduction

   This document defines a number of Attribute-Value Pairs (AVP) that can
   be used within the Diameter protocol [I-D.ietf-dime-rfc3588bis] 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 an extension 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.  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.

   The influence attributed to prioritization may also affect QoS, but it
   is not to be confused with QoS.  As an example, if packets of two or more
   flows are contending for the same shared resources, prioritization helps
   determine which packet receives the resource.  However, this allocation
   of resource does not correlate directly to any specific delay or loss
   bounds that have been associated with the packet.

   Another example of how prioritization can be realized is articulated in
   Appendix A.3 (the priority by-pass model) of
   [I-D.ietf-tsvwg-emergency-rsvp].  In this case, prioritized flows may
   gain access to resources that are never shared with non-prioritized
   flows.

1.1  Other Priority-Related AVPs

   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]
Show full document text