Re: [Teas] Opsdir last call review of draft-ietf-teas-actn-framework-13

Leeyoung <leeyoung@huawei.com> Mon, 30 April 2018 19:49 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 2B520126D0C; Mon, 30 Apr 2018 12:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.2
X-Spam-Level:
X-Spam-Status: No, score=-3.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, 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 QsTjWMc6mP0X; Mon, 30 Apr 2018 12:49:50 -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 ACE1312420B; Mon, 30 Apr 2018 12:49:50 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 4EB9E9598C386; Mon, 30 Apr 2018 20:49:46 +0100 (IST)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 30 Apr 2018 20:49:48 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.34]) by SJCEML701-CHM.china.huawei.com ([169.254.3.144]) with mapi id 14.03.0382.000; Mon, 30 Apr 2018 12:49:44 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Scott Bradner <sob@sobco.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "draft-ietf-teas-actn-framework.all@ietf.org" <draft-ietf-teas-actn-framework.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, 'Daniele Ceccarelli' <daniele.ceccarelli@ericsson.com>
Thread-Topic: Opsdir last call review of draft-ietf-teas-actn-framework-13
Thread-Index: AQHT3/Elu3Qc21LD70yKwQWKRfoWc6QZt+NA
Date: Mon, 30 Apr 2018 19:49:44 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E173CFE44A3@sjceml521-mbx.china.huawei.com>
References: <152503048609.328.6923654156090705843@ietfa.amsl.com>
In-Reply-To: <152503048609.328.6923654156090705843@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: 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/teas/idFL9cAJJYjXdXPQZQH7-5V1cLE>
Subject: Re: [Teas] Opsdir last call review of draft-ietf-teas-actn-framework-13
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: Mon, 30 Apr 2018 19:49:52 -0000

Hi Scott,

Thanks for your comment on this draft. 

In regards to Nits, we have resolved all Bruno's comments and updated the draft. 

Thank you for your meta-level comment. I see your point --- throwing more bandwidth would solve some problem; however, this work is about providing network resources partitioned/sliced for different customers. Throwing more bandwidth to the network would not solve all of the customer's requirements such as monitoring and controlling of their virtual networks flexibly with expected QoS and Traffic Engineering constraints. In addition, the solution work is in progress utilizing data models for abstraction in the hierarchical network controller environments. There are many vendors and operators that are implementing ACTN solutions as they see this has value and usefulness. 

Hope this answers your comment.

Thanks & best regards,
Young & Daniele

-----Original Message-----
From: Scott Bradner [mailto:sob@sobco.com] 
Sent: Sunday, April 29, 2018 2:35 PM
To: ops-dir@ietf.org
Cc: draft-ietf-teas-actn-framework.all@ietf.org; ietf@ietf.org; teas@ietf.org
Subject: Opsdir last call review of draft-ietf-teas-actn-framework-13

Reviewer: Scott Bradner
Review result: Has Nits

I did an OPS-DIR review of Framework for Abstraction and Control of Traffic Engineered Networks (draft-ietf-teas-actn-framework-13). As a framework document rather than a technical specification this document does not have any direct operational issues though the framework is for a technology that is "all operations." With that in mind I did not see any particular operational worry other than the overall complexity of the solution.

I will defer to Bruno Decranene's review for his detailed listing of nits.

My only real comment is a meta one - I generally question the likelihood of widespread use of a system of this level of multi-player complexity in environments where it is reasonably easy to throw bandwidth at this class of problem.

That said, I see no reason to not publish this as an Informational RFC just in case the thought that went into this could be useful to others or, maybe, if the use of the technology itself proves to be more cost effective than adding bandwidth.