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

"BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com> Tue, 22 September 2015 18:06 UTC

Return-Path: <sergio.belotti@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 D77F71A92DC; Tue, 22 Sep 2015 11:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.609
X-Spam-Level:
X-Spam-Status: No, score=-6.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 aesdHUVqsg8g; Tue, 22 Sep 2015 11:06:36 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 2F96D1A916A; Tue, 22 Sep 2015 11:06:34 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 68CA5CCEA8195; Tue, 22 Sep 2015 18:06:28 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t8MI6Umo010990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Sep 2015 20:06:30 +0200
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.213]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Tue, 22 Sep 2015 20:06:30 +0200
From: "BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com>
To: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Thread-Topic: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents
Thread-Index: AQHQ9N654UWqYxDScEiY3o2MTisAA55IjmyAgAAFgYCAABa+gIAAIgeA///m6oCAACKOoA==
Date: Tue, 22 Sep 2015 18:06:29 +0000
Message-ID: <B9FEE68CE3A78C41A2B3C67549A96F48B7602B49@FR711WXCHMBA05.zeu.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> <6D32668528F93D449A073F45707153D8BEBB2938@US70UWXCHMBA03.zam.alcatel-lucent.com> <56017AC5.5080800@labn.net> <CA+YzgTuy15TpNDSCdT7wC+eGvkzs-8Av1Eb8LhXfn0a=dnSupA@mail.gmail.com> <B9FEE68CE3A78C41A2B3C67549A96F48B7602AF8@FR711WXCHMBA05.zeu.alcatel-lucent.com> <CA+YzgTt0q=BwLZCsgE=ipE9SvsuEvQEM1jMzMhSE0i-aydpV5A@mail.gmail.com>
In-Reply-To: <CA+YzgTt0q=BwLZCsgE=ipE9SvsuEvQEM1jMzMhSE0i-aydpV5A@mail.gmail.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_B9FEE68CE3A78C41A2B3C67549A96F48B7602B49FR711WXCHMBA05z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/iZy_PvTN-l4wxqOaE-Mbam-2UMs>
Cc: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>, TEAS WG <teas@ietf.org>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@ietf.org>, Leeyoung <leeyoung@huawei.com>, Lou Berger <lberger@labn.net>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
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 18:06:39 -0000

It is certainly fair as soon as required before WG adoption as WG seems to me already support for this , not after , and before publication. If missed definition, that , btw, I explained you why it is missed in the draft document,  would be a real problem for WG, I guess WG would have expressed needs for this update before WG adoption request.
Any debate as you mention would be on a further version of the document when an update would been required not when WG already expressed support for version 00 adoption.

Regards
Sergio



From: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com]
Sent: martedì 22 settembre 2015 19:52
To: BELOTTI, SERGIO (SERGIO)
Cc: Lou Berger; Varma, Eve L (Eve); Daniele Ceccarelli; Leeyoung; draft-lee-teas-actn-requirements@ietf.org; TEAS WG
Subject: Re: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents


So can you kindly explain why we should put the text  “justifies using "ACTN" to characterize the set of requirements that have been put forth” when the draft has been created exactly to collect requirements for ACTN ?
Since this is the first document under the "ACTN umbrella" to be adopted by the WG, I think it is fair to expect a definition for "ACTN" to be present in this document and to expect it to be debated thoroughly. I don't understand the reluctance to come up with a definition or point to an existing definition.
Regards,
-Pavan







From: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com<mailto:vishnupavan@gmail.com>]
Sent: martedì 22 settembre 2015 19:20
To: Lou Berger
Cc: Varma, Eve L (Eve); Daniele Ceccarelli; Leeyoung; draft-lee-teas-actn-requirements@ietf.org<mailto:draft-lee-teas-actn-requirements@ietf.org>; TEAS WG
Subject: Re: [Teas] 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents


> 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?

Any input on this would be much appreciated.

I thought the proposal texts from Igor and Xian were pretty good for a start. Can the authors please build on this and put together some text that succinctly defines ACTN (text that, hopefully, justifies using "ACTN" to characterize the set of requirements that have been put forth)? Given all the work that has gone into this (and all the documents that have been put together so far) over the past couple of years, I would like to think that this wouldn't take too long.
Regards,
-Pavan


On 9/22/2015 11:39 AM, Varma, Eve L (Eve) wrote:
> 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<mailto:lberger@labn.net>]
> Sent: Monday, September 21, 2015 10:31 PM
> To: Daniele Ceccarelli; Leeyoung; draft-lee-teas-actn-requirements@ietf.org<mailto: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
>
>
>