[sip-overload] RFC 7339 on Session Initiation Protocol (SIP) Overload Control
rfc-editor@rfc-editor.org Tue, 23 September 2014 20:01 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7641A1BF9; Tue, 23 Sep 2014 13:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level:
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 fV9CxDM_HveC; Tue, 23 Sep 2014 13:01:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3331A1BB4; Tue, 23 Sep 2014 13:01:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B1EF180015; Tue, 23 Sep 2014 13:01:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140923200105.4B1EF180015@rfc-editor.org>
Date: Tue, 23 Sep 2014 13:01:05 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/sip-overload/jOlYAjWhwhkXRq3kc0NYRbO2QSI
Cc: drafts-update-ref@iana.org, sip-overload@ietf.org, rfc-editor@rfc-editor.org
Subject: [sip-overload] RFC 7339 on Session Initiation Protocol (SIP) Overload Control
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 23 Sep 2014 20:01:20 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7339 Title: Session Initiation Protocol (SIP) Overload Control Author: V. Gurbani, Ed., V. Hilt, H. Schulzrinne Status: Standards Track Stream: IETF Date: September 2014 Mailbox: vkg@bell-labs.com, volker.hilt@bell-labs.com, hgs@cs.columbia.edu Pages: 38 Characters: 89898 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-soc-overload-control-15.txt URL: https://www.rfc-editor.org/rfc/rfc7339.txt Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all the 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 defines the behavior of SIP servers involved in overload control and also specifies a loss-based overload scheme for SIP. This document is a product of the SIP Overload Control Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://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