Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Diameter Congestion and Filter Attributes (RFC7660)

IP.com Disclosure Number: IPCOM000245002D
Original Publication Date: 2015-Oct-01
Included in the Prior Art Database: 2016-Feb-05
Document File: 18 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Bertz: AUTHOR [+3]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 14% of the total text.

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.  Ple...