Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn

Aijun Wang <> Fri, 02 April 2021 01:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2775B3A2B77; Thu, 1 Apr 2021 18:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Status: No, score=-1.907 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.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KjereyYYsvKu; Thu, 1 Apr 2021 18:28:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C3BD83A2B74; Thu, 1 Apr 2021 18:28:36 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown []) by (Hmail) with ESMTPA id ADED01C00C6; Fri, 2 Apr 2021 09:28:31 +0800 (CST)
From: "Aijun Wang" <>
To: =?utf-8?Q?'=EB=B0=95=EC=B6=98=EA=B1=B8=28Naas_Transformation_=ED=8C=80=29'?= <>, "'Gyan Mishra'" <>, <>, <>, "'Dhruv Dhody'" <>, "'Adrian Farrel'" <>
References: <64B123AD47B4514BA507B0376760B284017793E65B@MAIL-MBX-05>
In-Reply-To: <64B123AD47B4514BA507B0376760B284017793E65B@MAIL-MBX-05>
Date: Fri, 2 Apr 2021 09:28:30 +0800
Message-ID: <007a01d7275f$7de97ff0$79bc7fd0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_007B_01D727A2.8C11A1F0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHPgSPGipz4MOTOgloyOQtllg1+Xaqvu36Q
Content-Language: zh-cn
X-HM-Tid: 0a78903231acd993kuwsaded01c00c6
Archived-At: <>
Subject: Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Apr 2021 01:28:43 -0000



Also as a telco, we are expecting the implementation of PCEP-LS, and once it is ready, we will try to deploy it in the network.


Best Regards


Aijun Wang

China Telecom


From: <> On Behalf Of ???(Naas Transformation ?)
Sent: Friday, April 2, 2021 9:14 AM
To: Gyan Mishra <>om>;;; Dhruv Dhody <>om>; Adrian Farrel <>
Subject: Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn


Dear Gyan,


As a telco, we are interested in the upgrade of PCEP.

PCEP and H-PCE scenarios is always being considered as valuable tools for solving our issues in telco’s multi-domain environment.






From: Gyan Mishra < <> > 
Sent: Thursday, March 18, 2021 11:36 AM
To: <> ; <> ; Dhruv Dhody < <> >; Adrian Farrel < <> >
Subject: [Pce] draft-dhodylee-pce-pcep-te-data-extn


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.   



Gyan (on behalf of co-authors)







Gyan Mishra

Network Solutions Architect 

Email <> 

M 301 502-1347





이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을 포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다. 
This E-mail may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. If you receive this email by mistake, please either delete it without reproducing, distributing or retaining copies thereof or notify the sender immediately.