Diameter Congestion and Filter Attributes

The information below is for an old version of the document
Document Type Expired Internet-Draft (dime WG)
Authors Brent Hirschman  , Lyle Bertz 
Last updated 2014-10-20 (latest revision 2014-04-18)
Replaces draft-bertz-dime-congestion-flow-attributes
Stream Internet Engineering Task Force (IETF)
Expired & archived
pdf htmlized bibtex
Additional Resources
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Brent Hirschman (brent.hirschman@sprint.com)
Lyle Bertz (lyle.t.bertz@sprint.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)