[sip-overload] RFC 7200 on A Session Initiation Protocol (SIP) Load-Control Event Package

rfc-editor@rfc-editor.org Wed, 30 April 2014 23:59 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 42EC11A0A02; Wed, 30 Apr 2014 16:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xidb-iDBpCqR; Wed, 30 Apr 2014 16:59:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 015221A6F22; Wed, 30 Apr 2014 16:59:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 80E6018000D; Wed, 30 Apr 2014 16:59:22 -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: <20140430235922.80E6018000D@rfc-editor.org>
Date: Wed, 30 Apr 2014 16:59:22 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/sip-overload/svTmz2hXoS4DkAILyFp3HeC9Zyg
Cc: drafts-update-ref@iana.org, sip-overload@ietf.org, rfc-editor@rfc-editor.org
Subject: [sip-overload] RFC 7200 on A Session Initiation Protocol (SIP) Load-Control Event Package
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: Wed, 30 Apr 2014 23:59:43 -0000

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

        RFC 7200

        Title:      A Session Initiation Protocol (SIP) 
                    Load-Control Event Package 
        Author:     C. Shen, H. Schulzrinne,
                    A. Koike
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2014
        Mailbox:    charles@cs.columbia.edu, 
        Pages:      44
        Characters: 98689
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-soc-load-control-event-package-13.txt

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

This specification defines a load-control event package for the
Session Initiation Protocol (SIP).  It allows SIP entities to
distribute load-filtering policies to other SIP entities in the
network.  The load-filtering policies contain rules to throttle calls
from a specific user or based on their source or destination domain,
telephone number prefix.  The mechanism helps to prevent signaling
overload and complements feedback-based SIP overload control efforts.

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 Internet
Official Protocol Standards (STD 1) 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

For searching the RFC series, see http://www.rfc-editor.org/search
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