IETF Logo Mail Archive

Re: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents

"Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com> Tue, 22 September 2015 15:39 UTC

Return-Path: <eve.varma@alcatel-lucent.com>
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 BE5EF1ACD52; Tue, 22 Sep 2015 08:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.61
X-Spam-Level:
X-Spam-Status: No, score=-6.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, 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 QRSC-5lVvN63; Tue, 22 Sep 2015 08:39:47 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-01.alcatel-lucent.com [135.245.210.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 628231ACD31; Tue, 22 Sep 2015 08:39:47 -0700 (PDT)
Received: from us70tusmtp2.zam.alcatel-lucent.com (unknown [135.5.2.64]) by Websense Email Security Gateway with ESMTPS id 8FE876E4AE249; Tue, 22 Sep 2015 15:39:42 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id t8MFdbMw010370 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Sep 2015 15:39:43 GMT
Received: from US70UWXCHMBA03.zam.alcatel-lucent.com ([169.254.9.242]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Tue, 22 Sep 2015 11:39:20 -0400
From: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>
To: Lou Berger <lberger@labn.net>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Leeyoung <leeyoung@huawei.com>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@ietf.org>
Thread-Topic: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents
Thread-Index: AQHQ9N63pCyN1lmkBk6vu+zdWwAi8p5Irwkw
Date: Tue, 22 Sep 2015 15:39:19 +0000
Message-ID: <6D32668528F93D449A073F45707153D8BEBB2938@US70UWXCHMBA03.zam.alcatel-lucent.com>
References: <55E75B39.1050101@labn.net> <55FA9E28.4060602@labn.net> <1A722C8D-3AC3-4CD4-BB0A-9E9C8155FD65@coriant.com> <55FB6000.4080904@labn.net> <4A1562797D64E44993C5CBF38CF1BE48129F0B44@ESESSMB301.ericsson.se> <CA+YzgTu38t9-aVnDn8u=BUz2rPqsrYg2dgVCc8Zc=KwGWmR+tg@mail.gmail.com> <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>
In-Reply-To: <5600BD48.9050408@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/h88uIV6cIRmra1XdD7kKy7QPevo>
Cc: Vishnu Pavan Beeram <vishnupavan@gmail.com>, TEAS WG <teas@ietf.org>
Subject: Re: [Teas] 答复: 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: Tue, 22 Sep 2015 15:39:48 -0000

Hi Lou,

Adding a definition seems a reasonable thing to do, considering all the discussion that's taken place.  From a procedure perspective, I assume the authors should first publish draft-teas-actn-requirements-00 as a WG draft without any changes to the content, and thereafter proceed from there to change “Transport” to “TE” within the draft and add a definition?

Best regards,
Eve

-----Original Message-----
From: Lou Berger [mailto:lberger@labn.net] 
Sent: Monday, September 21, 2015 10:31 PM
To: Daniele Ceccarelli; Leeyoung; draft-lee-teas-actn-requirements@ietf.org
Cc: Varma, Eve L (Eve); Vishnu Pavan Beeram; TEAS WG
Subject: Re: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents

Daniele, ACTN authors, All,

On 9/21/2015 8:44 AM, Daniele Ceccarelli wrote:
> ...
> Looking forward to progress a fruitful thread and publishing the WG draft so work can progress.
>

Okay, let's take a step back here. 

The basic question is how does ACTN fit into the TEAS WG. 

Based on the discussions to date in the context of the WG, we thought we understood where we were going WRT ACTN, but perhaps not.  We also clearly expected to answer this in greater detail  as the WG  moved towards "ACTN" solutions. 

As has been pointed out earlier in the thread, having the first document on a topic without any definition of the topic is a bit awkward.  So perhaps now would be a good time to provide a definition of ACTN that can be added to the requirements document. 

Could someone (individually or collectively) provide a definition of ACTN that would be suitable for inclusion in a -01 of the WG requirements document on the topic?

Also as mentioned before, it may be helpful to look at the MPLS-TP requirements document, RFC 5654, which provides an example of such a definition.

Thank you,
Lou

v2.23.0 | Report a Bug | By Email