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

Leeyoung <leeyoung@huawei.com> Wed, 23 May 2018 23:10 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 CA07912D86D; Wed, 23 May 2018 16:10:16 -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 MNZNYglWetZh; Wed, 23 May 2018 16:10:14 -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 370D0128896; Wed, 23 May 2018 16:10:14 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 6784CE4A64267; Thu, 24 May 2018 00:10:09 +0100 (IST)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 24 May 2018 00:10:11 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.141]) by SJCEML701-CHM.china.huawei.com ([169.254.3.48]) with mapi id 14.03.0382.000; Wed, 23 May 2018 16:10:08 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Warren Kumari <warren@kumari.net>, The IESG <iesg@ietf.org>
CC: "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>, "vbeeram@juniper.net" <vbeeram@juniper.net>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Warren Kumari's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)
Thread-Index: AQHT8gR/EsEK3P0TH0GEygLJKdBOcqQ98PuQ
Date: Wed, 23 May 2018 23:10:07 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173D001C26@sjceml521-mbx.china.huawei.com>
References: <152701791513.31214.14570535633284371905.idtracker@ietfa.amsl.com>
In-Reply-To: <152701791513.31214.14570535633284371905.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.80.196]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E173D001C26sjceml521mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/au7ZnG-zXdeKWWyLeJzjngKDqcU>
Subject: Re: [Teas] Warren Kumari'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: Wed, 23 May 2018 23:10:17 -0000

Hi Warren,



Thanks for providing good comments for the document. Please see inline for our response to your comments.

Please let us know if our responses are all good to you.



Thanks & Best regards,

Young and Daniele,



-----Original Message-----
From: Warren Kumari [mailto:warren@kumari.net]
Sent: Tuesday, May 22, 2018 2:39 PM
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: Warren Kumari's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)



Warren Kumari 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:

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



I have a few nits to further improve readability:



Section 1:

"Traffic Engineered (TE) networks have a variety of mechanisms to facilitate separation of data plane and control plane" s/facilitate separation/facilitate the separation/ ?



DC&YL>> Yes, agree. We will correct as you suggested.



"This document describes a set of management and control functions used to operate one or more TE networks to construct virtual networks that can be represented to customers" The word "represented" here sounds odd, but I don't really have an alternative -- perhaps just "presented" ? Represented is probably technically correct, but it feels like there should be a more appropriate one...



DC&YL>> We will replace "represented" with "presented".



Section 3.4:

"In addition, some networks may operate a control plane and as such it is not practical for the customer to directly interface with network elements." Can you please clarify that you mean a TE (or similar) control plane -- I believe that *all* networks have some sort of control plane (and so the "some networks"

is false / misleading).



DC&YL>> Here in this sentence, what we were saying is that “some networks may operate a centralized controller, whether it is TE or non-TE, and as such it is also not practical

for the customer to directly interface with network elements. As unclear, and as the first sentence already says this, we think the best is to remove this sentence. Hope that is clearer.