Diameter Overload Indication Conveyance
RFC 7683
| Document | Type |
RFC - Proposed Standard
(October 2015; Errata)
Was draft-ietf-dime-ovli (dime WG)
|
|
|---|---|---|---|
| Last updated | 2015-12-02 | ||
| Replaces | draft-docdt-dime-ovli | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication (wg milestone: Mar 2013 - Submit I-D 'Diameter... ) | |
| Document shepherd | Alan DeKok | ||
| Shepherd write-up | Show (last changed 2015-06-23) | ||
| IESG | IESG state | RFC 7683 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Stephen Farrell | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) J. Korhonen, Ed.
Request for Comments: 7683 Broadcom Corporation
Category: Standards Track S. Donovan, Ed.
ISSN: 2070-1721 B. Campbell
Oracle
L. Morand
Orange Labs
October 2015
Diameter Overload Indication Conveyance
Abstract
This specification defines a base solution for Diameter overload
control, referred to as Diameter Overload Indication Conveyance
(DOIC).
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 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7683.
Copyright Notice
Copyright (c) 2015 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
(http://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.
Korhonen, et al. Standards Track [Page 1]
RFC 7683 DOIC October 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Conventions Used in This Document . . . . . . . . . . . . . . 5
4. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 5
4.1. Piggybacking . . . . . . . . . . . . . . . . . . . . . . 6
4.2. DOIC Capability Announcement . . . . . . . . . . . . . . 7
4.3. DOIC Overload Condition Reporting . . . . . . . . . . . . 9
4.4. DOIC Extensibility . . . . . . . . . . . . . . . . . . . 11
4.5. Simplified Example Architecture . . . . . . . . . . . . . 12
5. Solution Procedures . . . . . . . . . . . . . . . . . . . . . 12
5.1. Capability Announcement . . . . . . . . . . . . . . . . . 12
5.1.1. Reacting Node Behavior . . . . . . . . . . . . . . . 13
5.1.2. Reporting Node Behavior . . . . . . . . . . . . . . . 13
5.1.3. Agent Behavior . . . . . . . . . . . . . . . . . . . 14
5.2. Overload Report Processing . . . . . . . . . . . . . . . 15
5.2.1. Overload Control State . . . . . . . . . . . . . . . 15
5.2.2. Reacting Node Behavior . . . . . . . . . . . . . . . 19
5.2.3. Reporting Node Behavior . . . . . . . . . . . . . . . 20
5.3. Protocol Extensibility . . . . . . . . . . . . . . . . . 22
6. Loss Algorithm . . . . . . . . . . . . . . . . . . . . . . . 23
6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 23
6.2. Reporting Node Behavior . . . . . . . . . . . . . . . . . 24
6.3. Reacting Node Behavior . . . . . . . . . . . . . . . . . 24
7. Attribute Value Pairs . . . . . . . . . . . . . . . . . . . . 25
7.1. OC-Supported-Features AVP . . . . . . . . . . . . . . . . 25
7.2. OC-Feature-Vector AVP . . . . . . . . . . . . . . . . . . 25
7.3. OC-OLR AVP . . . . . . . . . . . . . . . . . . . . . . . 26
7.4. OC-Sequence-Number AVP . . . . . . . . . . . . . . . . . 26
7.5. OC-Validity-Duration AVP . . . . . . . . . . . . . . . . 26
7.6. OC-Report-Type AVP . . . . . . . . . . . . . . . . . . . 27
7.7. OC-Reduction-Percentage AVP . . . . . . . . . . . . . . . 27
7.8. AVP Flag Rules . . . . . . . . . . . . . . . . . . . . . 28
8. Error Response Codes . . . . . . . . . . . . . . . . . . . . 28
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
9.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . 29
9.2. New Registries . . . . . . . . . . . . . . . . . . . . . 29
10. Security Considerations . . . . . . . . . . . . . . . . . . . 30
10.1. Potential Threat Modes . . . . . . . . . . . . . . . . . 30
Show full document text