[Actn] IETF 91
Leeyoung <leeyoung@huawei.com> Sat, 28 March 2015 03:54 UTC
Return-Path: <leeyoung@huawei.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 DF1F41A1B7A for <actn@ietfa.amsl.com>; Fri, 27 Mar 2015 20:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 jhg709pQ3AYJ for <actn@ietfa.amsl.com>; Fri, 27 Mar 2015 20:54:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BF391A1B57 for <actn@ietf.org>; Fri, 27 Mar 2015 20:54:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQU29795; Sat, 28 Mar 2015 03:54:23 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 28 Mar 2015 03:54:23 +0000
Received: from DFWEML706-CHM.china.huawei.com ([10.193.5.225]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Fri, 27 Mar 2015 20:54:19 -0700
From: Leeyoung <leeyoung@huawei.com>
To: "actn@ietf.org" <actn@ietf.org>
Thread-Topic: IETF 91
Thread-Index: AdBpCuKXp3YmX19fRtKijOMBVm5SQA==
Date: Sat, 28 Mar 2015 03:54:18 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729CAAED6@dfweml706-chm>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.136.10]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E1729CAAED6dfweml706chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/actn/pMrpxOpvCNbipgWRZmHp-AHeaH8>
Subject: [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: Sat, 28 Mar 2015 03:54:28 -0000
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
- [Actn] IETF 91 Leeyoung
- Re: [Actn] IETF 91 Andrew G. Malis
- Re: [Actn] IETF 91 Daniele Ceccarelli