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

Gyan Mishra <hayabusagsm@gmail.com> Thu, 01 April 2021 13:26 UTC

MIME-Version: 1.0
References: <mmdxdcyukze1.mmdxdcyqjg6i.g1@dooray.com>
In-Reply-To: <mmdxdcyukze1.mmdxdcyqjg6i.g1@dooray.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 01 Apr 2021 09:25:47 -0400
Message-ID: <CABNhwV3wCRF87qn=nD4E4XUOmrJFQwdepqupjipFAEoKD8mXqA@mail.gmail.com>
To: 윤빈영 <byyun@etri.re.kr>
Cc: Adrian Farrel <adrian@olddog.co.uk>, Dhruv Dhody <dd@dhruvdhody.com>, draft-dhodylee-pce-pcep-ls@ietf.org, pce@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000359b005bee92ca9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/qEeoryx0MOQPAxyhmoFupo5-znY>
Subject: Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn
Precedence: list

Thank you Bin for your sharing your positive experience with PCEP-LS in the
field and continued experimenting in scenarios such as H-PCE and PCECC.

Thank you for supporting this experimental draft and interest in
progressing.


Kind Regards

Gyan


On Thu, Apr 1, 2021 at 1:00 AM 윤빈영 <byyun@etri.re.kr> wrote:

> Hi Gyan,
>
>
> We have implemented PCEP in the past.
>
> This experimental upgrade of PCEP to enable direct TE updates to PCE is
> worth to try and we'd be interested in the implementation of this work.
>
>
> Regards,
>
> Bin
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* Thursday, March 18, 2021 11:36 AM
> *To:* pce@ietf.org; draft-dhodylee-pce-pcep-ls@ietf.org; Dhruv Dhody <
> dd@dhruvdhody.com>; Adrian Farrel <adrian@olddog.co.uk>
> *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 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] draft-dhodylee-pce-pcep-te-data-extn Gyan Mishra
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn 윤빈영
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn Gyan Mishra
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn 박춘걸(Naas Transformation 팀)
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn Aijun Wang
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn Gyan Mishra
Re: [Pce] draft-dhodylee-pce-pcep-te-data-extn Gyan Mishra