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

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 06 May 2015 14:53 UTC

Return-Path: <adrian@olddog.co.uk>
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 ACC0E1ACDA3 for <teas@ietfa.amsl.com>; Wed, 6 May 2015 07:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.3
X-Spam-Level:
X-Spam-Status: No, score=-100.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_STOP=2.3, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] 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 9q-aEfAAZn7v for <teas@ietfa.amsl.com>; Wed, 6 May 2015 07:53:19 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B64FB1ACD76 for <teas@ietf.org>; Wed, 6 May 2015 07:53:18 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id t46ErGoC030012; Wed, 6 May 2015 15:53:16 +0100
Received: from 950129200 (jplon-nat12.juniper.net [193.110.55.12]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id t46ErDTb029951 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 6 May 2015 15:53:14 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: teas@ietf.org
Date: Wed, 06 May 2015 15:53:10 +0100
Message-ID: <053f01d0880c$5fe606c0$1fb21440$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCIDCeYAcDkI4zpRh2QqW2xCwhzvg==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21524.007
X-TM-AS-Result: No--13.313-10.0-31-10
X-imss-scan-details: No--13.313-10.0-31-10
X-TMASE-MatchedRID: YljPWrWy9t5HdhuYYkLbTOmc4/pDEQa27Le741QScwhxLdRaRYf22j3O I50zUwHgKRSPua7nDcHRhlG8MjLrXIuestpzLAVPxZQoGMRGhhNG/JUd7BvSQqahpdmRZCVuZAk UOpYIyGqObIAKMbDdIL4bOTEqgJ/88aBaUhpwDPW4jAucHcCqnV+iEcKpKdpugac2CvgtNes/sJ JrvRfE1OFncs+4EmXtmVqtsZidiQyhzaM0+ttmeMvGXPoeezwBQKuv8uQBDjqQcp7izK6RGNLLr CowcRc6ZQ7uOAFsU1/9KP9acIz8s01+zyfzlN7y/sToY2qzpx7dB/CxWTRRu25FeHtsUoHuYaCd Tepp2itNzhjwgzU+3raK9B3tElS1STXsXkV13hw+kK598Yf3Mg==
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/nBJKFpPwS5j71wPewY6K8KmljHY>
Cc: draft-ceccarelli-actn-framework@tools.ietf.org
Subject: [Teas] Thoughts on draft-ceccarelli-actn-framework-07.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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 14:53:23 -0000

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).

---

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).

---

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

---

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

---

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

---

Page 4 bullet 1

Need to expand "ONF" on first use.

---

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.

---

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