Re: [Teas] FW: New Version Notification for draft-ietf-teas-actn-framework-03.txt

Hi Young,

While I agree that an example in Section 4.1 is a good idea, I personally find the ASCII art in Figure 6 quite confusing. Maybe I miss something, but neither the meaning of ".." and "..." is obvious to me, and also for "o" I have to guess quite a bit what this could be.

I think instead of trying to fit a lot into one Figure 6, it could be better to depict the topologies by ASCII art symbols similar to what is used elsewhere in the document, and use labels, e.g. with the terminology in Section 1.1. If the Figure gets too large with such symbols, I think separating it into several pieces would be possible.

My 2 cents...

Michael

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Leeyoung
> Sent: Thursday, February 02, 2017 5:36 PM
> To: Daniele Ceccarelli; TEAS WG (teas@ietf.org)
> Subject: Re: [Teas] FW: New Version Notification for draft-ietf-teas-actn-
> framework-03.txt
> 
> Hi WG,
> 
> The new version also made a new section 4.1 where VN creation process is
> illustrated to show how a VN is created recursively in the hierarchy of MDSCs.
> 
> With all the changes made in this version, the co-authors believe the document
> is ready for WG LC. If there are any comments on this version, please provide
> your comments in the list.
> 
> Thanks,
> Young (on behalf of co-authors).
> 
> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Daniele Ceccarelli
> Sent: Thursday, February 02, 2017 5:19 AM
> To: TEAS WG (teas@ietf.org) <teas@ietf.org>
> Subject: [Teas] FW: New Version Notification for draft-ietf-teas-actn-
> framework-03.txt
> 
> Hi WG,
> 
> We posted a new version of the ACTN fwk (03).
> 
> It addresses all the comments from Adrian
> (https://mailarchive.ietf.org/arch/msg/teas/K6jCQFL3ruPpSt1VRAaawpxgw64 ) and
> most of the comments from Michael (https://www.ietf.org/mail-
> archive/web/teas/current/msg01861.html ), in particular the following ones:
> 
> -	Remove orchestration from Page 5 and substitute with: domains
> coordination
> -	Comment on PNC and NMS: Added  this sentence to the definition in order
> to solve the following issues on NMS:
> 		oPNC: A Physical Network Controller is a domain controller that
> is responsible for controlling virtual or physical devices or NEs under its
> direct control. This can be an SDN controller, a Network Management System
> (NMS), an Element Management System (EMS) or any other mean to dynamically
> control a set of nodes and that is implementing an NBI compliant with ACTN
> specification.
> -	Fixed the reference to the ONF architecture
> -	Removed the PCE in figure 3 below the PNC , actually the PCE is a PNC
> -	Removed this sentence: “A hierarchy of PNCs can be foreseen for
> scalability and administrative choices.”…the hierarchy of PNCs can’t exist.
> 
> Thanks
> Daniele for the authors.
> 
> 
> 
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: giovedì 2 febbraio 2017 12:13
> > To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>; Young Lee
> > <leeyoung@huawei.com>
> > Subject: New Version Notification for
> > draft-ietf-teas-actn-framework-03.txt
> >
> >
> > A new version of I-D, draft-ietf-teas-actn-framework-03.txt
> > has been successfully submitted by Daniele Ceccarelli and posted to
> > the IETF repository.
> >
> > Name:		draft-ietf-teas-actn-framework
> > Revision:	03
> > Title:		Framework for Abstraction and Control of Traffic Engineered
> > Networks
> > Document date:	2017-02-02
> > Group:		teas
> > Pages:		34
> > URL:            https://www.ietf.org/internet-drafts/draft-ietf-teas-actn-
> > framework-03.txt
> > Status:         https://datatracker.ietf.org/doc/draft-ietf-teas-actn-
> framework/
> > Htmlized:       https://tools.ietf.org/html/draft-ietf-teas-actn-framework-
> 03
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-actn-
> framework-03
> >
> > Abstract:
> >    Traffic Engineered 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 or the customer of the operator that actually owns
> >    the network resources.
> >
> >    This document provides a framework for Abstraction and Control of
> >    Traffic Engineered Networks (ACTN).
> >
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
> > submission until the htmlized version and diff are available at
> tools.ietf.org.
> >
> > The IETF Secretariat
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas