Re: [Pce] Secdir last call review of draft-ietf-pce-wson-rwa-ext-10

Leeyoung <leeyoung@huawei.com> Mon, 21 January 2019 20:16 UTC

Return-Path: <leeyoung@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 5C5CC126BED; Mon, 21 Jan 2019 12:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.201
X-Spam-Level:
X-Spam-Status: No, score=-3.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 z2LK65BOuloV; Mon, 21 Jan 2019 12:16:16 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F417E124408; Mon, 21 Jan 2019 12:16:15 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id DEDF0D3BC1E958F94207; Mon, 21 Jan 2019 20:16:13 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 21 Jan 2019 20:16:13 +0000
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.96]) by SJCEML703-CHM.china.huawei.com ([169.254.5.115]) with mapi id 14.03.0415.000; Mon, 21 Jan 2019 12:16:08 -0800
From: Leeyoung <leeyoung@huawei.com>
To: Watson Ladd <watsonbladd@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "draft-ietf-pce-wson-rwa-ext.all@ietf.org" <draft-ietf-pce-wson-rwa-ext.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Secdir last call review of draft-ietf-pce-wson-rwa-ext-10
Thread-Index: AQHUnAPv3/fqZQlb10mkTsVxPoH3HqW6Ue8w
Date: Mon, 21 Jan 2019 20:16:07 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D0C5201@sjceml521-mbx.china.huawei.com>
References: <154570936991.12911.1627288364179668736@ietfa.amsl.com>
In-Reply-To: <154570936991.12911.1627288364179668736@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.123]
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/p7N0G5bFlFonJ7c4dClI0UniCdE>
Subject: Re: [Pce] Secdir last call review of draft-ietf-pce-wson-rwa-ext-10
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: Mon, 21 Jan 2019 20:16:18 -0000

Hi Watson,

Sorry for the late response to your review.  I thank you for your review of this draft and the result. 

In regards to your question, please see below inline. 

Thanks & Best regards,
Young

-----Original Message-----
From: Watson Ladd [mailto:watsonbladd@gmail.com] 
Sent: Monday, December 24, 2018 9:43 PM
To: secdir@ietf.org
Cc: draft-ietf-pce-wson-rwa-ext.all@ietf.org; pce@ietf.org; ietf@ietf.org
Subject: Secdir last call review of draft-ietf-pce-wson-rwa-ext-10

Reviewer: Watson Ladd
Review result: Ready

Dear all,

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

The summary of the review is READY.

This is a document in an area I know almost nothing about. It appears to be about an internal mechanism for configuring label based routing in an optical network to minimize the number of optical to electrical transitions along the route. I am perhaps a bit confused as to why the PCC would specify the constraints on wavelengths on hops that are not the end ones: if the packets must flow from A to B, shouldn't the PCE be the one to decide how to do that using all the resources available? 

YL>> PCC is a client that would ask some constraints to the PCE so that PCE would filter such constraints in its path computation. The final decision on the path and wavelength assignment is done by the PCE in general case. Hope this answers to your question. 

Merry Christmas!

Sincerely,
Watson Ladd