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

[Daniele Ceccarelli <[e-mail]>]

Hi Michael,

No it's not intentional, my mistake. It reflects my conflicting relationship with Google.

I'll fix it.

Thanks
Daniele  

> -----Original Message-----
> From: Teas [mailto:[e-mail]] On Behalf Of Scharf, Michael
> (Nokia - DE)
> Sent: domenica 5 febbraio 2017 19:41
> To: Daniele Ceccarelli <[e-mail]>; TEAS WG
> ([e-mail]) <[e-mail]>
> Subject: Re: [Teas] FW: New Version Notification for draft-ietf-teas-actn-
> framework-03.txt
> 
> Hi Daniele,
> 
> Thanks for addressing "most" of my comments. One question, though...
> 
> > -----Original Message-----
> > From: Teas [mailto:[e-mail]] On Behalf Of Daniele
> > Ceccarelli
> > Sent: Thursday, February 02, 2017 12:19 PM
> > To: TEAS WG ([e-mail])
> > 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/K6jCQFL3ruPpSt1VRAaawpxgw6
> > 4 ) 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
> 
> Is it intentional that the reference is to ONF TR-502 (1.0, year 2014), and not
> the more recent document ONF TR-521 (1.1, year 2016)?
> 
> Thanks
> 
> Michael
> 
> 
> > -	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: [e-mail] [mailto:[e-mail]]
> > > Sent: giovedì 2 febbraio 2017 12:13
> > > To: Daniele Ceccarelli <[e-mail]>; Young Lee
> > > <[e-mail]>
> > > 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
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/teas