RFC 7660: Diameter Congestion and Filter Attributes
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7660
- Published
- October 2015
- Authors
- L. Bertz; S. Manning; B. Hirschman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7666Management Information Base for Virtual Machines Controlled by a HypervisorCurrent
October 2015
- RFC 7654Benchmarking Methodology for In-Service Software Upgrade (ISSU)Current
October 2015
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 7679A One-Way Delay Metric for IP Performance Metrics (IPPM)Current
January 2016
- RFC 7680A One-Way Loss Metric for IP Performance Metrics (IPPM)Current
January 2016
- RFC 7640Traffic Management BenchmarkingCurrent
September 2015
- RFC 7682Considerations for Internet Routing Registries (IRRs) and Routing Policy ConfigurationCurrent
December 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?