Diameter Congestion and Filter Attributes
RFC 7660

Document Type RFC - Proposed Standard (October 2015; No errata)
Last updated 2015-10-14
Replaces draft-bertz-dime-congestion-flow-attributes
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication Nov 2014
Document shepherd Lionel Morand
Shepherd write-up Show (last changed 2015-06-04)
IESG IESG state RFC 7660 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          L. Bertz
Request for Comments: 7660                                    S. Manning
Category: Standards Track                                         Sprint
ISSN: 2070-1721                                             B. Hirschman
                                                            October 2015

               Diameter Congestion and Filter Attributes

Abstract

   This document defines optional Diameter attributes that can be used
   to help manage networks that use Explicit Congestion Notification
   (ECN) or Diameter traffic filters.  These new attributes allow for
   improved data traffic identification, support of ECN, and minimal
   Diameter filter administration.

   RFC 5777 defines a Filter-Rule Attribute Value Pair (AVP) that
   accommodates extensions for classification, conditions, and actions.
   It, however, does not support traffic identification for packets
   using Explicit Congestion Notification as defined in RFC 3168 and
   does not provide specific actions when the flow(s) described by the
   Filter-Rule are congested.

   Further, a Filter-Rule can describe multiple flows but not the exact
   number of flows.  Flow count and other associated data (e.g.,
   packets) are not captured by accounting applications, leaving
   administrators without useful information regarding the effectiveness
   or appropriateness of the filter definition.

   The optional attributes defined in this document are forward and
   backwards compatible with RFC 5777.

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/rfc7660.

Bertz                        Standards Track                    [Page 1]
RFC 7660            Congestion and Filter Attributes        October 2015

Copyright Notice

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

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  ECN-IP-Codepoint, Congestion-Treatment and Filter Attributes .  4
     3.1.  ECN-IP-Codepoint AVP . . . . . . . . . . . . . . . . . . .  4
     3.2.  Congestion-Treatment AVP . . . . . . . . . . . . . . . . .  4
     3.3.  Flow-Count AVP . . . . . . . . . . . . . . . . . . . . . .  5
     3.4.  Packet-Count AVP . . . . . . . . . . . . . . . . . . . . .  5
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
     4.1.  AVP Codes  . . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     5.1. Classifier Example  . . . . . . . . . . . . . . . . . . . .  6
     5.2. Diameter Credit Control (CC) with Congestion Information  .  6
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  8
   Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

Bertz                        Standards Track                    [Page 2]
RFC 7660            Congestion and Filter Attributes        October 2015

1.  Introduction

   Two optional AVPs related to Explicit Congestion Notification (ECN)
   [RFC3168] are specified in this document.  The first AVP provides
   direct support for filtering ECN-marked traffic [RFC3168] and the
   second AVP provides the ability to define alternate traffic treatment
   when congestion is experienced.

   This document also defines two optional AVPs, Flow-Count and Packet-
   Count, used for conveying flow information within the Diameter
Show full document text