Re: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with COMMENT)

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Fri, 26 February 2021 03:36 UTC

Return-Path: <pengshuping@huawei.com>
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 5EF353A046B; Thu, 25 Feb 2021 19:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 sgaoAb1vgbdX; Thu, 25 Feb 2021 19:36:33 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 255AE3A03FA; Thu, 25 Feb 2021 19:36:33 -0800 (PST)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DmwFf35dQz67sgC; Fri, 26 Feb 2021 11:32:22 +0800 (CST)
Received: from fraeml702-chm.china.huawei.com (10.206.15.51) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Fri, 26 Feb 2021 04:36:27 +0100
Received: from DGGEML401-HUB.china.huawei.com (10.3.17.32) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.2106.2 via Frontend Transport; Fri, 26 Feb 2021 04:36:27 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.50]) by DGGEML401-HUB.china.huawei.com ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0509.000; Fri, 26 Feb 2021 11:36:24 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org" <draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org>, "pce-chairs@ietf.org" <pce-chairs@ietf.org>, "pce@ietf.org" <pce@ietf.org>, Julien Meuric <julien.meuric@orange.com>
Thread-Topic: Roman Danyliw's No Objection on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with COMMENT)
Thread-Index: AQHXCt8AdkdCsOTYeESE5GwrQjBxc6ppyM4A
Date: Fri, 26 Feb 2021 03:36:24 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE19938F25@DGGEML532-MBX.china.huawei.com>
References: <161419307324.26402.15121790675645853920@ietfa.amsl.com>
In-Reply-To: <161419307324.26402.15121790675645853920@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.243.114]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/h6arFBVzDD2oUhjr-xPbNHwKqcU>
Subject: Re: [Pce] Roman Danyliw's No Objection on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with COMMENT)
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, 26 Feb 2021 03:36:38 -0000

Hi Roman, 

Thank you for your comments! Please find the diff and the responses in line below. Thank you!

Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-pcep-extension-for-pce-controller-12&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-pcep-extension-for-pce-controller-13.txt


-----Original Message-----
From: Roman Danyliw via Datatracker [mailto:noreply@ietf.org] 
Sent: Thursday, February 25, 2021 2:58 AM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org; pce-chairs@ietf.org; pce@ietf.org; Julien Meuric <julien.meuric@orange.com>; julien.meuric@orange.com
Subject: Roman Danyliw's No Objection on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with COMMENT)

Roman Danyliw has entered the following ballot position for
draft-ietf-pce-pcep-extension-for-pce-controller-12: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Yaron Sheffer for the SECDIR review and the updates made as a result to improve the Security Considerations.  I endorse the revised text that minimally RECOMMENDs the use of “mutually-authenticated and encrypted sessions.”  My question is why can’t we go even further and require (use MUST) this crucial provisioning channel always be protected.  When would we NOT want to use TLS?  I appreciate that mandating the use of security primitives in routing is challenging due to a long tail of legacy investment.  However, this extension seems like a near "green field" focused on a modern, SDN architecture which seems unlikely to have less capable legacy elements.


Shuping> This is a case of blending elements of SDN into the existing distributed control plane and devices without necessarily completely replacing it and enhancing PCEP as an SBI. It is true that the central control instructions allows greater control to label allocation but it is not far from what is already done for segment routing label stack (which uses 'RECOMMEND').

Best Regards, 
Shuping