RFC 7068 on Diameter Overload Control Requirements

rfc-editor@rfc-editor.org Wed, 20 November 2013 00:25 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8791AE25C; Tue, 19 Nov 2013 16:25:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnOmPmzruQoa; Tue, 19 Nov 2013 16:25:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id BB6281AE250; Tue, 19 Nov 2013 16:25:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A963175E020; Tue, 19 Nov 2013 16:14:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7068 on Diameter Overload Control Requirements
From: rfc-editor@rfc-editor.org
Message-Id: <20131120001459.A963175E020@rfc-editor.org>
Date: Tue, 19 Nov 2013 16:14:59 -0800
Cc: drafts-update-ref@iana.org, dime@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 00:25:25 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7068

        Title:      Diameter Overload Control Requirements 
        Author:     E. McMurry, B. Campbell
        Status:     Informational
        Stream:     IETF
        Date:       November 2013
        Mailbox:    emcmurry@computer.org, 
                    ben@nostrum.com
        Pages:      29
        Characters: 69536
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dime-overload-reqs-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7068.txt

When a Diameter server or agent becomes overloaded, it needs to be
able to gracefully reduce its load, typically by advising clients to
reduce traffic for some period of time.  Otherwise, it must continue
to expend resources parsing and responding to Diameter messages,
possibly resulting in a progressively severe overload condition.  The
existing Diameter mechanisms are not sufficient for managing overload
conditions.  This document describes the limitations of the existing
mechanisms.  Requirements for new overload management mechanisms are
also provided.

This document is a product of the Diameter Maintenance and Extensions Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC