Re: [Actn] IETF 91

Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Mon, 30 March 2015 07:36 UTC

Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: actn@ietfa.amsl.com
Delivered-To: actn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670AB1A9119 for <actn@ietfa.amsl.com>; Mon, 30 Mar 2015 00:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.795
X-Spam-Level:
X-Spam-Status: No, score=-0.795 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506] autolearn=ham
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 W1IzcUECMzmc for <actn@ietfa.amsl.com>; Mon, 30 Mar 2015 00:36:14 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E31B1A9115 for <actn@ietf.org>; Mon, 30 Mar 2015 00:36:13 -0700 (PDT)
X-AuditID: c1b4fb2d-f79a46d0000006b4-94-5518fcebb4e2
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id D2.B2.01716.BECF8155; Mon, 30 Mar 2015 09:36:11 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.84]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0210.002; Mon, 30 Mar 2015 09:36:10 +0200
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Leeyoung <leeyoung@huawei.com>, "actn@ietf.org" <actn@ietf.org>
Thread-Topic: IETF 91
Thread-Index: AdBpCuKXp3YmX19fRtKijOMBVm5SQABsEpwg
Date: Mon, 30 Mar 2015 07:36:10 +0000
Message-ID: <4A1562797D64E44993C5CBF38CF1BE48128BD0E4@ESESSMB301.ericsson.se>
References: <7AEB3D6833318045B4AE71C2C87E8E1729CAAED6@dfweml706-chm>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729CAAED6@dfweml706-chm>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_4A1562797D64E44993C5CBF38CF1BE48128BD0E4ESESSMB301erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+Jvje7rPxKhBnf3iVls6bnAZjFtnqsD k0fLkbesHkuW/GQKYIrisklJzcksSy3St0vgyjj3SbXgg2XF7ndN7A2MXwy7GDk5JARMJCZt nMIOYYtJXLi3nq2LkYtDSOAoo8S+jxsYIZzFjBKrt80Dcjg42ASsJJ4c8gFpEBFwltiw/Sgz iC0sICJx534jG0RcVOLCldXMELaRxO91rxhBbBYBVYnem09YQGxeAV+Jxrl3mEBsIQEXiZUv LoDVcwq4ShzoOcQKYjMKyEpM2L0IrJdZQFzi1pP5TBCHCkgs2XOeGcIWlXj5+B8rhK0osfNs OzNEfb7E9SlPmSF2CUqcnPmEZQKjyCwko2YhKZuFpAwiriOxYPcnNghbW2LZwtfMMPaZA4+Z kMUXMLKvYhQtTi0uzk03MtZLLcpMLi7Oz9PLSy3ZxAiMqYNbfuvuYFz92vEQowAHoxIPr8I6 iVAh1sSy4srcQ4zSHCxK4rx2xodChATSE0tSs1NTC1KL4otKc1KLDzEycXBKNTB2TORtP+zx bL1+9scZB3i2Z5Qx/vxUOOE1hxv/rKvdwrNiyyK1FRtlXvZ92FLIodYttMVoybGucvO2wCVf k299jF3BscJdxLhz3ZeXszn0DhQ2ZIVNX/FUekLMd3YDg1Pbb28ROqI6eWrErrx2tf/Kzmve BrFsOlVso3t84TW3+uKrikqbW+4qsRRnJBpqMRcVJwIAEo737IoCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/actn/QQdTsGtqxA0HbeixroOr98IaKIo>
Subject: Re: [Actn] IETF 91
X-BeenThere: actn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Abstraction and Control of Transport Networks \(ACTN\)" <actn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/actn>, <mailto:actn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/actn/>
List-Post: <mailto:actn@ietf.org>
List-Help: <mailto:actn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/actn>, <mailto:actn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 07:36:16 -0000

This does not mean that we're done with ACTN :)

We're just at the beginning in TEAS, where we'll work on requirements, architecture and possibly models, but then we'll need to start working on protocols.
Which protocols will be augmented is still TBD (or maybe we'll come to the conclusion that a new one is needed), but in any case we'll need a strong ACTN design team coordinating the work among the different working groups (or a brand new ACTN working group).

Please keep on following (and driving) the progresses on the TEAS list.

Thanks you all
Daniele

From: ACTN [mailto:actn-bounces@ietf.org] On Behalf Of Leeyoung
Sent: sabato 28 marzo 2015 04:54
To: actn@ietf.org
Subject: [Actn] IETF 91

Hi,

Hope all is fine with you. Thanks you for your readership and participation over the past several months. I thank each one of you for your interest in ACTN.

I wanted to share some directions and news about ACTN as many people were curious about the ACTN status.  In IETF 91 at Dallas, ACTN requirement was presented in the TEAS WG meeting and received an overwhelming support from an informal hand-raising. As a result of that, we will find the ACTN home base in the TEAS WG to address architecture and information model and possibly development  of data models. Protocol development is yet to be seen and will depend on the work to be progressed down the road.

Please continue to address your interest in and contribution for ACTN work. Please send your question to the list.

Thanks.
Young