Re: [Teas] Thoughts on draft-ceccarelli-actn-framework-07.txt

Leeyoung <leeyoung@huawei.com> Wed, 06 May 2015 16:18 UTC

Return-Path: <leeyoung@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E31C1A014C for <teas@ietfa.amsl.com>; Wed, 6 May 2015 09:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level:
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, MANGLED_STOP=2.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 MT4jKPZZEleK for <teas@ietfa.amsl.com>; Wed, 6 May 2015 09:18:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D2621A0203 for <teas@ietf.org>; Wed, 6 May 2015 09:18:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BVS88604; Wed, 06 May 2015 16:18:03 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 6 May 2015 17:18:03 +0100
Received: from DFWEML706-CHM.china.huawei.com ([10.193.5.225]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Wed, 6 May 2015 09:18:00 -0700
From: Leeyoung <leeyoung@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Thoughts on draft-ceccarelli-actn-framework-07.txt
Thread-Index: AdCIDCeYAcDkI4zpRh2QqW2xCwhzvgAC0Lsg
Date: Wed, 06 May 2015 16:17:59 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729CB522A@dfweml706-chm>
References: <053f01d0880c$5fe606c0$1fb21440$@olddog.co.uk>
In-Reply-To: <053f01d0880c$5fe606c0$1fb21440$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.155.102]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/HNVfhbpRoTiXtjOcbmPg4kiIOg8>
Cc: "draft-ceccarelli-actn-framework@tools.ietf.org" <draft-ceccarelli-actn-framework@tools.ietf.org>
Subject: Re: [Teas] Thoughts on draft-ceccarelli-actn-framework-07.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 06 May 2015 16:18:07 -0000

Hi Adrian,

Thanks for providing your great comments. Please see inline for my response. 

Regards,
Young

-----Original Message-----
From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: Wednesday, May 06, 2015 9:53 AM
To: teas@ietf.org
Cc: draft-ceccarelli-actn-framework@tools.ietf.org
Subject: [Teas] Thoughts on draft-ceccarelli-actn-framework-07.txt

Hi,

I had cause to look at this draft again this week and a few comments popped up.

Here they are for the authors to think about.

Cheers,
Adrian

The I-D would best be renamed draft-ceccarelli-teas-actn-framework so that
people can more easily associate it with TEAS (just like you did with
draft-lee-teas-actn-requirements).

YOUNG>> Good idea. The revision will be published with the suggested title of the draft. 

---

I really like short Abstracts, but I think this one may be too short.
Need to add an initial paragraph on what is going on. I suggest...

   Transport networks have a variety of mechanisms to facilitate the
   separation of the data plane and control plane.  They also have a
   range of management and provisioning protocols to configure and 
   activate network resources.  These mechanisms represent key
   technologies for enabling flexible and dynamic networking.

   Abstraction of network resources is a technique that can be applied
   to a single network domain or across multiple domains to create a 
   single virtualized network that is under the control of a network
   operator that may be the customer of the operator that actually owns
   the network resources.

   This draft provides a framework for Abstraction and Control of
   Transport Networks (ACTN).

YOUNG>> Accepted. Thanks. 
---

Please run through the document and ensure consistent capitalisation of
all of the three controllers.

YOUNG>> OK, Will do. 
---

Section 1 page 3 para 2

OLD
   Centralized control in SDN
   helps improve network resources utilization from a distributed
   network control. 
NEW
   Centralized control in SDN helps improve network resources
   utilization compared with distributed network control. 
END


YOUNG>> OK. 
---

Section 1. Top of page 4

   Such a view may be specific to the set of consumed services as well
   as to a particular customer. 

"consumed services"? I think...

NEW
   Such a view may be specific to a specific service, the set of
   consumed resources or to a particular customer. 
END


YOUNG>> OK.
---

Page 4 bullet 1

Need to expand "ONF" on first use.


YOUNG>> OK. 
---

Page 5 top para (last para of section 1).

   The organization of this draft is as follows. Section 2 provides a
   discussion for a Business Model, Section 3 ACTN Architecture,
   Section 4 ACTN Applicability, and Section 5 ACTN Interface
   requirements.

This is out of date and since there is a perfectly good table of
contents, I suggest deleting this para.


YOUNG>> Yes, we can delete that. 
---

Section 5 is broken. You need to separate Daniele and Young as Authors
(section 5) and the rest as Contributors (section 6). 

YOUNG>> OK. Will correct. 

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas