Quality of Service Parameters for Usage with Diameter
RFC 5624

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 11

Network Working Group                                   J. Korhonen, Ed.
Request for Comments: 5624                                 H. Tschofenig
Category: Standards Track                         Nokia Siemens Networks
                                                               E. Davies
                                                        Folly Consulting
                                                             August 2009

         Quality of Service Parameters for Usage with Diameter

Abstract

   This document defines a number of Quality of Service (QoS) parameters
   that can be reused for conveying QoS information within Diameter.

   The defined QoS information includes data traffic parameters for
   describing a token bucket filter, a bandwidth parameter, and a per-
   hop behavior class object.

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (c) 2009 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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Korhonen, et al.            Standards Track                     [Page 1]
RFC 5624                     QoS Parameters                  August 2009

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology and Abbreviations  . . . . . . . . . . . . . . . .  3
   3.  QoS Parameter Encoding . . . . . . . . . . . . . . . . . . . .  4
     3.1.  TMOD-1 AVP . . . . . . . . . . . . . . . . . . . . . . . .  4
       3.1.1.  Token-Rate AVP . . . . . . . . . . . . . . . . . . . .  4
       3.1.2.  Bucket-Depth AVP . . . . . . . . . . . . . . . . . . .  4
       3.1.3.  Peak-Traffic-Rate AVP  . . . . . . . . . . . . . . . .  4
       3.1.4.  Minimum-Policed-Unit AVP . . . . . . . . . . . . . . .  4
       3.1.5.  Maximum-Packet-Size AVP  . . . . . . . . . . . . . . .  4
     3.2.  TMOD-2 AVP . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.3.  Bandwidth AVP  . . . . . . . . . . . . . . . . . . . . . .  5
     3.4.  PHB-Class AVP  . . . . . . . . . . . . . . . . . . . . . .  5
       3.4.1.  Case 1: Single PHB . . . . . . . . . . . . . . . . . .  5
       3.4.2.  Case 2: Set of PHBs  . . . . . . . . . . . . . . . . .  5
       3.4.3.  Case 3: Experimental or Local Use PHBs . . . . . . . .  6
   4.  Extensibility  . . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     8.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     8.2.  Informative References . . . . . . . . . . . . . . . . . .  9
   Appendix A.  ABNF Code Fragment  . . . . . . . . . . . . . . . . . 11

1.  Introduction

   This document defines a number of Quality of Service (QoS) parameters
   that can be reused for conveying QoS information within the Diameter
   protocol [RFC3588].  The current set of QoS parameters defined in
   this document are a core subset determined to be useful for a wide
   range of applications.  Additional parameters may be defined in
   future documents as the need arises and are for future study.  The
   parameters are defined as Diameter-encoded Attribute Value Pairs
   (AVPs), which are described using a modified version of the Augmented
   Backus-Naur Form (ABNF), see [RFC3588].  The data types are also
   taken from [RFC3588].

   The traffic model (TMOD) AVPs are containers consisting of four AVPs
   and provide a way to describe the traffic source.

   o  token rate (r)

   o  bucket depth (b)

   o  peak traffic rate (p)

Korhonen, et al.            Standards Track                     [Page 2]
RFC 5624                     QoS Parameters                  August 2009

   o  minimum policed unit (m)

   o  maximum packet size (M)

   The encoding of the <TMOD-1> and the <TMOD-2> AVPs can be found in
   Sections 3.1 and 3.2.  The semantics of these two AVPs are described
   in Section 3.1 of [RFC2210] and in Section 3.6 of [RFC2215].

   The <TMOD-2> AVP is, for example, needed by some DiffServ
   applications.

      It is typically assumed that DiffServ expedited forwarding (EF)
      traffic is shaped at the ingress by a single-rate token bucket.