Re: [Teas] Poll on draft-lee-teas-actn-requirements-01 a WG documents
Lou Berger <lberger@labn.net> Fri, 18 September 2015 14:55 UTC
Return-Path: <lberger@labn.net>
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 338221B2DB1 for <teas@ietfa.amsl.com>; Fri, 18 Sep 2015 07:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.667
X-Spam-Level:
X-Spam-Status: No, score=-1.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, 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 0VFq3-pgkRLf for <teas@ietfa.amsl.com>; Fri, 18 Sep 2015 07:55:39 -0700 (PDT)
Received: from gproxy6-pub.mail.unifiedlayer.com (gproxy6-pub.mail.unifiedlayer.com [67.222.39.168]) by ietfa.amsl.com (Postfix) with SMTP id DADE81B2DAE for <teas@ietf.org>; Fri, 18 Sep 2015 07:55:38 -0700 (PDT)
Received: (qmail 27658 invoked by uid 0); 18 Sep 2015 14:55:38 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy6.mail.unifiedlayer.com with SMTP; 18 Sep 2015 14:55:38 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw4 with id Jeva1r00C2SSUrH01evdM6; Fri, 18 Sep 2015 08:55:38 -0600
X-Authority-Analysis: v=2.1 cv=QdD14Krv c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=wU2YTnxGAAAA:8 a=cNaOj0WVAAAA:8 a=IkcTkHD0fZMA:10 a=-NfooI8aBGcA:10 a=uEJ9t1CZtbIA:10 a=ff-B7xzCdYMA:10 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=1XWaLZrsAAAA:8 a=0FD05c-RAAAA:8 a=ArpIVqDIGT_l8hiNm7IA:9 a=VQbEJWUFuHNQQqjT:21 a=UGmEeZKW6Hz-pXcg:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=8SBxQdq6G5EtkN1R9tI+7+avr211RTP/9kfdqHzfcQk=; b=d05+AXmVg2G5VjJ/1PggY+F7n1U/9yunH1T6dMuOw3cFugiPabh+EjZo8CtpykRcpRdTs7SjYeE9b5KsbzcoTW2kFvhoXn3qq/vCXhh6ltKqHH/GISmWBVYN9YA2JtVx;
Received: from box313.bluehost.com ([69.89.31.113]:55051 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1Zcx4X-0004vB-TO; Fri, 18 Sep 2015 08:55:34 -0600
To: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, Vishnu Pavan Beeram <vishnupavan@gmail.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>
From: Lou Berger <lberger@labn.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <55FC25E2.2000004@labn.net>
Date: Fri, 18 Sep 2015 10:55:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <6D32668528F93D449A073F45707153D8BEBB01AB@US70UWXCHMBA03.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/AMTspzix487JReIkZImxh54dtWw>
Cc: "Doolan, Paul (Coriant - US/Irving)" <paul.doolan@coriant.com>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@ietf.org>, 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: Fri, 18 Sep 2015 14:55:42 -0000
On 09/18/2015 08:56 AM, Varma, Eve L (Eve) wrote: > Dear all, > > > > I must agree with Daniele’s points. In reviewing the inputs re > draft-lee-teas-actn-requirements becoming a WG document, which resulted > in its adoption as such, I don’t recall any inputs other than “Support”; > I didn’t see “Support, but clarify….” or “Support, but change….” Given > this, I am truly surprised at the discussion that has now arisen. Eve, See my last message. The comments were made in Pargue (publicly and expanded upon privately), and I had a discussion with the Authors via e-mail during the adoption period -- in this brief e-mail exchange I indicated that I decided to not impede adoption as I believe the current contents of the document is a great starting point for the WG. I specifically didn't want the discussion on what is basically how the "ACTN" *solution* fits in with the rest of IETF TE to impede the adoption of what is essentially a generic TE requirements document. > While I have no real issue in changing Transport to TE in the document > title to move this forward, though I don’t see the issue with using the > term Transport (which hasn’t been considered solely L0/L1 for a long > time), I hope that the authors would be able to move forward quickly to > publish as a WG draft with essentially the same title. Changing the title is not yet on the table and would not occur in the -00 rev of the document. Lou > > > > Bes regards, > > Eve > > > > *From:*Teas [mailto:teas-bounces@ietf.org] *On Behalf Of *Daniele Ceccarelli > *Sent:* Friday, September 18, 2015 8:38 AM > *To:* Vishnu Pavan Beeram > *Cc:* Doolan, Paul (Coriant - US/Irving); Lou Berger; > draft-lee-teas-actn-requirements@ietf.org; TEAS WG > *Subject:* Re: [Teas] Poll on draft-lee-teas-actn-requirements-01 a WG > documents > > > > Pavan, > > > > Please see inline. > > > > BR > Daniele > > > > *From:*Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com] > *Sent:* venerdì 18 settembre 2015 14:05 > *To:* Daniele Ceccarelli > *Cc:* Lou Berger; Doolan, Paul (Coriant - US/Irving); > 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 > > > > A few points to mull over and move the discussion along: > > - Fitting "ACTN" into the "TEAS" body of work: > Work focusing on "how TE networks can be abstracted and managed in a > controller(s) driven environment" is an obvious item of interest to the > WG. And this is primarily where we believe the "ACTN" work can > contribute; the requirements discussed in the document that just got > adopted by the WG aligns well with this. The intent behind the > name-change was to have something generic enough to capture what we want > this work to be about. Note that this is just a requirements document > and since this is the first document to be adopted in this realm, it is > important to get the "naming" right now rather than later. "VN > Controller" is perhaps not a great choice -- very much open to other > choices that would capture the essence of the first statement above. > > */[DanCe] The IETF is contribution driven. If the WG contributed a draft > related to a subset of what the chairs expect, it means that there is > interest just in that subset. If the chairs wanted something generic > enough they should have asked for a document generic enough (before the > wg adoption), not call for the adoption of a document and then ask to > change its scope. The authors are interested in writing ACTN > requirements, which not only is a subset of what the chairs ask for but > is also slightly different since we’re not speaking just about nodes and > links. /* > > > - Complementing existing TEAS work: > <draft-ietf-teas-interconnected-te-info-exchange> discusses the > architecture for the exchange of TE information between interconnected > TE networks in support of end-to-end TE path establishment. It discusses > in great detail the notion of "abstraction in TE networks". Our sincere > hope (belief rather) is that the <actn-requirements> document (and other > <actn> related documents that get adopted by the WG) would be > complementary to (/consistent with) the > <interconnected-te-info-exchange> draft. > > */[DanCe] What does complementary mean? Complementary in the sense that > interconnected TE is for multi-domain LSP establishment in distributed > control plane and ACTN does the same for centralized one? ACTN has a > broader scope. The multi domain and multi layer part can be seen as > complimentary, but again ACTN is not just nodes and links, it includes > services, VNF, network slices and so on./* > > > - Focus on the term "Controller": > One train of thought is to use this new work (conveniently facilitated > by the induction of ACTN into TEAS) to focus solely on the "controller" > aspects (given the belief that non-controller aspects are adequately > covered by existing solutions). Personally, I don't have a strong > preference on whether the "naming" should reflect this or not > (Danielle's latest suggestion - use "TE" in the ACTN acronym - is pretty > close to what I personally would like it to be), but it is important to > get some clarity on this "scoping" detail before zeroing in on any "name". > > */[DanCe] The scoping should have been made clear before the call for > adoption. The authors scoped the draft as X and asked for the adoption > of X and now they are requested to publish the draft as a starting point > for Y. In 2 years we have put together use cases, an architecture and > would have liked to start working on solutions for that, we’d like not > to start from the beginning again. Please note the list of ACTN related > drafts in TEAS (not to consider the expired ones still submitted as > draft-xxxxx-actn…)/* > > */ /* > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-klee-teas-actn-connectivity-multi-domain-02%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-klee-teas-actn-connectivity-multi-domain > <http://tools.ietf.org/id/draft-klee-teas-actn-connectivity-multi-domain-02.txt> > > > > -02 > <http://tools.ietf.org/html/draft-klee-teas-actn-connectivity-multi-domain-02.txt> > > > > 2015-06-08 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-kumaki-teas-actn-multitenant-vno-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-kumaki-teas-actn-multitenant-vno > <http://tools.ietf.org/id/draft-kumaki-teas-actn-multitenant-vno-00.txt> > > > > -00 > <http://tools.ietf.org/html/draft-kumaki-teas-actn-multitenant-vno-00.txt> > > > > 2015-07-06 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-lam-teas-usage-info-model-net-topology-01%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-lam-teas-usage-info-model-net-topology > <http://tools.ietf.org/id/draft-lam-teas-usage-info-model-net-topology-01.txt> > > > > -01 > <http://tools.ietf.org/html/draft-lam-teas-usage-info-model-net-topology-01.txt> > > > > 2015-07-03 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-lee-teas-actn-requirements-01%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-lee-teas-actn-requirements > <http://tools.ietf.org/id/draft-lee-teas-actn-requirements-01.txt> > > > > -01 <http://tools.ietf.org/html/draft-lee-teas-actn-requirements-01.txt> > > > > 2015-07-27 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-leebelotti-teas-actn-info-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-leebelotti-teas-actn-info > <http://tools.ietf.org/id/draft-leebelotti-teas-actn-info-00.txt> > > > > -00 <http://tools.ietf.org/html/draft-leebelotti-teas-actn-info-00.txt> > > > > 2015-07-02 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-leeking-teas-actn-problem-statement-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-leeking-teas-actn-problem-statement > <http://tools.ietf.org/id/draft-leeking-teas-actn-problem-statement-00.txt> > > > > -00 > <http://tools.ietf.org/html/draft-leeking-teas-actn-problem-statement-00.txt> > > > > 2015-06-09 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-suzuki-teas-actn-multidomain-opc-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-suzuki-teas-actn-multidomain-opc > <http://tools.ietf.org/id/draft-suzuki-teas-actn-multidomain-opc-00.txt> > > > > -00 > <http://tools.ietf.org/html/draft-suzuki-teas-actn-multidomain-opc-00.txt> > > > > 2015-07-06 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-xu-teas-actn-abstract-alarm-report-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-xu-teas-actn-abstract-alarm-report > <http://tools.ietf.org/id/draft-xu-teas-actn-abstract-alarm-report-00.txt> > > > > -00 > <http://tools.ietf.org/html/draft-xu-teas-actn-abstract-alarm-report-00.txt> > > > > 2015-07-06 > > http://tools.ietf.org/images/search-small.gif > <https://www.google.com/search?as_q=%22draft-ceccarelli-teas-actn-framework-00%22&as_sitesearch=mailarchive.ietf.org/arch/browse/teas/> > > > > draft-ceccarelli-teas-actn-framework > <http://tools.ietf.org/id/draft-ceccarelli-teas-actn-framework-00.txt> > > > > -00 <http://tools.ietf.org/html/draft-ceccarelli-teas-actn-framework-00.txt> > > > > 2015-06-15 > > */ /* > > */ /* > > Regards, > > -Pavan > > > > On Fri, Sep 18, 2015 at 3:22 AM, Daniele Ceccarelli > <daniele.ceccarelli@ericsson.com > <mailto:daniele.ceccarelli@ericsson.com>> wrote: > > Lou, > > Is your concern mostly related to the "transport" word? In the last > years the concept of transport evolved pretty much, mostly with > transport SDN and it is no longer tied to the L0-L1 but it covers > whatever mean used to transport IP. Young already pointed out what the > draft aims to cover. > > If you're so strongly willing to change the name we could turn > "Transport" into TE so that it becomes Abstraction and Control of TE > networks. (this is my personal proposal, not shared by the other > ACTNers)...and ACTN remains, but with the "broader" scope and it is > "more" complementary to the interconnected TE. > The change of the file name is not just the change of a file name. > > Daniele > >> -----Original Message----- >> From: Lou Berger [mailto:lberger@labn.net <mailto:lberger@labn.net>] >> Sent: venerdì 18 settembre 2015 02:51 >> To: Doolan, Paul (Coriant - US/Irving) >> Cc: TEAS WG; draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> >> Subject: Re: [Teas] Poll on draft-lee-teas-actn-requirements-01 a WG >> documents >> >> > >> Paul, >> >> On 9/17/2015 4:28 PM, Doolan, Paul (Coriant - US/Irving) wrote: >> > Hello Lou and Pavan, >> > >> > this instruction to change ACTN to VN-Controller seems a little high >> handed. >> >> I/we hear you. But... >> >> > Young Lee, Danielle and their co-authors have spent a long time working >> on this and creating mind share and name recognition for ACTN. I know what >> it stands for as do audiences around the world to whom the team have >> introduced the idea and from whom they have garnered support. >> >> That's fair, but from our perspective the IETF has been working TE a lot >> longer than the term ACTN has been around, and that is the context where >> this work fits. >> >> As I stated at the last meeting, it's my (not to speak for Pavan, but > think he >> agrees too) option that this work is complimentary to the > interconnected-te >> particularly as it is more focused on the >> controller/non-fully distributed control plane approaches. We think >> that covering such controller based TE models as very important and > fills an >> important gap in the TE architecture. >> >> Right now, we (the WG) are just at the requirements stage and those >> requirements apply quite broadly and that is what we (the chairs) want to >> make clear by the name change. >> >> > In contrast I have absolutely no idea what a vn-controller >> > requirements draft might be about and, >> >> > if you persist with this renaming, it clearly makes no sense to make 'no >> other changes to the draft' since, at the very least, the (new) title > needs >> explanation. >> >> It's just a filename. That said, we (chairs) are trying to project > where the >> work will end up based on the WG consensus process. Chairs have changed >> names in the past and been right and sometimes wrong, but in the end we >> have an RFC published with the title that represents WG consensus and an >> RFC number. >> >> > I really think the draft should be adopted as (originally) named. If > you want >> to change the name then coming back to the WG with a clearly articulated >> rationale and asking for its support would seem to me to be a more > inclusive >> way to do things. >> >> It's not unusual for chairs to change names of a draft at adoption. >> Normally it goes without comment. Perhaps if this wasn't the first 'actn' >> document it would have. >> >> Again, we're open to alternatives that capture the scope of the work. >> >> Lou >> >> > my 10cents, >> > pd >> > >> > >> > >> > >> > On Sep 17, 2015, at 7:04 AM, Lou Berger wrote: >> > >> >> All, >> >> The WG poll is closed. >> >> >> >> Authors, >> >> Please republish draft-lee-teas-actn-requirements-01 as >> >> draft-ietf-teas-vn-controller-requirements-00 with only the date and >> >> file name changed. >> >> Comments received (publicly and privately) should be discussed and >> >> addresses in the -01 version. >> >> >> >> Please note the file name change. Normally it's pretty formulaic. >> >> But this draft is a little different as it has evolved over time to >> >> its current form and where we expect it to go. In particular, we >> >> see this draft as a companion to the 'interconnected-te' work and >> >> covering the various possible controller-based TE models (where the >> >> previous work was more focused on fully distributed control models). >> >> So we think a broader name warranted. >> >> >> >> Again, no other changes to the draft should be made at this time. >> >> >> >> Thank you, >> >> Lou and Pavan >> >> >> >> On 9/2/2015 4:25 PM, Lou Berger wrote: >> >>> All, >> >>> >> >>> This is start of a two week poll on making >> >>> draft-lee-teas-actn-requirements-01 a TEAS working group document. >> >>> Please send email to the list indicating "yes/support" or "no/do not >> >>> support". If indicating no, please state your technical reservations >> >>> with the document. If yes, please also feel free to provide >> >>> comments you'd like to see addressed once the document is a WG >> document. >> >>> >> >>> The poll ends September 16th >> >>> Thanks, >> >>> Lou and Pavan >> >>> >> >>> _______________________________________________ >> >>> Teas mailing list >> >>> Teas@ietf.org <mailto:Teas@ietf.org> >> >>> https://www.ietf.org/mailman/listinfo/teas >> >>> >> >> >> >> _______________________________________________ >> >> Teas mailing list >> >> Teas@ietf.org <mailto:Teas@ietf.org> >> >> https://www.ietf.org/mailman/listinfo/teas >> > >> > > _______________________________________________ > Teas mailing list > Teas@ietf.org <mailto:Teas@ietf.org> > https://www.ietf.org/mailman/listinfo/teas > > >
- [Teas] Poll on draft-lee-teas-actn-requirements-0… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Daniele Ceccarelli
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Dieter Beller
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Varma, Eve L (Eve)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Yuji Tochio
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Andrew G. Malis
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Quintin zhao
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Takuya Miyasaka
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Loa Andersson
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Xufeng Liu
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Jeff Tantsura
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Zhangxian (Xian)
- [Teas] 答复: Poll on draft-lee-teas-actn-requiremen… Zhenghaomian
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Fatai Zhang
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Huaimo Chen
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Dongjie (Jimmy)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Kwangkoog Lee
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Mach Chen
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Aihua Guo
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… 鈴木敏明 / SUZUKI,TOSHIAKI
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Dhruv Dhody
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Daniele Ceccarelli
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Varma, Eve L (Eve)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Daniele Ceccarelli
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Doolan, Paul (Coriant - US/Irving)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Andrew G. Malis
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Zhangxian (Xian)
- [Teas] 答复: Poll on draft-lee-teas-actn-requiremen… Zhenghaomian
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Varma, Eve L (Eve)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Daniele Ceccarelli
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Vishnu Pavan Beeram
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Daniele Ceccarelli
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Varma, Eve L (Eve)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Igor Bryskin
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Doolan, Paul (Coriant - US/Irving)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Leeyoung
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Igor Bryskin
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- [Teas] 答复: Poll on draft-lee-teas-actn-requiremen… Zhenghaomian
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Zhangxian (Xian)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Lou Berger
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] Poll on draft-lee-teas-actn-requiremen… Zhangxian (Xian)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Daniele Ceccarelli
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Lou Berger
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Varma, Eve L (Eve)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Lou Berger
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Varma, Eve L (Eve)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Lou Berger
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Leeyoung
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Vishnu Pavan Beeram
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Leeyoung
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Vishnu Pavan Beeram
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Leeyoung
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… BELOTTI, SERGIO (SERGIO)
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Lou Berger
- Re: [Teas] 答复: Poll on draft-lee-teas-actn-requir… Leeyoung
- [Teas] Proposed ACTN Definition Text (Re: 答复: Pol… Lou Berger
- [Teas] WG adoption and draft naming process (Re: … Lou Berger
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] WG adoption and draft naming process (… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Lou Berger
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Vishnu Pavan Beeram
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Zhangxian (Xian)
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Giovanni Martinelli (giomarti)
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Daniele Ceccarelli
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Daniele Ceccarelli
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] WG adoption and draft naming process (… Daniele Ceccarelli
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Daniele Ceccarelli
- Re: [Teas] WG adoption and draft naming process (… Lou Berger
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Vishnu Pavan Beeram
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Leeyoung
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Vishnu Pavan Beeram
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Daniele Ceccarelli
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Igor Bryskin
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Daniele Ceccarelli
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Varma, Eve L (Eve)
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Lou Berger
- Re: [Teas] WG adoption and draft naming process (… Lou Berger
- Re: [Teas] Proposed ACTN Definition Text (Re: 答复:… Varma, Eve L (Eve)
- Re: [Teas] WG adoption and draft naming process (… Leeyoung
- Re: [Teas] WG adoption and draft naming process (… Lou Berger
- Re: [Teas] WG adoption and draft naming process (… Leeyoung