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

Leeyoung <leeyoung@huawei.com> Wed, 20 June 2018 22:43 UTC

Return-Path: <leeyoung@huawei.com>
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 A39A9130E2F; Wed, 20 Jun 2018 15:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 8qQ1MwNxdjkf; Wed, 20 Jun 2018 15:43:17 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 C489C1277BB; Wed, 20 Jun 2018 15:43:16 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A24EDD459422D; Wed, 20 Jun 2018 23:43:12 +0100 (IST)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 20 Jun 2018 23:43:14 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.141]) by SJCEML701-CHM.china.huawei.com ([169.254.3.24]) with mapi id 14.03.0382.000; Wed, 20 Jun 2018 15:43:11 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
CC: "draft-ietf-teas-actn-info-model@ietf.org" <draft-ietf-teas-actn-info-model@ietf.org>, Vishnu Beeram <vbeeram@juniper.net>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "vbeeram@juniper.net" <vbeeram@juniper.net>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Benjamin Kaduk's No Objection on draft-ietf-teas-actn-info-model-09: (with COMMENT)
Thread-Index: AQHUCNki2Tn9sLEusUq4Ua1QxsvLhqRps6rA
Date: Wed, 20 Jun 2018 22:43:10 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D01A803@sjceml521-mbx.china.huawei.com>
References: <152952816841.28616.13487599041543688657.idtracker@ietfa.amsl.com>
In-Reply-To: <152952816841.28616.13487599041543688657.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.218.137.166]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E173D01A803sjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/luGaU7Lhb9qfwT0V57iNh3Fo81Q>
Subject: Re: [Teas] Benjamin Kaduk's No Objection on draft-ietf-teas-actn-info-model-09: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 20 Jun 2018 22:43:21 -0000

Hi Benjamin,



Thanks for proving valuable comments and suggestions.



Please see inline for my response.



Thanks.

Young



-----Original Message-----
From: Benjamin Kaduk [mailto:kaduk@mit.edu]
Sent: Wednesday, June 20, 2018 3:56 PM
To: The IESG <iesg@ietf.org>;
Cc: draft-ietf-teas-actn-info-model@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-info-model-09: (with COMMENT)



Benjamin Kaduk has entered the following ballot position for

draft-ietf-teas-actn-info-model-09: 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-info-model/







----------------------------------------------------------------------

COMMENT:

----------------------------------------------------------------------



I echo the comments questioning the archival value for publishing a document like this.

I think it's a good intermediate point to have, including the security considerations text (thank you for the quick update after the secdir review!), but am unsure what portion(s) of it could not be easily folded into successor documents.



YL>> Please see my comment to Ben on the archival value of this document.



Section 2



  This section provides an ACTN common interface information model to

   describe in terms of primitives, objects, their properties

   (represented as attributes), their relationships, and the resources

   for the service applications needed in the ACTN context.



nit: The grammar here is a bit odd -- as-is, it says we have a model "to describe in terms of [a list of things]", but don't say what is being described.  I'm not entirely sure what the intended text would be, though.



YL>> I agree. I would change as follows:



NEW: This section provides an ACTN common interface information model to

   describe primitives, objects, their properties

   (represented as attributes), their relationships, and the resources

   for the service applications needed in the ACTN context.





Section 3.2, 3.4



Do I understand correctly that Modify is for CNC-to-MDSC commmunication and Update is for MDSC-to-CNC communication?  Perhaps this could be made more explicit.



YL>> Yes, your understanding is correct. We will add explicit text that says: Modify is for CNC-to-MDSC communication in Section 3.2 and Update is for MDSC-to-CNC communication in Section 3.4.



Section 5.7.2



      [...] For example, permission

      the correct selection from the network of the destination related

      to the indicated VNF It is e.g. the case of VM migration among

      data center and CNC can enforce specific policy that can permit

      MDSC/PNC to calculate the correct path for the connectivity

      supporting the data center interconnection required by

      application.



There seems to be an editing error around "indicated VNF It is e.g.", maybe just a missing full stop and commas around "e.g."?



YL>> Yes, there is an editing error here.

OLD: For example, permission

      the correct selection from the network of the destination related

      to the indicated VNF It is e.g. the case of VM migration among

      data center and CNC can enforce specific policy that can permit

      MDSC/PNC to calculate the correct path for the connectivity

      supporting the data center interconnection required by

      application.



NEW: For example, CNC can enforce client-specific preferences, e.g.,

      selection of a destination data center from the set of candidate data

      centers based on some criteria in the context of VM migration.

      MSDC/PNC should then provide the data center interconnection that

      supports the client-specific preference.



Section 9



   The ACTN information model does not directly introduce security

   issues. Rather, it defines a set of interfaces for traffic



I would hope that no product of the IETF directly introduces security

*issues* (problems)!  Maybe "is not directly relevant when considering potential security issues" is some better wordsmithing.



YL>> Agree. Will change the sentence as you suggest.



   Implementations of the ACTN framework will have distributed

   functional components that will exchange this information model.



nit: Perhaps this is overly pedantic, but are they exchanging this information model, or a concrete instantiation that adheres to this model?



YL>> Agree. How about:



NEW:

   Implementations of the ACTN framework will have distributed

   functional components that will exchange a concrete instantiation

   that adheres to this information model.