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

윤빈영 <> Thu, 01 April 2021 05:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 044433A40D6 for <>; Wed, 31 Mar 2021 22:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5iNK8EfAwBpt for <>; Wed, 31 Mar 2021 22:00:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DA6C83A40D1 for <>; Wed, 31 Mar 2021 22:00:03 -0700 (PDT)
Received: from unknown (HELO ( by with ESMTP; 1 Apr 2021 14:00:00 +0900
Received: from [] (HELO ([]) by with SMTP id fb861a0a60655351; Thu, 01 Apr 2021 14:00:01 +0900
DKIM-Signature: a=rsa-sha256; b=uosPY9PHlfqK3FbGqttGb3jtTkhmVgZU9UJR9mHjUwwEtsDvotZdFATUqbttzt/5ekmW0AxOW5 d5eTUvOLU4KeYgAIuYnsn72th7EY8VHvYr25HhGenf91mt1WW6pB1hzoNmGnaT+1y1601wk7a9xx qyC3+avapMH82M6BemZogC+xls0TumJkCkIFmQDG/Y3guHp4j4jFYxvVLgV9mUcEjXOB2AELY1Ws 1XHBU7v+2WM6V89IvEKtyUB09OAqit4Bc/5dOYAbCfS3EdOmyBXmvQelrlmaByq83+pft9hYvnAb gMO/OCF1b3LjwdGv0HYRXXDdQt9uK8sSo6llxPqA==; c=relaxed/relaxed; s=selector;; v=1; bh=g7L7L2HR/JLrd+2kg8fmf2YPDgoUZF4UhxwhCQ1marI=; h=From:To:Subject:Message-ID;
Dooray-Meta-Signature: 4OdxcaVK4/8vimmmFWsy2tEpY6Zbamy5sKr8Pn8p6Yfr79s2oMRxk 6CJfUxmwrfx6s915o7W1VucUCd+W2Cmmzb1Yz6hTpO6WkJGj6mVBaiigzlMafiLUfPLuVCEGghQE GTiTwjLlSnXiYZlhH/xfLZraw9UxEloN/sVlXUDIrm8EFwGm+PyyzFn5Y3wOIxmP9DNJG3lGtN2L vnC2MjCjPSLxKOV2iFhINeac+i9+XOg+kjelb3zJouvP7C4v1j5z+3M2u7qgRe8+G5UPfCl1jNHI yvBgx8f9WLVzggv29fPNInHNuvQQVXdDnlIbsFW1o0v1cOh9SPDnizIzjTYmtokpSKKR80KupXMF ODf9II=
Received: from [] (HELO ([]) by with SMTP id 93afad3f6065534f; Thu, 01 Apr 2021 13:59:59 +0900
From: =?UTF-8?B?7Jyk67mI7JiB?= <>
To: Gyan Mishra <>,,, Dhruv Dhody <>, Adrian Farrel <>
Message-ID: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_40115_1361533573.1617253198541"
X-Dsn-Request: true
X-Dooray-Agent: mail-api
X-Dooray-Mail-Id: 2977527393237636649
Importance: Normal
X-Priority: Normal
X-MSMail-Priority: Normal
Date: Thu, 01 Apr 2021 13:59:59 +0900 (KST)
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: Thu, 01 Apr 2021 05:00:09 -0000

Hi Gyan,

We have implemented PCEP in the past.&nbsp;
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.


From:&nbsp;Gyan Mishra &lt;;  Sent: Thursday, March 18, 2021 11:36 AM To:;; Dhruv Dhody &lt;;; Adrian Farrel &lt;; 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.&nbsp;

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...&nbsp;

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. &nbsp;&nbsp;

Gyan (on behalf of co-authors)

Gyan Mishra
Network Solutions Architect&nbsp;
M 301 502-1347