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

"박춘걸(Naas Transformation 팀)" <> Fri, 02 April 2021 01:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A88293A2B14; Thu, 1 Apr 2021 18:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QkPI0_TYX3XJ; Thu, 1 Apr 2021 18:14:39 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 051213A2B12; Thu, 1 Apr 2021 18:14:38 -0700 (PDT)
Received: from external ([]) by (1.0) id 1321E6f00474; Fri, 02 Apr 2021 10:14:06 +0900
Received: from ([]) by ([]) with mapi id 14.03.0439.000; Fri, 2 Apr 2021 10:14:06 +0900
From: =?utf-8?B?67CV7LaY6rG4KE5hYXMgVHJhbnNmb3JtYXRpb24g7YyAKQ==?= <>
To: Gyan Mishra <>, "" <>, "" <>, Dhruv Dhody <>, Adrian Farrel <>
Thread-Topic: [Pce] draft-dhodylee-pce-pcep-te-data-extn
Thread-Index: AdcnW2E0X6HXo/VqT9WFHcstfxlNuw==
Date: Fri, 2 Apr 2021 01:14:05 +0000
Message-ID: <64B123AD47B4514BA507B0376760B284017793E65B@MAIL-MBX-05>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_64B123AD47B4514BA507B0376760B284017793E65BMAILMBX05_"
MIME-Version: 1.0
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:14:46 -0000

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


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.