Diameter Overload Control Solution Issues
draft-campbell-dime-overload-issues-01

Document Type Expired Internet-Draft (individual)
Last updated 2014-01-16 (latest revision 2013-07-15)
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-issues-01.txt

Abstract

The Diameter Maintenance and Extensions (DIME) working group has undertaken an "overload control" work item, with the goal of standardizing a mechanism to allow Diameter nodes to report overload information among themselves. Requirements currently include, among others, the need to accurately report the scope of overload conditions, and the ability to report overload information between nodes that are not directly connected at the transport layer. These requirements introduce complex issues. This document describes those issues, in the hope that it will assist the working group's decision process.

Authors

Ben Campbell (ben@nostrum.com)

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