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

Adrian Farrel <adrian@olddog.co.uk> Sun, 18 July 2021 18:40 UTC

Return-Path: <adrian@olddog.co.uk>
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 296A43A16E7; Sun, 18 Jul 2021 11:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.884
X-Spam-Level:
X-Spam-Status: No, score=-1.884 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5rWyRtmJrFz7; Sun, 18 Jul 2021 11:40:24 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 588023A16E4; Sun, 18 Jul 2021 11:40:21 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 16IIeGhm004932; Sun, 18 Jul 2021 19:40:16 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id ECD3B4604B; Sun, 18 Jul 2021 19:40:15 +0100 (BST)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CC46B4604A; Sun, 18 Jul 2021 19:40:15 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS; Sun, 18 Jul 2021 19:40:15 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.103.107]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 16IIeD4E011280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 18 Jul 2021 19:40:14 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Gyan Mishra'" <hayabusagsm@gmail.com>, "'Dhruv Dhody'" <dd@dhruvdhody.com>, <draft-dhodylee-pce-pcep-ls@ietf.org>, "'pce-chairs'" <pce-chairs@ietf.org>, <pce@ietf.org>
References: <CABNhwV1hby7ap3DWQzxB2aV+ggVCeuDL89SNfaMA6RH0XiC8sQ@mail.gmail.com>
In-Reply-To: <CABNhwV1hby7ap3DWQzxB2aV+ggVCeuDL89SNfaMA6RH0XiC8sQ@mail.gmail.com>
Date: Sun, 18 Jul 2021 19:40:12 +0100
Organization: Old Dog Consulting
Message-ID: <064a01d77c04$59272510$0b756f30$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_064B_01D77C0C.BAEC9E80"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKHa/UUVb+o28IZeZd32h3lqa/20qnpLG9A
Content-Language: en-gb
X-Originating-IP: 84.93.103.107
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2034-8.6.0.1017-26292.002
X-TM-AS-Result: No--20.362-10.0-31-10
X-imss-scan-details: No--20.362-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1017-26292.002
X-TMASE-Result: 10--20.362400-10.000000
X-TMASE-MatchedRID: CxmI61mtwh/xIbpQ8BhdbGyGdbpKa3ZsfkuZtv/FS5q9Z2yPmkEoTDlw dnKldJgi/b1NZcW9aJMsZfAFu40smkRSot6s7kwJh+OEdRz72Lwyi3XhzUIbyN5xxKd6VyUzaxZ lX1gwMFuLUwmkRA7At8YQrmaGCURxTdxlgyoTjki5UUv022NJAhmyTBaqiJvcNjzm7ovKQAbupp zaQqavCLsjlp4pVWOeA03qZSw4NIIpsn9kdROMaZHXKSSl+ScK/LeCo0NaJubjW2KX8PkX4Y6xo 0c4N5dQUAsHThNBbWPzue7fWLKKraMLmp3wjW4q8/dMbHimq7EKJM4okvH5XnzWVdfOL2uZApEm 6XacmPKfhHQDFoWdjC6124x090IjwfZlJsUAV2Hl2CNM+DA49EyQ5fRSh265X/yUapWy0lftZ4D ZVrT18glNTOh1ZlxvscNiTFx6moqzC657f0No8smR5yDJkPg4EwOwAhdI3QM1ho4h8XMwoOjYpj NWETpmxL/4IjKi31E82HMFzuq3rJ4PKMTQaQGUkiSxx29igC1boh0Au8fxU+oo2sUZ26HG+h8V1 Xga7jNPWA06O6p8u+CZGWnDN1tgmo2ZG/E7i3NBsDU0AwZiuAPfn+3SI1uEbd9WaXdyUN5N72Cv uDcMq3yYThRrCy7BKDX7UR/i5dqyQNoUnxiQNO0/o+/4D7Dzd7mNUbprq0q15eNIExieaYvbgnl NqzfoeG/tRkLoURcMd03S1VKXzMj/emqUpI+sF9jfTqcDdugh9SbkbLxu9P67wpKrIJNBK6HQs3 v+pqNomzU6Vs5Rj3JXuAX1c1SNjjCvOetwLqc0i6L0DcfAAF5MyqobPoe0hXp6MC9PVQbmVuTu1 vVZhCiNG0gFH6Rw4kYXbobxJbKl/MtrTwS4UKuCuY3sshN4knrbKvE4YL19rV47XdZehgWilrK0 Uxgqk++misrL66g=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/hjSqkQUyFpLy48UpU5uoVW0Xp74>
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 18:40:30 -0000

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/

==

 

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

Gyan Mishra

Network Solutions Architect 

Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> 

M 301 502-1347

 

-- 

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

Gyan Mishra

Network Solutions Architect 

Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> 

M 301 502-1347