RFC 8582: Diameter Overload Rate Control
In plain English — editorial summary, not part of the RFC
This specification documents an extension to the Diameter Overload Indication Conveyance (DOIC) base solution, which is defined in RFC 7683. This extension adds a new overload-control abatement algorithm. This abatement algorithm allows for a DOIC reporting node to specify a maximum rate at which a DOIC reacting node sends Diameter requests to the DOIC reporting node.
Document record
- Document ID
- RFC8582
- Published
- August 2019
- Authors
- S. Donovan; E. Noel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8581Diameter Agent Overload and the Peer Overload ReportCurrent
August 2019
- RFC 7944Diameter Routing Message PriorityCurrent
August 2016
- RFC 8583Diameter Load Information ConveyanceCurrent
August 2019
- RFC 8506Diameter Credit-Control ApplicationCurrent
March 2019
- RFC 7966Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and RequirementsCurrent
September 2016
- RFC 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 7075Realm-Based Redirection In DiameterCurrent
November 2013
- RFC 6733Diameter Base ProtocolUpdated
October 2012
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?