Re: [dispatch] draft-shen-soc-avalanche-restart-overload

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Sat, 15 February 2014 23:35 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 345311A00F5 for <dispatch@ietfa.amsl.com>; Sat, 15 Feb 2014 15:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.049
X-Spam-Level:
X-Spam-Status: No, score=-110.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, 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 uMU9LAdt1tb5 for <dispatch@ietfa.amsl.com>; Sat, 15 Feb 2014 15:35:42 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id CB6A41A022B for <dispatch@ietf.org>; Sat, 15 Feb 2014 15:35:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2381; q=dns/txt; s=iport; t=1392507340; x=1393716940; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=H5mEPXH2d2RKcgkCiUo5zUZvYVwt5E9qxIYqoHvFJRY=; b=lziQaAr4WO5Y/uQq34KUrW3wnV39t8IUWzzFsKZX2w2fdglCcA0bUaDI 594lkl0Rewyp6+ZLjc+7E6x5LzHABJbyGx6nxJNrcE+pEUqCVUnWxNvfQ YG/+rynyO6CLk0iNQlNiCiZG4DMscrNd/UkAN+jJGRxbWmMs+S0uiRbmr U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioFAIH4/1KtJV2c/2dsb2JhbABZDoJ4OFe+bU+BDxZ0giUBAQEDAQEBAWsLBQsCAQgkIicLJQIEDgUUh2kIDck3F44zGzMHgySBFASYLIEykHGCbj+CKg
X-IronPort-AV: E=Sophos;i="4.95,852,1384300800"; d="scan'208";a="20775721"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP; 15 Feb 2014 23:35:39 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s1FNZdC1016648 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Feb 2014 23:35:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.105]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Sat, 15 Feb 2014 17:35:39 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Charles Shen <charles@cs.columbia.edu>
Thread-Topic: [dispatch] draft-shen-soc-avalanche-restart-overload
Thread-Index: AQHPKqahBkj4OIFP6USMZv7/Bsbi+Q==
Date: Sat, 15 Feb 2014 23:35:38 +0000
Message-ID: <FE17D37B-5E97-4EBD-A198-9D21E5FC9034@cisco.com>
References: <CAPSQ9ZWxwomvKJBKbSTpO8B83wis=7+oqkfZYE7cg3RQ7wcf3g@mail.gmail.com>
In-Reply-To: <CAPSQ9ZWxwomvKJBKbSTpO8B83wis=7+oqkfZYE7cg3RQ7wcf3g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.246.94]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A7A3F552F19F1C4C955B2E215A9604BD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/cqT-8E7OS2hBRvEOGPod-AWDoHA
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] draft-shen-soc-avalanche-restart-overload
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Feb 2014 23:35:45 -0000

This seems like a draft that could benefit from review in a WG. Can someone fill in a bit of the background of this draft in SOC. I’m not seeing why the SOC charter would need to be changed to do this work. 



On Feb 11, 2014, at 1:35 PM, Charles Shen <charles@cs.columbia.edu> wrote:

> Dear all: 
> 
> As advised by Richard Barnes, I am writing to seek opinion from you about this draft:
> 
> http://datatracker.ietf.org/doc/draft-shen-soc-avalanche-restart-overload/
> A Mechanism for Session Initiation Protocol (SIP) Avalanche Restart Overload Control
> 
> Abstract:
>    When a large number of clients register with a SIP registrar server
>    at approximately the same time, the server may become overloaded.
>    Near-simultaneous floods of SIP SUBSCRIBE and PUBLISH requests may
>    have similar effects.  Such request avalanches can occur, for
>    example, after a power failure and recovery in a metropolitan area.
>    This document describes how to avoid such overload situations.  Under
>    this mechanism, a server estimates an avalanche restart backoff
>    interval during its normal operation and conveys this interval to its
>    clients through a new Restart-Timer header in normal response
>    messages.  Once an avalanche restart actually occurs, the clients
>    perform backoff based on the previously received Restart-Timer header
>    value before sending out the first request attempt.  Thus, the
>    mechanism spreads all the initial client requests and prevents them
>    from overloading the server.
> 
> The draft has been presented and discussed in IETF meetings since 2010, and generated interest among the community:
> 
> https://encrypted.google.com/search?as_q=draft-shen-soc-avalanche-restart-overload&as_sitesearch=www.ietf.org%2Fmail-archive%2Fweb%2F
> 
> I am looking for your kind opinion on what should be the appropriate next step for this document:
> 
> -- Should this draft be dispatched to SOC (and their charter amended)?
> -- Should this draft be processed as AD-sponsored?
> -- Should this draft be killed (if it is harmful)?
> 
> Thank you very much.
> 
> Charles
> 
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch