[sip-overload] RFC 6357 on Design Considerations for Session Initiation Protocol (SIP) Overload Control
rfc-editor@rfc-editor.org Wed, 31 August 2011 21:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 1C20821F8E7B; Wed, 31 Aug 2011 14:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level:
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.114,
BAYES_00=-2.599, NO_RELAYS=-0.001, 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 qP-yn6iAsePv;
Wed, 31 Aug 2011 14:35:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by
ietfa.amsl.com (Postfix) with ESMTP id A26D521F8E2E;
Wed, 31 Aug 2011 14:35:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A538398C24E;
Wed, 31 Aug 2011 14:36:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110831213657.A538398C24E@rfc-editor.org>
Date: Wed, 31 Aug 2011 14:36:57 -0700 (PDT)
Cc: sip-overload@ietf.org, rfc-editor@rfc-editor.org
Subject: [sip-overload] RFC 6357 on Design Considerations for Session
Initiation Protocol (SIP) Overload Control
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Overload <sip-overload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip-overload>
List-Post: <mailto:sip-overload@ietf.org>
List-Help: <mailto:sip-overload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip-overload>,
<mailto:sip-overload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2011 21:35:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6357
Title: Design Considerations for Session Initiation
Protocol (SIP) Overload Control
Author: V. Hilt, E. Noel,
C. Shen, A. Abdelal
Status: Informational
Stream: IETF
Date: August 2011
Mailbox: volker.hilt@alcatel-lucent.com,
eric.noel@att.com,
charles@cs.columbia.edu,
aabdelal@sonusnet.com
Pages: 25
Characters: 64252
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-soc-overload-design-08.txt
URL: http://www.rfc-editor.org/rfc/rfc6357.txt
Overload occurs in Session Initiation Protocol (SIP) networks when
SIP servers have insufficient resources to handle all SIP messages
they receive. Even though the SIP protocol provides a limited
overload control mechanism through its 503 (Service Unavailable)
response code, SIP servers are still vulnerable to overload. This
document discusses models and design considerations for a SIP
overload control mechanism. This document is not an Internet
Standards Track specification; it is published for informational purposes.
This document is a product of the SIP Overload Control 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/rfcsearch.html.
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