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

Siva Sivabalan <msiva282@gmail.com> Sun, 18 July 2021 12:43 UTC

Return-Path: <msiva282@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 6026E3A1E5B; Sun, 18 Jul 2021 05:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.836
X-Spam-Level:
X-Spam-Status: No, score=-1.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 PEVzdFTRnilP; Sun, 18 Jul 2021 05:43:13 -0700 (PDT)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 A8B6A3A1E5A; Sun, 18 Jul 2021 05:43:12 -0700 (PDT)
Received: by mail-ot1-x334.google.com with SMTP id h24-20020a9d64180000b029036edcf8f9a6so15192497otl.3; Sun, 18 Jul 2021 05:43:12 -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=6tYb2cVVGb/6XHSOUw3TvIVGjHwQvjKtJ3sjy15d1o0=; b=WUZWNFoNIcMoDLtGWbo1HD6p3AXPAKk3Jszzk3KuuRpN6HczwiHm+fV1j1VXsUyjjD UBhGhihFP8c9hZTEVqmFbcmugCDSTWpa4VzIJX8/n5T5jllIH+HekrQH+TUKdIDVsJ1h z/kXiYWA/L36krCVjbqaw98CYq15eQVePVDPL9KaF7sMJtiQbq54TaB5GtzNRxByUqw1 7GMvto/hACGREOh+S6VE/p7ZeZd0EvFoDJRI+U1dWGQNzFkmVMxvD6NqX9UAh1DCLcqJ q5w4+K1aNEZKSB6saRAKDPLyRHNnY+A79iWoVDmkV+etLMOZt7wTO68WKOcGpzrPhvT1 BXVw==
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=6tYb2cVVGb/6XHSOUw3TvIVGjHwQvjKtJ3sjy15d1o0=; b=TenqQI4khFZ0sQz978ZbOiHsPlQEHopEp+uMZDKJJJXYH7AFTKIae2Pnnf3bUu+K7L VCewri9sU+Le4h9JfuYy9Aq+AZlXJ3fg63iTuQwsXHcZxjbO41cXIZzttGWCQzJiwpvR IMkitgSSSQolCKdW7PW77vBNBXyqsSCkBSeFtdToTZJWjk2OkyApJ81LfWQGCfx5UPz6 bVI9zO9gfyUTmxZ9CYiTPqP0xbhhnPJRcbm22UildffGiOmp+nXjc4OdZmIxpR95aksv PI8mX293bqRDBll5N9mpX3++qtE14JnDykEKakgR3elFjnvX/QU5ewQ3s55f+9p+glVY x/ew==
X-Gm-Message-State: AOAM532vuttAoT7peIQUmKrOEuO5nx20CyCVJdpStyf7imjc5Jl0XqWz MHyKd34rdVMWNKeQIxiLH0fgUA/Ih5XIxe3G1C0=
X-Google-Smtp-Source: ABdhPJwmGG7qSzeYjYWnFXgPah0nsucUw4Y/w/7M0ApctZLNYzVFhvuvdV1gRQ0U/IFrGRFPEii5eYiyyOPEKgFCzKo=
X-Received: by 2002:a05:6830:54a:: with SMTP id l10mr15568581otb.194.1626612191434; Sun, 18 Jul 2021 05:43:11 -0700 (PDT)
MIME-Version: 1.0
References: <CABNhwV1hby7ap3DWQzxB2aV+ggVCeuDL89SNfaMA6RH0XiC8sQ@mail.gmail.com>
In-Reply-To: <CABNhwV1hby7ap3DWQzxB2aV+ggVCeuDL89SNfaMA6RH0XiC8sQ@mail.gmail.com>
From: Siva Sivabalan <msiva282@gmail.com>
Date: Sun, 18 Jul 2021 08:43:01 -0400
Message-ID: <CANJFx2SJYNn9uTdR4KxVnAM=rpygJXVniVeeWdwZp+20+5nQrA@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Dhruv Dhody <dd@dhruvdhody.com>, "draft-dhodylee-pce-pcep-ls@ietf.org" <draft-dhodylee-pce-pcep-ls@ietf.org>, pce-chairs <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000db9bbe05c76529f1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/w0Fx2d2qeDyTz9u8F71cGA5MOoA>
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: Sun, 18 Jul 2021 12:43:18 -0000

Hi Gyan,

I support this experimental work. If a router communicates with PCE over
PCEP for path computation purpose, it might as well propagate topology via
PCEP eliminating the need for another protocol for that purpose. The lesser
the number of protocols, the better for simplifying network operation.

Thanks,
Siva


On Mon, Jul 5, 2021 at 2:43 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:

>
> 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/
>
> ==
>
>
> <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*
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>