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

Charles Shen <charles@cs.columbia.edu> Sun, 16 February 2014 19:09 UTC

Return-Path: <charles.newyork@gmail.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 BEC731A0227 for <dispatch@ietfa.amsl.com>; Sun, 16 Feb 2014 11:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 dWieEVkEmhqY for <dispatch@ietfa.amsl.com>; Sun, 16 Feb 2014 11:09:51 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 22AD71A020D for <dispatch@ietf.org>; Sun, 16 Feb 2014 11:09:51 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so16803978oah.3 for <dispatch@ietf.org>; Sun, 16 Feb 2014 11:09:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=GLJt2BzKq9Z/+lpdPjT2VB1mzHPZ095U9KtBJMeCoFA=; b=MV7fg2qgN6lQsDBWrEq0zvGqdGMhhE2gs394ZAh7MZsIdiwdDKXZuaDvziTQ56MXJS g+ZyU8QAiBDeN5vM5jQOgKgVfhbwJmPGKPZmWFeWDKmp9GTqxVNc8/utEqKNU2zoPOtr j0sy7U1sNUZzKnFfMhFyE26yi4xV50A8ysQku+nDSDwKkZBNz/gwXBFYZWrcgiKmKKH0 ALKSBDm7XWLE9Th15AtcRoFRSbpRBtVMCET95zlZVgsh7E4nrtFZcPucBS5qpJ11N6dQ hgEvNEGJq/2qSSSxft0gjk8oXsUS02Hch41vNMMuFY85bQdaJgrX6Aawur4zM6uidRTI zVFg==
X-Received: by 10.182.113.195 with SMTP id ja3mr2705431obb.46.1392577788688; Sun, 16 Feb 2014 11:09:48 -0800 (PST)
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.182.55.106 with HTTP; Sun, 16 Feb 2014 11:09:28 -0800 (PST)
In-Reply-To: <FE17D37B-5E97-4EBD-A198-9D21E5FC9034@cisco.com>
References: <CAPSQ9ZWxwomvKJBKbSTpO8B83wis=7+oqkfZYE7cg3RQ7wcf3g@mail.gmail.com> <FE17D37B-5E97-4EBD-A198-9D21E5FC9034@cisco.com>
From: Charles Shen <charles@cs.columbia.edu>
Date: Sun, 16 Feb 2014 14:09:28 -0500
X-Google-Sender-Auth: AYy80VMU2Fki15bQ18FE-BiwMhY
Message-ID: <CAPSQ9ZW90YLHkO387CWM6hfmnUJ1aLAB3v2pCMjxgnrRuh5s_g@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="089e013d0db06ac0d204f28ac8b1"
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/a05N4XwwrZp1LAKviC801ZoYFyo
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: Sun, 16 Feb 2014 19:09:54 -0000

Thanks Cullen for your comments,

According to my understanding, the current charter description

http://datatracker.ietf.org/wg/soc/charter/

does not seem to cover the goal of advancing this draft into a working
group deliverable. Please correct me if I were wrong.

Thanks

Charles




On Sat, Feb 15, 2014 at 6:35 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote:

>
> 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
>
>