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

[Gyan Mishra <[e-mail]>]

Hi Peter

That’s good to hear interest from operators such as yourself in PCEP-LS.
As you deploy PCECC and H-PCE in a multi domain environments you will be
able to reuse the SBI PCEP session for PCEP-LS and then can take full
advantage of some of benefits of PCEP-LS such as synchronization
optimization and incremental updates.

Thank you for sharing your interest in PCEP-LS.

Kind Regards

Gyan

On Thu, Apr 1, 2021 at 9:14 PM 박춘걸(Naas Transformation 팀) <[e-mail]>
wrote:

> 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.
>
>
>
> Regards,
>
> Peter
>
>
>
>
>
> *From:* Gyan Mishra <[e-mail]>
> *Sent:* Thursday, March 18, 2021 11:36 AM
> *To:* [e-mail]; [e-mail]; Dhruv Dhody <
> [e-mail]>; Adrian Farrel <[e-mail]>
> *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.
>
>
>
> 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 [e-mail] <[e-mail]>*
>
> *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.
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [e-mail] <[e-mail]>*



*M 301 502-1347*