draft-ietf-dime-overload-reqs-11.txt   draft-ietf-dime-overload-reqs-12.txt 
Network Working Group E. McMurry Network Working Group E. McMurry
Internet-Draft B. Campbell Internet-Draft B. Campbell
Intended status: Informational Tekelec Intended status: Informational Tekelec
Expires: February 27, 2014 August 26, 2013 Expires: March 14, 2014 September 10, 2013
Diameter Overload Control Requirements Diameter Overload Control Requirements
draft-ietf-dime-overload-reqs-11 draft-ietf-dime-overload-reqs-12
Abstract Abstract
When a Diameter server or agent becomes overloaded, it needs to be When a Diameter server or agent becomes overloaded, it needs to be
able to gracefully reduce its load, typically by informing clients to able to gracefully reduce its load, typically by informing clients to
reduce sending traffic for some period of time. Otherwise, it must reduce sending traffic for some period of time. Otherwise, it must
continue to expend resources parsing and responding to Diameter continue to expend resources parsing and responding to Diameter
messages, possibly resulting in congestion collapse. The existing messages, possibly resulting in congestion collapse. The existing
Diameter mechanisms are not sufficient for this purpose. This Diameter mechanisms are not sufficient for this purpose. This
document describes the limitations of the existing mechanisms. document describes the limitations of the existing mechanisms.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 27, 2014. This Internet-Draft will expire on March 14, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 20, line 39 skipping to change at page 20, line 39
REQ 12: When a single network node fails, goes into overload, or REQ 12: When a single network node fails, goes into overload, or
suffers from reduced processing capacity, the solution MUST suffers from reduced processing capacity, the solution MUST
make it possible to limit the impact of this on other nodes make it possible to limit the impact of this on other nodes
in the network. This helps to prevent a small-scale failure in the network. This helps to prevent a small-scale failure
from becoming a widespread outage. from becoming a widespread outage.
REQ 13: The solution MUST NOT introduce substantial additional work REQ 13: The solution MUST NOT introduce substantial additional work
for node in an overloaded state. For example, a requirement for node in an overloaded state. For example, a requirement
for an overloaded node to send overload information every for an overloaded node to send overload information every
time it received a new request would introduce substantial time it received a new request would introduce substantial
work. Existing messaging is likely to have the work.
characteristic of increasing as an overload condition
approaches, allowing for the possibility of increased
feedback for information piggybacked on it.
REQ 14: Some scenarios that result in overload involve a rapid REQ 14: Some scenarios that result in overload involve a rapid
increase of traffic with little time between normal levels increase of traffic with little time between normal levels
and overload inducing levels. The solution SHOULD provide and overload inducing levels. The solution SHOULD provide
for rapid feedback when traffic levels increase. for rapid feedback when traffic levels increase.
REQ 15: The solution MUST NOT interfere with the congestion control REQ 15: The solution MUST NOT interfere with the congestion control
mechanisms of underlying transport protocols. For example, mechanisms of underlying transport protocols. For example,
a solution that opened additional TCP connections when the a solution that opened additional TCP connections when the
network is congested would reduce the effectiveness of the network is congested would reduce the effectiveness of the
 End of changes. 4 change blocks. 
7 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/