[Teas] Proposed ACTN Definition Text (Re: 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents)

Lou Berger <lberger@labn.net> Thu, 24 September 2015 12:36 UTC

Return-Path: <lberger@labn.net>
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 68CAC1ACD18 for <teas@ietfa.amsl.com>; Thu, 24 Sep 2015 05:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.366
X-Spam-Level:
X-Spam-Status: No, score=-1.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, WEIRD_PORT=0.001] 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 NDmJz9Ss-8JF for <teas@ietfa.amsl.com>; Thu, 24 Sep 2015 05:36:44 -0700 (PDT)
Received: from gproxy5-pub.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id 49F621ACD16 for <teas@ietf.org>; Thu, 24 Sep 2015 05:36:42 -0700 (PDT)
Received: (qmail 10771 invoked by uid 0); 24 Sep 2015 12:36:38 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy5.mail.unifiedlayer.com with SMTP; 24 Sep 2015 12:36:38 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with id M0cX1r00R2SSUrH010caH6; Thu, 24 Sep 2015 06:36:36 -0600
X-Authority-Analysis: v=2.1 cv=C6F6l2/+ c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=ff-B7xzCdYMA:10 a=48vgC7mUAAAA:8 a=q_lmiWdQaxaeRUuK5x8A:9 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=YGbqz3h1fW6jKOrxdc5xO9ZrABfLR6L6xGYkzt4624U=; b=jyeo8zr4wrQYmmysajfIwwL7J2/wLP1MgfAKuO8khjQ+XP6axZyK8sR/x6EZ5no7J1dRqE6e3wlrJgcnBAx+YaMezUKAHdYx5xn2TW1ivyDzEWzM+XjCrIh8FBKS0fun;
Received: from box313.bluehost.com ([69.89.31.113]:50365 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1Zf5lI-00030V-Ur; Thu, 24 Sep 2015 06:36:33 -0600
To: Leeyoung <leeyoung@huawei.com>, Vishnu Pavan Beeram <vishnupavan@gmail.com>
References: <55E75B39.1050101@labn.net> <4A1562797D64E44993C5CBF38CF1BE48129F0F0E@ESESSMB301.ericsson.se> <6D32668528F93D449A073F45707153D8BEBB01AB@US70UWXCHMBA03.zam.alcatel-lucent.com> <55FC25E2.2000004@labn.net> <E4AC9A6F-FA33-4707-9CDC-4920DC30BB72@coriant.com> <55FC3D86.6080102@labn.net> <7AEB3D6833318045B4AE71C2C87E8E1729D1FCA7@dfweml706-chm> <55FC4D66.5070200@labn.net> <d2c37111aa12453c8a5143caa3709a71@ATL-SRV-MBX1.advaoptical.com> <55FC67E3.1030408@labn.net> <E0C26CAA2504C84093A49B2CAC3261A438CD7145@SZXEMA504-MBX.china.huawei.com> <55FEB30E.2060402@labn.net> <4A1562797D64E44993C5CBF38CF1BE4812A1CF18@ESESSMB301.ericsson.se> <5600BD48.9050408@labn.net> <6D32668528F93D449A073F45707153D8BEBB2938@US70UWXCHMBA03.zam.alcatel-lucent.com> <56017AC5.5080800@labn.net> <CA+YzgTuy15TpNDSCdT7wC+eGvkzs-8Av1Eb8LhXfn0a=dnSupA@mail.gmail.com> <7AEB3D6833318045B4AE71C2C87E8E1729D21A82@dfweml706-chm> <56019F6D.1090408@labn.net> <7AEB3D6833318045B4AE71C2C87E8E1729D21F52@dfweml706-chm>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <5603EE48.1090008@labn.net>
Date: Thu, 24 Sep 2015 08:36:24 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729D21F52@dfweml706-chm>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/qL99E7C1DsKjBScPQ7QLHJjIvmw>
Cc: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, TEAS WG <teas@ietf.org>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@ietf.org>
Subject: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 24 Sep 2015 12:36:46 -0000

NOTE: I've changed the title so that we can keep separate process
discussion from the definition discussion.  Please keep comments limited
to the appropriate thread so folks (like Adrian) that don't care about
the process can ignore it.

 <This is the non-process thread>



On 9/23/2015 1:21 PM, Leeyoung wrote:
> Hi Lou and Pavan, 
>
> ...
>
> Here's the working version of what ACTN is based on the authors/contributors input and based on ACTN framework and problem statement drafts. 
>
> We'd welcome the input of WG to refine this as a concerted effort. 
>
> Thanks,
>
> Young (on behalf of all contributors)
>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Abstraction and Control of TE Networks (ACTN) defines new methods and capabilities to support virtual network operations needed to orchestrate, control and manage 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 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 they can dynamically control their virtual networks by creating, modifying, monitoring, and deleting them.
>
> -	Multi-domain and multi-tenant virtual network operation via hierarchical abstraction of TE domains that facilitates multi-administration, multi-vendor, and multi-technology networks as a single virtualized network. This is achieved presenting the network domain as an abstracted topology to the customers via open and programmable interfaces. This allows for the recursion of controllers in a customer-provider relationship. 
>
> -	Orchestration of end-to-end virtual network services and applications via slicing 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, security/policy enforcement.
>
> -	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. 
>

Great.  This is constructive.  Thank you.

WG,

Please review/comment/propose changes. 

I've dropped the text into an etherpad
(http://etherpad.tools.ietf.org:9000/p/teas-actn-def) to track the
latest text.  Feel free to make changes there if you propose changes.

Lou

> -----Original Message-----
> From: Lou Berger [mailto:lberger@labn.net] 
> Sent: Tuesday, September 22, 2015 1:35 PM
> To: Leeyoung; Vishnu Pavan Beeram
> Cc: TEAS WG; Daniele Ceccarelli; Varma, Eve L (Eve); draft-lee-teas-actn-requirements@ietf.org
> Subject: Re: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents
>
> Young,
>
> On 9/22/2015 1:32 PM, Leeyoung wrote:
>> But not with the procedural violation! This would set a wrong 
>> precedent in IETF. I’d like to hold all of us accountable to the right 
>> procedure.
> I'm not sure to what you are referring.  The sole formal procedural requirement for issuing a draft is WG chair approval, at which time chairs select the filename.  Now it is certainly normal and good practice for  WG chairs to ensure support for the work via such things as polls, but this isn't procedurally required.  Also, chairs always evaluate the filename as part of our approval process, and while less common,  approve file names different than the form used by the individual draft.  Feel free to look around and you'll find a few examples.
>
> Now we'd really like to move the discussion to something a bit more than process and get a definition for inclusion in the -01 rev of the document.  -- which in our opinion will formally answer the question of if ACTN is just a (set of) solutions or something broader, and thereby inform the filename choice.
>
> Can you and the other authors help with that? 
>
> This question is open to all, so if you think you have a definition that's worth sharing, please chime in.
>
> Thanks,
> Lou
>
>
>
>