[Dime] I-D Action: draft-ietf-dime-overload-reqs-13.txt

internet-drafts@ietf.org Mon, 30 September 2013 18:53 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867B921F856A; Mon, 30 Sep 2013 11:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level:
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+VRT-6IRw+1; Mon, 30 Sep 2013 11:53:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C946121F9D9C; Mon, 30 Sep 2013 11:53:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130930185337.31558.77133.idtracker@ietfa.amsl.com>
Date: Mon, 30 Sep 2013 11:53:37 -0700
Cc: dime@ietf.org
Subject: [Dime] I-D Action: draft-ietf-dime-overload-reqs-13.txt
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2013 18:53:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF.

	Title           : Diameter Overload Control Requirements
	Author(s)       : Eric McMurry
                          Ben Campbell
	Filename        : draft-ietf-dime-overload-reqs-13.txt
	Pages           : 28
	Date            : 2013-09-30

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.  Otherwise, it must
   continue to expend resources parsing and responding to Diameter
   messages, possibly resulting in a progressively more severe overload
   condition.  The existing Diameter mechanisms are not sufficient for
   this purpose.  This document describes the limitations of the
   existing mechanisms.  Requirements for new overload management
   mechanisms are also provided.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dime-overload-reqs

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dime-overload-reqs-13

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dime-overload-reqs-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/