Last Call: <draft-ietf-dime-congestion-flow-attributes-01.txt> (Diameter Congestion and Filter Attributes) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 18 May 2015 15:10 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-dime-congestion-flow-attributes-01.txt> (Diameter Congestion and Filter Attributes) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150518151047.17954.81737.idtracker@ietfa.amsl.com>
Date: Mon, 18 May 2015 08:10:47 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/M-Hyhitm1ipBz2TBmlQdS-5ab0I>
Cc: dime@ietf.org
Reply-To: ietf@ietf.org

The IESG has received a request from the Diameter Maintenance and
Extensions WG (dime) to consider the following document:
- 'Diameter Congestion and Filter Attributes'
  <draft-ietf-dime-congestion-flow-attributes-01.txt> as Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-06-01. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document defines optional ECN and filter related attributes that
   can be used for improved traffic identification, support of ECN and
   minimized filter administration within Diameter.

   RFC 5777 defines a Filter-Rule AVP that accommodates extensions for
   classification, conditions and actions. It 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.

   A Filter-Rule can describe multiple flows but not the exact number of
   flows. Flow count and other associated data (e.g. packets) is not
   captured in Accounting applications, leaving administrators without
   useful information regarding the effectiveness or understanding of
   the filter definition.

   These optional attributes are forward and backwards compatible with
   RFC 5777.



The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dime-congestion-flow-attributes/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dime-congestion-flow-attributes/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-dime-congestion-flow-attri… The IESG