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

Vishnu Pavan Beeram <vishnupavan@gmail.com> Tue, 22 September 2015 17:20 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 A5F0D1B2C62; Tue, 22 Sep 2015 10:20: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 i1RE9Kk7ebK3; Tue, 22 Sep 2015 10:20:27 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (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 9298F1B2C61; Tue, 22 Sep 2015 10:20:26 -0700 (PDT)
Received: by vkfp126 with SMTP id p126so11101915vkf.3; Tue, 22 Sep 2015 10:20:25 -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=mtbO5lxh/ZA9IgcK4Cy/Ujf+k4w/guEYNPl2BktMKO8=; b=02np54f024FOh3klF0lnH11kxwijECbsQMqIQT/9DWDJubb/oUO2uEhuLltDFDmKGZ MBaWBLS4XjDoAESw978tVFQp+rh+UizL1o+HueECjmBs36uCd4n2V8I+/U33G9mS9hm6 b6z9zgavdXoN+8fyjnZ/Csfm9S+SWr1KSrjzv8QAIn0ZIH/XriPSMrKYPGiz8gxUxfKj fx6GYSdFMmVg2rh8HllvP2FtpqwpE9Q9M6jrZAEsYOLi4NVKguCndJKrgadL0l9YUDai GR1J2+ebAhMW6Bgnx8xUSh1fzW7OAcMoxFyfxRYD1C2P1uGxI0jHBoz8bS76C4GBBr0v rQ5w==
MIME-Version: 1.0
X-Received: by 10.31.146.203 with SMTP id u194mr18802641vkd.42.1442942425705; Tue, 22 Sep 2015 10:20:25 -0700 (PDT)
Received: by 10.31.96.141 with HTTP; Tue, 22 Sep 2015 10:20:25 -0700 (PDT)
In-Reply-To: <56017AC5.5080800@labn.net>
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>
Date: Tue, 22 Sep 2015 13:20:25 -0400
Message-ID: <CA+YzgTuy15TpNDSCdT7wC+eGvkzs-8Av1Eb8LhXfn0a=dnSupA@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary="001a1143945cb7351d05205936d6"
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/sWIzUxr5kdERIuJIpipF2OIpUYY>
Cc: TEAS WG <teas@ietf.org>, Leeyoung <leeyoung@huawei.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@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 17:20:28 -0000

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