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

Charles Shen <charles@cs.columbia.edu> Mon, 06 June 2011 03:25 UTC

Return-Path: <charles.newyork@gmail.com>
X-Original-To: sip-overload@ietfa.amsl.com
Delivered-To: sip-overload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7100D11E8086 for <sip-overload@ietfa.amsl.com>; Sun, 5 Jun 2011 20:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdkdqP+AJmj5 for <sip-overload@ietfa.amsl.com>; Sun, 5 Jun 2011 20:25:31 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id D0EE111E808A for <sip-overload@ietf.org>; Sun, 5 Jun 2011 20:25:31 -0700 (PDT)
Received: by iwn39 with SMTP id 39so4230327iwn.31 for <sip-overload@ietf.org>; Sun, 05 Jun 2011 20:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=0v1HVtaq4/X15bSyfItwLoO4rVylZtjKpilF/1ckqDs=; b=V8j5z4cX0aMq1IAA0rIV/5vPbDkXOw3/LavaeTZmkapipn6LEI/TGJcTi6kMTR7fcS l6PcKjAohIRZWhra9mIP2pWpdA3Rzm5PHdQPsfI9fYLfmLshjLquH3FHPrxXeS6IsU5k HVITYSLtm0fAIoQfWEToPhHw0mnDd7xnBYd9k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; b=pRPghaIF9lPfc7e53sus7G22GlfguDM7TJt1ZkWk/nNWzXn7R/Bj3BSf2kH4gO4ZLs rIo+kIET9FjmQS52wASkEAIrVvBov5Bmdq178+06bkkGawSuvs6yVLUO4tcR2OUjZwm/ sghakAtQgJRW5t8gLQO0/XwWcFYAVO1hkVcLY=
Received: by 10.42.71.84 with SMTP id i20mr2428684icj.236.1307330731073; Sun, 05 Jun 2011 20:25:31 -0700 (PDT)
MIME-Version: 1.0
Sender: charles.newyork@gmail.com
Received: by 10.42.228.136 with HTTP; Sun, 5 Jun 2011 20:25:10 -0700 (PDT)
From: Charles Shen <charles@cs.columbia.edu>
Date: Sun, 5 Jun 2011 23:25:10 -0400
X-Google-Sender-Auth: ZFr0pQbUHxSPvjDPGs-OvCwyPWA
Message-ID: <BANLkTi=Q_Z_tcK=Lrwo-_XAxMgQwp4Z2og@mail.gmail.com>
To: "sip-overload@ietf.org" <sip-overload@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Volker Hilt <volker.hilt@alcatel-lucent.com>, Arata Koike <koike.arata@lab.ntt.co.jp>, Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: [sip-overload] draft-shen-soc-avalanche-restart-overload
X-BeenThere: sip-overload@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 06 Jun 2011 03:25:33 -0000

Hi all,

The IETF80 minutes below show mixed feedbacks about the avalanche
restart draft. I would therefore like to follow up discussing about
the comments raised.

1. There is an explicite mention of the "Outbound proxy RFC" which
"has timer to solve the issue". I assumed that means RFC5626 and took
a second look at it. One section I found could be most relevant is
Section 4.5 Flow Recovery, where it says each new registration "is
done in much the same way as forming a brand new flow as described in
Section 4.2; however, if there is a failure in forming this flow, the
UA needs to wait a certain amount of time before retrying to form a
flow to this particular next hop". The subsequent paragraphs in that
section define a way to compute the backoff time.

Back to Section 4.2, I did not find discussion about whether and how
the *initial registation* should be randomized. If that is the case,
the solution is different from what is presented in this avalanche
restart draft. The mechanism in this draft seeks to avoid the initial
storm of registration or similar message causing avalanche restart.
And if this effort is successful, subsequent backoff might not be
necessary, although I think inclusion of RFC5626 backoff timers would
certainly increase robustness.

2. There is also a suggestion to discuss this in dispatch. Since
"avalanche restart" is a problem described in the overload requirement
RFC 5390, maybe AD and/or chairs can advice whether we should cross
post this discussion or keep it in either one list for now.

Thanks

Charles



On Thu, Apr 28, 2011 at 1:54 PM, Salvatore Loreto
<salvatore.loreto@ericsson.com> wrote:
> Hi there,
>
> below the notes from the SoC session during the IETF80 meeting in Prague.
> (I have already uploaded this initial version to ietf proceeding site)
>
> Please review them and submit any correction to the chairs by May 11.
> The chairs have to send the notes toproceedings@ietf.org  by May18th.
>
> (many thanks to Partha for taking notes during the meeting)
>
> cheers
> /Sal
>
> --
> Salvatore Loreto
> www.sloreto.com
>

snipped ...

>
>
> Avalanche restart overload  (Presenter: Arate Koike)
> ------------------------
> Hadriel: Let register has restart-timer instead of subscribe as it is
> register avalanche. SUBSCRIBE may not go to Registrar.
> Partha: SUBSCRIBE message itself may overload
>
> Open discussion:
> Hadriel: Mention this problem may not be solved by the proposed mechanism.
> Partha: The problem solved by Avalanche is in the boot up time only.
> Hadriel, Robert: Outbound proxy RFC has timer to solve the issue and it is
> not generic
> Partha: Agreed, It will not solve all the problem
> Robert: Discuss in dispatch
>
> _______________________________________________
> sip-overload mailing list
> sip-overload@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-overload
>



Thanks

Charles