Diameter Load Information Conveyance
RFC 8583
Document | Type |
RFC - Proposed Standard
(August 2019; No errata)
Was draft-ietf-dime-load (dime WG)
|
|
---|---|---|---|
Authors | Ben Campbell , Steve Donovan , Jean-Jacques Trottin | ||
Last updated | 2019-08-15 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized 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 8583 (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) B. Campbell Request for Comments: 8583 S. Donovan, Ed. Category: Standards Track Oracle ISSN: 2070-1721 JJ. Trottin Nokia August 2019 Diameter Load Information Conveyance Abstract RFC 7068 describes requirements for Overload Control in Diameter. This includes a requirement to allow Diameter nodes to send "load" information, even when the node is not overloaded. The base solution defined in RFC 7683 (Diameter Overload Information Conveyance (DOIC)) describes a mechanism meeting most of the requirements but does not currently include the ability to send load information. This document defines a mechanism for the conveying of Diameter load information. 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/rfc8583. Campbell, et al. Standards Track [Page 1] RFC 8583 Diameter Load August 2019 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. Campbell, et al. Standards Track [Page 2] RFC 8583 Diameter Load August 2019 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 4 3. Conventions Used in This Document . . . . . . . . . . . . . . 5 4. Background . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Differences between Load and Overload Information . . . . 5 4.2. How Is Load Information Used? . . . . . . . . . . . . . . 6 5. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Theory of Operation . . . . . . . . . . . . . . . . . . . 9 6. Load-Mechanism Procedures . . . . . . . . . . . . . . . . . . 11 6.1. Reporting-Node Behavior . . . . . . . . . . . . . . . . . 11 6.1.1. Endpoint Reporting-Node Behavior . . . . . . . . . . 11 6.1.2. Agent Reporting-Node Behavior . . . . . . . . . . . . 12 6.2. Reacting-Node Behavior . . . . . . . . . . . . . . . . . 13 6.3. Extensibility . . . . . . . . . . . . . . . . . . . . . . 14 6.4. Addition and Removal of Nodes . . . . . . . . . . . . . . 14 7. Attribute-Value Pairs . . . . . . . . . . . . . . . . . . . . 15 7.1. Load AVP . . . . . . . . . . . . . . . . . . . . . . . . 15 7.2. Load-Type AVP . . . . . . . . . . . . . . . . . . . . . . 15 7.3. Load-Value AVP . . . . . . . . . . . . . . . . . . . . . 15 7.4. SourceID AVP . . . . . . . . . . . . . . . . . . . . . . 15 7.5. Attribute-Value Pair Flag Rules . . . . . . . . . . . . . 16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . 17 10.2. Informative References . . . . . . . . . . . . . . . . . 17 Appendix A. Topology Scenarios . . . . . . . . . . . . . . . . . 18 A.1. No Agent . . . . . . . . . . . . . . . . . . . . . . . . 18 A.2. Single Agent . . . . . . . . . . . . . . . . . . . . . . 18 A.3. Multiple Agents . . . . . . . . . . . . . . . . . . . . . 19 A.4. Linked Agents . . . . . . . . . . . . . . . . . . . . . . 19 A.5. Shared Server Pools . . . . . . . . . . . . . . . . . . . 21Show full document text