Diameter Overload Data Analysis
draft-campbell-dime-overload-data-analysis-00

Document Type Expired Internet-Draft (individual)
Last updated 2013-08-22 (latest revision 2013-02-18)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-campbell-dime-overload-data-analysis-00.txt

Abstract

When a Diameter server or agent becomes overloaded, it needs to be able to gracefully reduce its load, typically by informing clients to reduce sending traffic for some period of time. Multiple mechanisms have been proposed for transporting overload and load information. While these proposals differ in many ways, they share similar data requirements. This document analyzes the data requirements of each proposal with a view towards proposing a common set of of Diameter Attribute-Value Pairs (AVPs).

Authors

Ben Campbell (ben@nostrum.com)
Hannes Tschofenig (hannes.tschofenig@nsn.com)
Jouni Korhonen (jouni.nospam@gmail.com)
Adam Roach (adam@nostrum.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)