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

Vishnu Pavan Beeram <vishnupavan@gmail.com> Tue, 22 September 2015 17:52 UTC

Return-Path: <vishnupavan@gmail.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 41EAD1A9126; Tue, 22 Sep 2015 10:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-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 kVMHgIgXrsG1; Tue, 22 Sep 2015 10:52:27 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C65DC1A9140; Tue, 22 Sep 2015 10:52:26 -0700 (PDT)
Received: by vkao3 with SMTP id o3so11724481vka.2; Tue, 22 Sep 2015 10:52:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=R2FCx5rHgMJYo47yrjGtoA2TL9AvNjv25uQAEAOKP3Q=; b=Alkmv/kch8/5K2aojnIt6HndfuvPFIt+d0/i9JOaTvDoahgd95cL3Gqznyqq1BEzaJ 1e2uXbf1sOSbh89caRcOM9ZRc5wjtkzM860j1wkdHixOSqyB6N1gY13XSHkUALRfD5S8 l5AMh5i5sdWBfN1IiumHCThHs2xxYZ/x14OqYMx7nFRgS1SByzq14B8YH6FXP/VEEU0g myHQs3Jf5ui9PJV4FrM7qLQ8cq1HNT/FK64USU2xUgV3mpDfViR4vg6iDn0qBF/Mj5X4 V+rMhbtLrKf0Hbfn1Z1ijLQUEVRRaQXWJWOJvi4SmQfTIIX0zVltODXVykcxLpKuKGal Jl1Q==
MIME-Version: 1.0
X-Received: by 10.31.130.208 with SMTP id e199mr18581804vkd.78.1442944345911; Tue, 22 Sep 2015 10:52:25 -0700 (PDT)
Received: by 10.31.96.141 with HTTP; Tue, 22 Sep 2015 10:52:25 -0700 (PDT)
In-Reply-To: <B9FEE68CE3A78C41A2B3C67549A96F48B7602AF8@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>
Date: Tue, 22 Sep 2015 13:52:25 -0400
Message-ID: <CA+YzgTt0q=BwLZCsgE=ipE9SvsuEvQEM1jMzMhSE0i-aydpV5A@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
To: "BELOTTI, SERGIO (SERGIO)" <sergio.belotti@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="001a11466d142b38dd052059a970"
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/Rx_X2CGloYspc4LjUMP6EE6HooE>
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 17:52:29 -0000

>
> 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]
> *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; 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]
> > 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
> >
> >
> >
>
>
>