RFC 8581: Diameter Agent Overload and the Peer Overload Report
In plain English — editorial summary, not part of the RFC
This specification documents an extension to the Diameter Overload Indication Conveyance (DOIC), a base solution for Diameter overload defined in RFC 7683. The extension defines the Peer Overload report type. The initial use case for the peer report is the handling of occurrences of overload of a Diameter Agent.
Document record
- Document ID
- RFC8581
- Published
- August 2019
- Authors
- S. Donovan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
- Updates:
- RFC 7683
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8582Diameter Overload Rate ControlCurrent
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?