Re: [sip-overload] Protocol Action: 'Session Initiation Protocol (SIP) Rate Control' to Proposed Standard (draft-ietf-soc-overload-rate-control-10.txt)

Atle Monrad <> Mon, 05 January 2015 13:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 14AF91A6F33 for <>; Mon, 5 Jan 2015 05:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IgmECsZMl4IV for <>; Mon, 5 Jan 2015 05:09:26 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3623A1A6F34 for <>; Mon, 5 Jan 2015 05:09:20 -0800 (PST)
X-AuditID: c1b4fb25-f791c6d00000617b-e4-54aa8cfdfe86
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 61.10.24955.DFC8AA45; Mon, 5 Jan 2015 14:09:17 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Mon, 5 Jan 2015 14:09:16 +0100
From: Atle Monrad <>
To: soc chair <>
Thread-Topic: [sip-overload] Protocol Action: 'Session Initiation Protocol (SIP) Rate Control' to Proposed Standard (draft-ietf-soc-overload-rate-control-10.txt)
Thread-Index: AQHP7KZ3vtUXMyBbFUOIzoj/+mjRxpyx9ulA
Date: Mon, 5 Jan 2015 13:09:16 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: nb-NO, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvje7fnlUhBhPPmVvsf5pgsePQA1YH Jo8lS34yeXy5/JktgCmKyyYlNSezLLVI3y6BK2Pn0g9MBa8kK3582MfcwLhOtIuRk0NCwETi 2aODzBC2mMSFe+vZuhi5OIQEjjBKdE2ewQLhLGaUODzlDwtIFZuAjsS5n3dYQWwRAU2J7ROe MoLYzEDxoze+MoM0CAssYZSYcmgbK4gjIrCUUaJxXiczRIeRxOr2LiCbg4NFQEXifRs/SJhX wFeie/tfNhBbSMBBYvqxN+wgNqeAo8S+X59ZQcoZBWQl5jbxQuwSl7j1ZD4TxNUCEkv2nIf6 QFTi5eN/rBC2osTV6cuZYG5bsPsTG4StLbFs4WtmiLWCEidnPmGZwCg2C8nYWUhaZiFpmYWk ZQEjyypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwPg5uOW36g7Gy28cDzEKcDAq8fAa/FsZ IsSaWFZcmXuIUZqDRUmcd+G5ecFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGPnuezTbH8/Q vry8Zdvv5IdHF+vObfntekB4Pv+mFxsTG8ME0pX+zFrsICWnP7PRu0xIYafBh7S/WgU+xsen XVyxfP7Rld5XqlVu/s+LZ/x2VCx72UKH/Ds6rbdOXhQQLb1uktY/lX2W/UrXFTLKH/y/7rnH GKuvupndOlbl76PXTEdVj/J87VFiKc5INNRiLipOBADeDXHogAIAAA==
Cc: soc mailing list <>
Subject: Re: [sip-overload] Protocol Action: 'Session Initiation Protocol (SIP) Rate Control' to Proposed Standard (draft-ietf-soc-overload-rate-control-10.txt)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Overload <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Jan 2015 13:09:29 -0000


May I ask if the draft will move forward soon?

The draft is in AUTH48 since Dec 03 2014

Has some major obstacle appeared, or will the draft appear as RFC soon?

3GPP is waiting ...



Atle Monrad
3GPP CT Chairman

Group Function Technology - Standardization and Technical Regulation 

-----Original Message-----
From: sip-overload [] On Behalf Of The IESG
Sent: 20. oktober 2014 22:42
To: IETF-Announce
Cc: soc chair; soc mailing list; RFC Editor
Subject: [sip-overload] Protocol Action: 'Session Initiation Protocol (SIP) Rate Control' to Proposed Standard (draft-ietf-soc-overload-rate-control-10.txt)

The IESG has approved the following document:
- 'Session Initiation Protocol (SIP) Rate Control'
  (draft-ietf-soc-overload-rate-control-10.txt) as Proposed Standard

This document is the product of the SIP Overload Control Working Group.

The IESG contact persons are Richard Barnes and Alissa Cooper.

A URL of this Internet Draft is:

Technical Summary:

The document defines a rate-based overload control mechanism for the Session Initiation Protocol (SIP) to prevent signaling overload. It uses the framework defined in the Session Initiation Protocol (SIP) Overload Control specification and adds the specifications needed for a rate-based control mechanism. With this specification, SIP entities can choose between the loss-based overload control defined in Session Initiation Protocol (SIP) Overload Control and the rate-based overload control defined in this specification.

Working Group Summary:

The developement of this document resulted from a discussion in the WG on the overload feedback type (the pro's and con's of the feedback types discussed in Section 9. of RFC 6357). The WG decided to use loss-based control as the default mechanism in draft-ietf-soc-overload-control but allow extensions for other feedback types. Rate-based control was agreed as a needed extension as it has benefits in some scenarios. This draft provides the needed specifications for rate-based overload control. This draft was non-controversial and was is substantial interest in this specification. There was no competing proposal and it addresses the WG deliverable 'A specification for an SIP overload control mechanism based on implicit/explicit feedback'

Document Quality:
The basic mechanisms defined in this specification have been implemented and evaluated in several simulators as part of the work of the SIPPING Overload Control Design Team. The results of these evaluations were presented in several SIPPING WG meetings. The document has been reviewed several times as it has been developed by several members of the SOC WG including Salvatore Loreto, Janet Gunn, Christer Holmberg, James Yu, Keith Drage and Vijay Gurbani.

  Shepherd: Volker Hilt <>
  AD: Richard Barnes <>

sip-overload mailing list