Re: [Pce] draft-dhodylee-pce-pcep-ls next steps!

Gyan Mishra <hayabusagsm@gmail.com> Sat, 28 August 2021 07:27 UTC

Return-Path: <hayabusagsm@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 4B44E3A121A; Sat, 28 Aug 2021 00:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ClEMLMAghIdw; Sat, 28 Aug 2021 00:27:42 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23F653A1217; Sat, 28 Aug 2021 00:27:42 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id q3so5544830plx.4; Sat, 28 Aug 2021 00:27:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Q4YUYxoFqs76seZph2Lp0cNL0Xvrpbnc4UXGovJAK/I=; b=LhkyFQzGPlgmAqLcwVKQ7W7rFBiSP08qDF/uE1pcxuDmhVxmuA956oFiAK23MOfj1N 7sjzW6N4g7acjcAu8A3u6TeZ0GtViDGf+k3N89EHm2eTrIGT7jk+YnBbXUvtf8/w60Ya 6XBtrMohEcg3ozxSaFp0HBYWaLhdwLGtBd7om36LPgZPJgmMNDdeaHZcdTdkSIUBflui oWReyfQJUQmwCwn4Vvfo4wRRm29SuPpiBm86N/021X/JHAPTT3HYwkSIcE9OiVoP3Myf gcsrXEaos68Dtlm4Ugt/1lxZNr3SliCiiZMUs7zMpBnKH1etZDr7j1kxsJSysYsIIbaA H1CA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Q4YUYxoFqs76seZph2Lp0cNL0Xvrpbnc4UXGovJAK/I=; b=qXZ84AkPzrHzlAkEVCO9tP1OCzAhG8lfxugzl8bPD2EWXplPax3eQWShtxMPKALro8 eskQJ9Y4xYcLuafrItwBeoyYFRmbabAXcDauasKRKe8moO9JCg41XMw6DPhYmRtKS6M/ 8RayO6b3GWCMn3bYe0GB/yplHRq3M+8yFzA8b6e3pimWcH9z4gzknKoLmmTr+J/WI/xM oDSTHPrpvaaWbmC8Jj9jApem+8cP4+2Z/llhfoEsKJYe8mZwkOKQdfjdvXWxcme4N9hF qYQBRJ+GlOnX/w5UqWxuoOtz+3Nql7qiq7PcF8nKE9gZGxDfiwxNAcdAt5ux4EsOcwzJ pFww==
X-Gm-Message-State: AOAM530ev4SyenXSr1xT+O1FSe/U1ZRxWPxcZu5igp/qweNfYy1vBR98 6U0WzDc18MZRuL9Mzf5DaGqY2UvufPB60IEfs8do62z+
X-Google-Smtp-Source: ABdhPJwzHddzrHgpVzD3Gg4EFnl2vF4fVUm4+jLwxWeuH6mVvS7iCMpJFNauWz+xohO2JLAnkM9ZMfkiRsPj1FAJ800=
X-Received: by 2002:a17:90a:930e:: with SMTP id p14mr15182641pjo.132.1630135660451; Sat, 28 Aug 2021 00:27:40 -0700 (PDT)
MIME-Version: 1.0
References: <CABNhwV1hby7ap3DWQzxB2aV+ggVCeuDL89SNfaMA6RH0XiC8sQ@mail.gmail.com> <064a01d77c04$59272510$0b756f30$@olddog.co.uk> <CABNhwV3YJW=g_MW5zz7zimB0SFGpgLa=Hd4GUfEAE_nVYyhV3g@mail.gmail.com> <048401d799bd$b3a51c50$1aef54f0$@olddog.co.uk> <CABNhwV1-q73PojFG75e3Jfpj2O+6GgHaiFwN=5Mt+2aFV+=+2w@mail.gmail.com> <071401d79b3b$42fe3250$c8fa96f0$@olddog.co.uk>
In-Reply-To: <071401d79b3b$42fe3250$c8fa96f0$@olddog.co.uk>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 28 Aug 2021 03:27:29 -0400
Message-ID: <CABNhwV3ndFJWyTL7Nv80+z7mrR2s+X+LC+qb8ceWRdq+fEFApQ@mail.gmail.com>
To: adrian@olddog.co.uk
Cc: Dhruv Dhody <dd@dhruvdhody.com>, draft-dhodylee-pce-pcep-ls@ietf.org, pce@ietf.org, pce-chairs <pce-chairs@ietf.org>
Content-Type: multipart/related; boundary="000000000000fa376805ca998884"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/T72EBRdNpDmhLG2bMMC3wLM4sdw>
Subject: Re: [Pce] draft-dhodylee-pce-pcep-ls next steps!
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 28 Aug 2021 07:27:49 -0000

Perfect!

Thanks

Gyan
On Fri, Aug 27, 2021 at 8:01 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> -22 captures it. Thanks,
>
> Adrian
>
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* 27 August 2021 06:52
> *To:* adrian@olddog.co.uk
> *Cc:* Dhruv Dhody <dd@dhruvdhody.com>om>; draft-dhodylee-pce-pcep-ls@ietf.org;
> pce@ietf.org; pce-chairs <pce-chairs@ietf.org>
> *Subject:* Re: draft-dhodylee-pce-pcep-ls next steps!
>
>
>
>
>
> Hi Adrian
>
>
>
> Agreed.  We will make it more clear.
>
>
>
> Many Thanks!
>
>
>
> Gyan
>
>
>
> On Wed, Aug 25, 2021 at 10:30 AM Adrian Farrel <adrian@olddog.co.uk>
> wrote:
>
> Yes, thanks, Gyan.
>
>
>
> I think you have captured it all, although some of the behaviours are
> “hidden” in assumptions in the text.
>
>
>
> That is:
>
>
>
>    - A PCEP speaker that offers this feature to its peer that does not
>    support or does not wish to support the feature will not receive indication
>    of support in the Open message, and so is expected to not use the feature.
>
>
>
>    - A PCEP speaker that receives any of the objects that are part of the
>    feature when use of the feature has not been agreed, will <do something> as
>    described in <reference>.
>
>
>
> Of course, this is “business as usual” but the reviewer of the text will
> not necessarily know this.
>
>
>
> Cheers,
>
> Adrian
>
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* 25 August 2021 05:44
> *To:* adrian@olddog.co.uk
> *Cc:* Dhruv Dhody <dd@dhruvdhody.com>om>; draft-dhodylee-pce-pcep-ls@ietf.org;
> pce@ietf.org; pce-chairs <pce-chairs@ietf.org>
> *Subject:* Re: draft-dhodylee-pce-pcep-ls next steps!
>
>
>
> Hi Adrian
>
>
>
>
>
> See section 1.1 should have answers to your questions related to the
> experimental draft.
>
>
>
>
> https://www.ietf.org/archive/id/draft-dhodylee-pce-pcep-ls-21.html#section-1.1
>
>
>
>
> Kind Regards
>
>
>
> Gyan
>
> On Sun, Jul 18, 2021 at 2:40 PM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> Hi Gyan,
>
>
>
> I am very much in favour of positioning this work as Experimental.
>
>
>
> It is important (as with all IETF Experiments) to capture:
>
> -          What stops this extension “escaping" in the Internet?
>
> -          What stops this experiment clashing with other work or harming
> deployed equipment?
>
> -          How will you judge the success or failure of the experiment,
> and when?
>
> -          What follow-up to the experiment do you propose?
>
>
>
> Best,
>
> Adrian
>
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* 05 July 2021 07:43
> *To:* Adrian Farrel <adrian@olddog.co.uk>uk>; Dhruv Dhody <dd@dhruvdhody.com>om>;
> draft-dhodylee-pce-pcep-ls@ietf.org; pce-chairs <pce-chairs@ietf.org>rg>;
> pce@ietf.org
> *Subject:* draft-dhodylee-pce-pcep-ls next steps!
>
>
>
>
>
> Dear PCE WG,
>
>
>
> We presented the PCEP-LS [1] I-D [2] in the IETF 110 with a quick recap
> and a summary of past discussions. Some new scenarios such as PCECC, H-PCE
> were highlighted where the PCEP session could be reused.
>
>
>
> This is an experimental I-D with the aim to progress research and
> development efforts. This work is not a replacement for any of the existing
> mechanisms. There are specific scenarios highlighted where the reuse of
> PCEP sessions for this information is deemed useful. To make progress, it
> may not be useful to rehash the beauty context between everyone's favorite
> protocol :). What would be useful would be - finding out if there is still
> interest in this experimental work by some in the WG; are there strong
> technical objections for the experiment in its limited scope etc...
>
>
>
> As a next step, it would be good to define the scope of the experiments
> and expected output especially targeting the scalability concerns as well
> as impact in other protocols and the network, etc.
>
>
>
> From the last query on this draft March 18th we received positive feedback
> from Aijun Wang with China Telecom mentioned that as a telco are interest
> in deploying in their network PCEP-LS once the Huawei implementation is
> ready.  Aijun pointed out in the thread that using this draft simplifies
> the implementation of SDN controller.  One question asked by Aijun was
> related to section 9.2.1 LS Capability TLV R=1 remote allowed meaning
> hybrid mode to provide flexibility for operators not yet using SDN
> (SDN-like) SBI.  For any operators already using PCEP as SDN (SDN-like)
> SBI, a direct PCEP session already exist between all the nodes in the
> network and the PCE which would be the PCECV SDN scenario in which case the
> R flag in the open message is set to 0.
>
>
>
> We also received positive feedback from Peter Park with telco KT regarding
> interest in PCEP-LS.
>
>
>
> We also had feedback from Bin as they have implemented PCEP and have
> interest in this experimental implementation of this work.
>
>
>
> I would like to poll the WG again for interest in progressing research and
> development efforts of this draft as experimental.
>
>
>
> As stated in the last WG poll, I would like get feedback from the WG on
> scope of experiments especially related to scalability concerns and impact
> to other protocols on the network.
>
>
>
> Thanks!
>
> Gyan (on behalf of co-authors)
>
>
>
> [1]
> https://datatracker.ietf.org/meeting/110/materials/slides-110-pce-42-pcep-ls-00.pdf
>
> [2] https://datatracker.ietf.org/doc/draft-dhodylee-pce-pcep-ls/
>
> ==
>
>
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*