Diameter Agent Overload
draft-donovan-dime-agent-overload-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-08-27
Replaced by draft-ietf-dime-agent-overload, rfc8581
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Diameter Maintenance and Extensions (DIME)                    S. Donovan
Internet-Draft                                                    Oracle
Intended status: Standards Track                         August 27, 2014
Expires: February 28, 2015

                        Diameter Agent Overload
                draft-donovan-dime-agent-overload-02.txt

Abstract

   This specification documents an extension to the Diameter Overload
   Control (DOC) base solution.  The extension addresses the handling of
   agent overload.

Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 28, 2015.

Copyright Notice

   Copyright (c) 2014 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

Donovan                 Expires February 28, 2015               [Page 1]
Internet-Draft           Diameter Agent Overload             August 2014

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and Abbreviations . . . . . . . . . . . . . . . .   3
   3.  Diameter Agent Overload Use Cases . . . . . . . . . . . . . .   4
     3.1.  Single Agent  . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Redundant Agents  . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Agent Chains  . . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Interaction between agent and end-point overload  . . . .   7
   4.  Agent Overload Report . . . . . . . . . . . . . . . . . . . .   8
     4.1.  OC-Supported-Features AVP . . . . . . . . . . . . . . . .   8
       4.1.1.  OC-Peer-Node  . . . . . . . . . . . . . . . . . . . .   8
     4.2.  OC-OLR AVP  . . . . . . . . . . . . . . . . . . . . . . .   9
       4.2.1.  OC-Reporting-Node . . . . . . . . . . . . . . . . . .   9
   5.  Agent Overload Behavior . . . . . . . . . . . . . . . . . . .  10
     5.1.  Capability Advertisement  . . . . . . . . . . . . . . . .  10
     5.2.  Agent Overload Reporting Node Behavior  . . . . . . . . .  10
     5.3.  Agent Overload Reacting Node Behavior . . . . . . . . . .  11
   6.  IANA  Considerations  . . . . . . . . . . . . . . . . . . . .  12
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   This document defines the behavior of Diameter nodes when Diameter
   agents become overloaded.

   The base Diameter overload specification [I-D.ietf-dime-ovli]
   addresses the handling of overload when a Diameter endpoint (a
   Diameter Client or Diameter server as defined in [RFC6733]) becomes
   overloaded.

   In the base specification, the goal is to react to the overload as
   close to the generator of the Diameter traffic as is feasible.  When
   possible this is done at the originator of the traffic, generally
   referred to as a Diameter Client.  A Diameter agent can also handle
   the overload mitigation.  For instance, a Diameter agent might handle
   Diameter overload mitigation when it knows that a Diameter client
   does not support the DOIC extension.

Donovan                 Expires February 28, 2015               [Page 2]
Internet-Draft           Diameter Agent Overload             August 2014

   This document extends the base Diameter endpoint overload
   specification to address the case when Diameter agents become
   overloaded.  Just as is the case with other Diameter nodes -- clients
Show full document text