Re: [Teas] WG adoption and draft naming process (Re: 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents)

[Leeyoung <[e-mail]>]

Hi Lou and Pavan,

I think this is good. Thanks for driving this definition more clearer and acceptable to all and making this work workable in TEAS WG. 

I'd be happy to upload the requirements draft (00) shortly. 

Best regards,
Young

-----Original Message-----
From: Lou Berger [mailto:[e-mail]] 
Sent: Thursday, October 01, 2015 2:19 PM
To: TEAS WG
Cc: Vishnu Pavan Beeram; [e-mail]
Subject: Re: [Teas] WG adoption and draft naming process (Re: 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents)


All,
   We think the ACTN definition has reached a sufficient point where we'd like to do the following:

1) leave the requirements document tied to the ACTN solution space and publish draft-lee-teas-actn-requirements-01 as draft-ietf-teas-actn-requirements-00

2) Immediately, publish draft-ietf-teas-actn-requirements-01 with the discussed definition added to the intro section (Other changes to the intro section to align with the definition are at the discretion of the
editor.)   The definition from etherpad is:

   Abstraction and Control of TE Networks (ACTN) refers to the set
   of virtual network operations needed to orchestrate, control and
   manage large-scale multi-domain TE networks so as to facilitate
   network programmability, automation, efficient resource sharing,
   and end-to-end virtual service aware connectivity and network
   function virtualization services.

   These operations are summarized as follows:

   - Abstraction and coordination of underlying network resources
     to higher-layer applications and customers, independent of how
     these resources are managed or controlled, so that these
     higher-layer entities can dynamically control virtual
     networks. Where control includes creating, modifying,
     monitoring, and deleting virtual networks.

   - Multi-domain and multi-tenant virtual network operations via
     hierarchical abstraction of TE domains that facilitates
     multi-administration, multi-vendor, and multi-technology
     networks as a single virtualized network. This is achieved by
     presenting the network domain as an abstracted topology to the
     customers via open and programmable interfaces. Which allows
     for the recursion of controllers in a customer-provider
     relationship.

   - Orchestration of end-to-end virtual network services and
     applications via allocation of network resources to meet
     specific service, application and customer requirements.

   - Adaptation of customer requests (made on virtual resources) to
     the physical network resources performing the necessary
     mapping, translation, isolation and, policy that allows
     conveying, managing and enforcing customer policies with
     respect to the services by the network to said customer.

   - Provision of a computation scheme and virtual control
     capability via a data model to customers who request virtual
     network services. Note that these customers could, themselves,
     be service providers.

   ACTN solutions will build on, and extend, existing TE constructs
   and TE mechanisms wherever possible and appropriate.  Support
   for controller-based approaches is specifically included in the
   possible solution set.

3) For any area of ACTN-related work/solutions that the authors/contributors believe are outside the scope of the TEAS WG
charter: Please propose charter changes you think will cover the new area of work on the list and we can discuss with the WG and our AD.

Thank you,
Lou and Pavan