Re: [Pce] New version of the stateful pce applicability draft - draft-zhang-pce-stateful-pce-app-04

Ravi Torvi <pratiravi@gmail.com> Tue, 04 June 2013 17:42 UTC

Return-Path: <pratiravi@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0F9B21F9B60 for <pce@ietfa.amsl.com>; Tue, 4 Jun 2013 10:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOBB4D-MhBd6 for <pce@ietfa.amsl.com>; Tue, 4 Jun 2013 10:41:59 -0700 (PDT)
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by ietfa.amsl.com (Postfix) with ESMTP id 443E521F9D8A for <pce@ietf.org>; Tue, 4 Jun 2013 09:31:46 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id 13so887903lba.40 for <pce@ietf.org>; Tue, 04 Jun 2013 09:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YammejqnZnCFbmePgpav6whl3zZV+LGulULf3/EcihY=; b=aX+zRo1/2V5y/MHsMuxPwmyR2jCcrrQo6C8JfigGuLLAdX3O9FCuQab9TtssJRBjU+ DBbVsEHF38zFD1khodp5LjQWcmmymYI9bU5FRGJuLduAV4jGTLl3IFJlmrNKU06g8n86 qM0kMSiH4oOkiSkyieuR4tN80nd+jwjL+am8IQ08di2Whv9anYGH3K1eBASkQkHQE8P/ e9ZxN3z2VpzfFbVZxKYIA9P01Ar3cmT4CzcklbSpQm+ij9OjHgn64QMY76Ic2OsZ2eKf 16nWXJNm4yEe4VzkMYd0/j2Z3uFtusBiViI/1z3NkglApzXgnE70oGDIDD6jW2sgzgu/ jvjA==
MIME-Version: 1.0
X-Received: by 10.112.33.17 with SMTP id n17mr13277924lbi.72.1370363505051; Tue, 04 Jun 2013 09:31:45 -0700 (PDT)
Received: by 10.112.21.69 with HTTP; Tue, 4 Jun 2013 09:31:44 -0700 (PDT)
In-Reply-To: <036001ce5fa7$01a6aa40$04f3fec0$@olddog.co.uk>
References: <70BDAD02381BA54CA31315A2A26A7AD3037AFA02@BLUPRD0511MB436.namprd05.prod.outlook.com> <036001ce5fa7$01a6aa40$04f3fec0$@olddog.co.uk>
Date: Tue, 04 Jun 2013 12:31:44 -0400
Message-ID: <CAHAy71t8Qt1rQWaN2rV-uV=YnV7criFUmH=C86R7VLNHxJJ24w@mail.gmail.com>
From: Ravi Torvi <pratiravi@gmail.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary="14dae93d9446ee92d004de569d0d"
Cc: pce@ietf.org
Subject: Re: [Pce] New version of the stateful pce applicability draft - draft-zhang-pce-stateful-pce-app-04
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jun 2013 17:42:03 -0000

Hi Ina & Authors,
Now that we have new WG charter, I think it is a good time to clarify
applicability of PCE-Stateful.

Following are some of my observations that can be considered in your next
revisions of draft:

1. We need to scope the PCE-Stateful applicability, i.e., clarify
explicitly where vanilla PCE can be sufficient or PCE-Stateful could be an
overkill.
    - Similarly, it would be nice to describe deployments of Passive
Stateful PCE and  with Active Stateful PCE separately

I think draft describes goodness of Stateful well, however, it should
provide guidelines for choosing right set of PCE-stateful features.

Few basic applications (I am not sure this draft covers them explicitly)
from PCC Scale point of view:

2. I think draft should describe on performance w/ PCE-Stateful
    i.e., How PCE Stateful helps in dynamic changes compared to NMS based.

3. One obvious applicability of Active PCE-Stateful would be : config
scaling. Operators do not have to maintain tons of LSP configuration on the
box.

4. LSP monitoring is less expensive with PCE Stateful, as PCE is expected
to maintain complete state.
This reduces burden on routers.

Thanks,
Ravi



http://www.google.com/profiles/pratiravi


On Sun, Jun 2, 2013 at 11:36 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Ina, WG,****
>
> ** **
>
> Pleased to see people thinking about applicability and use cases. IMHO,
> not enough attention is paid to why we are doing things and how they will
> be used. ****
>
> ** **
>
> Thanks for the work, and hope people will review it (especially service
> providers!)****
>
> ** **
>
> Adrian****
>
> ** **
>
> *From:* pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] *On Behalf Of *Ina
> Minei
> *Sent:* 26 May 2013 22:52
> *To:* pce@ietf.org
> *Subject:* [Pce] New version of the stateful pce applicability draft -
> draft-zhang-pce-stateful-pce-app-04****
>
> ** **
>
> A new version of the stateful pce applicability draft was posted
> yesterday. ****
>
>  ****
>
> In the interest of making progress on this document, the authors would
> like to solicit review, comments and discussion from the working group,
> before the next IETF meeting. ****
>
>  ****
>
>  ****
>
> URL:
> http://www.ietf.org/internet-drafts/draft-zhang-pce-stateful-pce-app-04.txt
> ****
>
> Status:
> http://datatracker.ietf.org/doc/draft-zhang-pce-stateful-pce-app****
>
> Htmlized:
> http://tools.ietf.org/html/draft-zhang-pce-stateful-pce-app-04****
>
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-zhang-pce-stateful-pce-app-04****
>
>  ****
>
>  ****
>
> Ina and Xian on behalf of all the authors****
>
>  ****
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
>