Re: [Pce] PCE WG LC for draft-ietf-pce-pcep-extension-for-pce-controller

Aijun Wang <wangaijun@tsinghua.org.cn> Fri, 14 August 2020 09:42 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1A03A0E75 for <pce@ietfa.amsl.com>; Fri, 14 Aug 2020 02:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWfOKvozssfb for <pce@ietfa.amsl.com>; Fri, 14 Aug 2020 02:42:02 -0700 (PDT)
Received: from mail-m127101.qiye.163.com (mail-m127101.qiye.163.com [115.236.127.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BBA43A0E74 for <pce@ietf.org>; Fri, 14 Aug 2020 02:42:00 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown [219.142.69.75]) by mail-m127101.qiye.163.com (Hmail) with ESMTPA id AFECA45394; Fri, 14 Aug 2020 17:41:53 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: julien.meuric@orange.com, pce@ietf.org
References: <17685_1596644315_5F2ADBDB_17685_395_1_04e4ec71-6fdd-2f8b-e094-66c7f8cf5997@orange.com>
In-Reply-To: <17685_1596644315_5F2ADBDB_17685_395_1_04e4ec71-6fdd-2f8b-e094-66c7f8cf5997@orange.com>
Date: Fri, 14 Aug 2020 17:41:52 +0800
Message-ID: <004b01d6721f$243fc540$6cbf4fc0$@tsinghua.org.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01D67262.326464D0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHX+X3Kir3KHNv+Zitu0mg2QgWnsKkz31cQ
Content-Language: zh-cn
X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgYFAkeWUFZS1VLWVdZKFlBSkxLS0o3V1ktWUFJV1 kPCRoVCBIfWUFZTxkZGUJOSUoaT0tLVkpOQkxIQkNKSkhDQ09VEwETFhoSFyQUDg9ZV1kWGg8SFR 0UWUFZT0tIVUpKS09LQ1VKS0tZBg++
X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6ORQ6FCo4GT8eEjoTMRQ*GDEY EwwwChJVSlVKTkJMSEJDSkpPT0tCVTMWGhIXVQwaFRwaEhEOFTsPCBIVHBMOGlUUCRxVGBVFWVdZ EgtZQVlJSkJVSk9JVU1CVUxOWVdZCAFZQUpOTE9MNwY+
X-HM-Tid: 0a73ec58de019865kuuuafeca45394
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/uKzHWugUsanneB-A2HbRxaulGl8>
Subject: Re: [Pce] PCE WG LC for draft-ietf-pce-pcep-extension-for-pce-controller
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2020 09:42:06 -0000

Hi,Dhruv, Julien and authors of this draft:

 

I reviewed this draft and had the following comments for its WG LC:

1. Generally speaking, I support the direction that stated also in the draft
as "A PCE-based central controller (PCECC) can simplify the processing of a
distributed control plane by blending it with elements of SDN and

   without necessarily completely replacing it."

2. This draft states it focuses on LSP Path central control, but I think the
procedures described in this draft is common to other CCI object(which may
be defined in other documents). So would it be better to generalize the
procedures? The specific part for other path type may be only the CCI
objects. This can facilitate the extension of PCECC procedure in other
scenario.

3. Section-5.5.1of this draft
<https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controlle
r-06#section-5.5.1>  describes the “Basic PCECC LSP Setup”, which is based
on the LSP delegation mode. But for LSP delegate mode, the LSP must exist
beforehand, which is constructed via the distributed protocol(RSVP etc.). In
such scenario, is it necessary to allocate the Label via the PCE?

4. I think the most useful scenario for PCECC should be based on “PCE
Initiate” message, which is used to initiate one new path from the PCE,
together with the label allocation.

5. Similar consideration is for the “PCC allocation label”. What the
reason to let the PCC allocate such label? Why can’t PCE allocate such
information for each PCC from its appointed label space?

6. For definition of CCI object, will it simplify the overall procedures if
the CCI object for MPLS label includes both the IN and OUT label together?

 

 

Best Regards

 

Aijun Wang

China Telecom

 

 

 

 

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
julien.meuric@orange.com
Sent: Thursday, August 6, 2020 12:19 AM
To: pce@ietf.org
Subject: [Pce] PCE WG LC for
draft-ietf-pce-pcep-extension-for-pce-controller

 

Hi all,

 

This message initiates a 3-week WG Last Call on
draft-ietf-pce-pcep-extension-for-pce-controller-06. Please review and share
your feedback, whatever it is, using the PCE mailing list.

This LC will end on Wednesday August 26, 11:59pm (any timezone).

 

Please note that this I-D is related to

draft-zhao-pce-pcep-extension-pce-controller-sr which is already in our WG
adoption queue.

 

Thanks,

 

Dhruv & Julien

 

 

____________________________________________________________________________
_____________________________________________

 

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
exploites ou copies sans autorisation. Si vous avez recu ce message par
erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les
pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.

 

This message and its attachments may contain confidential or privileged
information that may be protected by law; they should not be distributed,
used or copied without authorisation.

If you have received this email in error, please notify the sender and
delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.

Thank you.

 

_______________________________________________

Pce mailing list

 <mailto:Pce@ietf.org> Pce@ietf.org

 <https://www.ietf.org/mailman/listinfo/pce>
https://www.ietf.org/mailman/listinfo/pce