draft-ietf-dime-overload-reqs-09.txt   draft-ietf-dime-overload-reqs-10.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: January 16, 2014 July 15, 2013 Expires: January 30, 2014 July 29, 2013
Diameter Overload Control Requirements Diameter Overload Control Requirements
draft-ietf-dime-overload-reqs-09 draft-ietf-dime-overload-reqs-10
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, listed in Section 4 are not sufficient for this Diameter mechanisms, listed in Section 4 are not sufficient for this
purpose. This document describes the limitations of the existing purpose. This document describes the limitations of the existing
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 January 16, 2014. This Internet-Draft will expire on January 30, 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 6, line 22 skipping to change at page 6, line 22
and any work to further mitigate network congestion is out of scope and any work to further mitigate network congestion is out of scope
both for this document, and for the work proposed by this document. both for this document, and for the work proposed by this document.
1.5. Diameter Applications in a Broader Network 1.5. Diameter Applications in a Broader Network
Most elements using Diameter applications do not use Diameter Most elements using Diameter applications do not use Diameter
exclusively. It is important to realize that overload of an element exclusively. It is important to realize that overload of an element
can be caused by a number of factors that may be unrelated to the can be caused by a number of factors that may be unrelated to the
processing of Diameter or Diameter applications. processing of Diameter or Diameter applications.
A element communicating via protocols other than Diameter that is An element that doesn't use Diameter exclusively needs to be able to
also using a Diameter application needs to be able to signal to signal to Diameter peers that it is experiencing overload regardless
Diameter peers that it is experiencing overload regardless of the of the cause of the overload, since the overload will affect that
cause of the overload, since the overload will affect that element's element's ability to process Diameter transactions. If the element
ability to process Diameter transactions. The element may also need communicates with other protocols than Diameter, it may also need to
to signal this on other protocols depending on its function and the signal the overload situation on these protocols depending on its
architecture of the network and application it is providing services function and the architecture of the network and application it is
for. Whether that is necessary can only be decided within the providing services for. Whether that is necessary can only be
context of that architecture and application. A mechanism for decided within the context of that architecture and use cases. A
signaling overload with Diameter, which this specification details mechanism for signaling overload with Diameter, which this
the requirements for, provides Diameter nodes the ability to signal specification details the requirements for, provides Diameter nodes
their Diameter peers of overload, mitigating that part of the issue. the ability to signal their Diameter peers of overload, mitigating
Diameter nodes may need to use this, as well as other mechanisms, to that part of the issue. Diameter nodes may need to use this, as well
solve their broader overload issues. Indicating overload on as other mechanisms, to solve their broader overload issues.
protocols other than Diameter is out of scope for this document, and Indicating overload on protocols other than Diameter is out of scope
for the work proposed by this document. for this document, and for the work proposed by this document.
2. Overload Control Scenarios 2. Overload Control Scenarios
Several Diameter deployment scenarios exist that may impact overload Several Diameter deployment scenarios exist that may impact overload
management. The following scenarios help motivate the requirements management. The following scenarios help motivate the requirements
for an overload management mechanism. for an overload management mechanism.
These scenarios are by no means exhaustive, and are in general These scenarios are by no means exhaustive, and are in general
simplified for the sake of clarity. In particular, the authors simplified for the sake of clarity. In particular, the authors
assume for the sake of clarity that the client sends Diameter assume for the sake of clarity that the client sends Diameter
 End of changes. 4 change blocks. 
19 lines changed or deleted 19 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/