Re: [Teas] Benjamin Kaduk's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Thu, 24 May 2018 20:20 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF6212E8D1; Thu, 24 May 2018 13:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 QAed8PYfiVfr; Thu, 24 May 2018 13:20:08 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (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 89195127735; Thu, 24 May 2018 13:20:08 -0700 (PDT)
X-AuditID: 12074425-29fff70000001eca-47-5b071e774093
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 83.0D.07882.77E170B5; Thu, 24 May 2018 16:20:07 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id w4OKK5Ow018944; Thu, 24 May 2018 16:20:05 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w4OKJxjP031594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 May 2018 16:20:02 -0400
Date: Thu, 24 May 2018 15:19:59 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Leeyoung <leeyoung@huawei.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-teas-actn-framework@ietf.org" <draft-ietf-teas-actn-framework@ietf.org>, Vishnu Beeram <vbeeram@juniper.net>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "teas@ietf.org" <teas@ietf.org>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Message-ID: <20180524201959.GN32807@kduck.kaduk.org>
References: <152709164646.27121.4769234793573944203.idtracker@ietfa.amsl.com> <7AEB3D6833318045B4AE71C2C87E8E173D001C01@sjceml521-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E173D001C01@sjceml521-mbx.china.huawei.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEKsWRmVeSWpSXmKPExsUixCmqrFsuxx5t8HC3isW05cuYLK5cusxi MePPRGaLafNcLZrm7mKyaP2xg8ViwZqZzA7sHr++XmXzaDnyltVjyZKfTB7Xm66yB7BEcdmk pOZklqUW6dslcGW8u7+VtWCdZsWaD3vZGhinyXcxcnBICJhITPrG1sXIxSEksJhJYsurf4wQ zkZGiae3djNDOFeZJH5sP8bUxcjJwSKgKrHn4QMwm01ARaKh+zIziC0ioCQxbcccsFHMAieZ JDYvfQZWJCyQKLHmymxWEJsXaN3b53NZIKbOZJTYfus6E0RCUOLkzCcsIDazgLrEn3mXmEHu YxaQllj+jwMiLC/RvHU22DJOgTCJP98msYHYogLKEnv7DrFPYBSchWTSLCSTZiFMmoVk0gJG llWMsim5Vbq5iZk5xanJusXJiXl5qUW6Fnq5mSV6qSmlmxhB0cHuorqDcc5fr0OMAhyMSjy8 Gw6wRQuxJpYVV+YeYpTkYFIS5V37DyjEl5SfUpmRWJwRX1Sak1p8iFGCg1lJhLf7F1CONyWx siq1KB8mJc3BoiTOm7OIMVpIID2xJDU7NbUgtQgmK8PBoSTB6ybLHi0kWJSanlqRlplTgpBm 4uAEGc4DNLwDpIa3uCAxtzgzHSJ/ilGXo+P9lB5mIZa8/LxUKXFeK5AiAZCijNI8uDmgpCaR vb/mFaM40FvCvOkgVTzAhAg36RXQEiagJReXM4MsKUlESEk1MLKEnJmxdm3tuXunKt9+nHRz xYOn6cnFi7uvF15K2xBodS6t0OxL1dacyAMPPmosjlP5MXfOod5Fv+otLjzwiqmZxZVVtENb 7HdhGG+kgMWXa6fOuU7ZEd8fydmSdC3zwdEQT4YbRYku174dWmImL8RhPjvxqt4W82c/pM4v aQ6TWOKm/skyK1CJpTgj0VCLuag4EQBEvaQcRQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/a9wspRbYYtzD-BhNg2mUcsaTX7k>
Subject: Re: [Teas] Benjamin Kaduk's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 20:20:12 -0000

On Wed, May 23, 2018 at 11:02:14PM +0000, Leeyoung wrote:
> Hi Benjamin,
> 
> 
> 
> Thanks for your kind words for the document and providing good comments and the nits to be fixed. Please see inline for our response. Please also let us know if our response is good with you.
> 
> 
> 
> Best regards,
> 
> Young and Daniele
> 
> 
> 
> -----Original Message-----
> From: Benjamin Kaduk [mailto:kaduk@mit.edu]
> Sent: Wednesday, May 23, 2018 11:07 AM
> To: The IESG <iesg@ietf.org>;
> Cc: draft-ietf-teas-actn-framework@ietf.org; Vishnu Beeram <vbeeram@juniper.net>;; teas-chairs@ietf.org; vbeeram@juniper.net; teas@ietf.org
> Subject: Benjamin Kaduk's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)
> 
> 
> 
> Benjamin Kaduk has entered the following ballot position for
> 
> draft-ietf-teas-actn-framework-14: 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-teas-actn-framework/
> 
> 
> 
> 
> 
> 
> 
> ----------------------------------------------------------------------
> 
> COMMENT:
> 
> ----------------------------------------------------------------------
> 
> 
> 
> Thanks for the clear and easy-to-follow document!
> 
> 
> 
> I do have a few minor comments, below.
> 
> 
> 
> 
> 
> Section 3
> 
> 
> 
> Please expand OSS and NMS on first usage.
> 
> 
> 
> DL&YL>>  Thanks. We will expand these acronyms on their firs usage: OSS: Operations Support System; NMS: Network Management System
> 
> 
> 
> Section 3.2
> 
> 
> 
>    [...] The two functions of the MDSC,
> 
>    namely, multi-domain coordination and virtualization/abstraction are
> 
>    referred to as network-related functions while the other two
> 
>    functions, namely, customer mapping/translation and virtual service
> 
>    coordination are referred to as service-related functions.
> 
> 
> 
> Starting out with "The two" implies that there are no others, which is contradicted by "the other two" later.  So, I'd suggest just starting with "Two functions of the MDSC ...".
> 
> 
> 
> DL&YL>>  Agree. Will delete "The" from the sentence.
> 
> 
> 
> Section 3.3
> 
> 
> 
> Please expand NBI (which appears to only be used once in the document).
> 
> 
> 
> DL&YL>>  Agree. We will expand it. NBI: Northbound Interface
> 
> 
> 
> 
> 
> Section 5.3.2
> 
> 
> 
> It seems pretty likely that allowing repeated path computation requests (with different parameters) would allow a malicious MDSC to learn a fair amount of information about the topology that the PNC is attempting to abstract away.  This is probably not a huge deal, though.
> 
> 
> 
> DL&YL>>  Yes there could be such possibility. But in most cases, the MDSC and PNCs are under one operator’s control, this may be a huge deal as you pointed out.
> 
> 
> 
> 
> 
> Section 8.3
> 
> 
> 
>    A key objective of the MDSC is to support the customer's expression
> 
>    of the application connectivity request via its CNC as set of
> 
>    desired business needs, therefore policy will play an important
> 
>    role.
> 
> 
> 
> nit: "as a set of"
> 
> 
> 
> DL&YL>>  Thanks, Will change as you suggested.
> 
> 
> 
>    Once authorized, the virtual network service will be instantiated
> 
>    via the CNC-MDSC Interface (CMI), it will reflect the customer
> 
>    application and connectivity requirements, and specific service
> 
>    transport needs.
> 
> 
> 
> nit: this is a comma splice; I'd change the comma before "it" to either a semicolon or a period.  (There's a similar issue in the following sentence, too.)
> 
> 
> 
> DL&YL>>  Yes. We would put semicolon before “it”.
> 
> 
> 
> We will fix the next sentence as follows:
> 
> 
> 
> OLD:
> 
> The CNC and the MDSC components will have agreed
> 
>    connectivity end-points, use of these end-points should be defined
> 
>    as a policy expression when setting up or augmenting virtual network
> 
>    services.
> 
> 
> 
> NEW:
> 
> The CNC and the MDSC components will have agreed
> 
>    connectivity end-points; use of these end-points should be defined
> 
>    as a policy expression when setting up or augmenting virtual network
> 
>    services.
> 
> 
> 
> Section 9.2
> 
> 
> 
> Perhaps we should say something about configuring trust anchors for the PKI, e.g., using a smaller set of trusted CAs than in the Web PKI.
> 
> 
> 
> DL&YL>>  That will be helpful. How about adding the following sentence at the end of the first paragraph:
> 
> 
> 
> Trust anchors for the PKI can be configured using a smaller set of trusted Certificate Authorities (CAs) than in the Web PKI.

I think "configured to us a smaller (and potentially
non-intersecting) set" might be better.

Thanks for all the fixups,

Benjamin