RFC 5624: Quality of Service Parameters for Usage with Diameter
In plain English — editorial summary, not part of the RFC
This document defines a number of Quality of Service (QoS) parameters that can be reused for conveying QoS information within Diameter. The defined QoS information includes data traffic parameters for describing a token bucket filter, a bandwidth parameter, and a per-hop behavior class object. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5624
- Published
- August 2009
- Authors
- J. Korhonen; H. Tschofenig; E. Davies
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5777Traffic Classification and Quality of Service (QoS) Attributes for DiameterCurrent
February 2010
- RFC 5447Diameter Mobile IPv6: Support for Network Access Server to Diameter Server InteractionCurrent
February 2009
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 6733Diameter Base ProtocolUpdated
October 2012
- RFC 7075Realm-Based Redirection In DiameterCurrent
November 2013
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 7966Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and RequirementsCurrent
September 2016
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?