Architectural Considerations for Diameter Load Information
draft-campbell-dime-load-considerations-01

Document Type Expired Internet-Draft (individual)
Last updated 2015-09-10 (latest revision 2015-03-09)
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-load-considerations-01.txt

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 Diameter Overload Information Conveyance (DOIC) solution describes a mechanism meeting most of the requirements, but does not currently include the ability to send load information. This document explores some architectural considerations for a mechanism to send Diameter load information.

Authors

Ben Campbell (ben@nostrum.com)
Steve Donovan (srdonovan@usdonovans.com)
Jean-Jacques Trottin (jean-jacques.trottin@alcatel-lucent.com)

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