Diameter Agent Overload and the Peer Overload Report
RFC 8581
| Document | Type |
RFC - Proposed Standard
(August 2019; No errata)
Updates RFC 7683
|
|
|---|---|---|---|
| Last updated | 2019-08-15 | ||
| Replaces | draft-donovan-dime-agent-overload | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Jouni Korhonen | ||
| Shepherd write-up | Show (last changed 2016-12-06) | ||
| IESG | IESG state | RFC 8581 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ignas Bagdonas | ||
| Send notices to | "Jouni Korhonen" <jouni.nospam@gmail.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) S. Donovan
Request for Comments: 8581 Oracle
Updates: 7683 August 2019
Category: Standards Track
ISSN: 2070-1721
Diameter Agent Overload and the Peer Overload Report
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8581.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Donovan Standards Track [Page 1]
RFC 8581 Diameter Agent Overload and Peer Report August 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4
4. Peer-Report Use Cases . . . . . . . . . . . . . . . . . . . . 5
4.1. Diameter Agent Overload Use Cases . . . . . . . . . . . . 5
4.1.1. Single Agent . . . . . . . . . . . . . . . . . . . . 5
4.1.2. Redundant Agents . . . . . . . . . . . . . . . . . . 6
4.1.3. Agent Chains . . . . . . . . . . . . . . . . . . . . 7
4.2. Diameter Endpoint Use Cases . . . . . . . . . . . . . . . 8
4.2.1. Hop-by-Hop Abatement Algorithms . . . . . . . . . . . 8
5. Interaction Between Host/Realm and Peer Overload Reports . . 9
6. Peer-Report Behavior . . . . . . . . . . . . . . . . . . . . 9
6.1. Capability Announcement . . . . . . . . . . . . . . . . . 9
6.1.1. Reacting-Node Behavior . . . . . . . . . . . . . . . 9
6.1.2. Reporting-Node Behavior . . . . . . . . . . . . . . . 9
6.2. Peer Overload Report Handling . . . . . . . . . . . . . . 10
6.2.1. Overload Control State . . . . . . . . . . . . . . . 10
6.2.2. Reporting-Node Maintenance of Peer-Report OCS . . . . 11
6.2.3. Reacting-Node Maintenance of Peer-Report OCS . . . . 12
6.2.4. Peer-Report Reporting-Node Behavior . . . . . . . . . 13
6.2.5. Peer-Report Reacting-Node Behavior . . . . . . . . . 13
7. Peer-Report AVPs . . . . . . . . . . . . . . . . . . . . . . 14
7.1. OC-Supported-Features AVP . . . . . . . . . . . . . . . . 14
7.1.1. OC-Feature-Vector AVP . . . . . . . . . . . . . . . . 15
7.1.2. OC-Peer-Algo AVP . . . . . . . . . . . . . . . . . . 15
7.2. OC-OLR AVP . . . . . . . . . . . . . . . . . . . . . . . 15
7.2.1. OC-Report-Type AVP . . . . . . . . . . . . . . . . . 16
7.3. SourceID AVP . . . . . . . . . . . . . . . . . . . . . . 16
7.4. Attribute-Value Pair Flag Rules . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . 18
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
Donovan Standards Track [Page 2]
RFC 8581 Diameter Agent Overload and Peer Report August 2019
1. Introduction
This specification documents an extension to the Diameter Overload
Show full document text