Re: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on draft-lee-teas-actn-requirements-01 a WG documents)
Lou Berger <lberger@labn.net> Thu, 01 October 2015 18:18 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 9813A1B2E5B for <teas@ietfa.amsl.com>; Thu, 1 Oct 2015 11:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.366
X-Spam-Level:
X-Spam-Status: No, score=-1.366 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, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, WEIRD_PORT=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 nAa2QqlMQfq6 for <teas@ietfa.amsl.com>; Thu, 1 Oct 2015 11:18:23 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id E08EF1B2E5F for <teas@ietf.org>; Thu, 1 Oct 2015 11:18:20 -0700 (PDT)
Received: (qmail 998 invoked by uid 0); 1 Oct 2015 18:18:18 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy4.mail.unifiedlayer.com with SMTP; 1 Oct 2015 18:18:18 -0000
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with id Q0JB1r01T2SSUrH010JEjG; Thu, 01 Oct 2015 18:18:17 -0600
X-Authority-Analysis: v=2.1 cv=Zs1+dbLG 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=5lJygRwiOn0A:10 a=pGLkceISAAAA:8 a=48vgC7mUAAAA:8 a=i0EeH86SAAAA:8 a=pmb6BNNbAAAA:8 a=0FD05c-RAAAA:8 a=gxZvrgisAAAA:8 a=NofaHbISM2RjGqoUYYIA:9 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=vD7hU49nG+5S3ytOp2fPvpquWLVfg7vCwtjKGXvDod8=; b=gXARgjw6qRysFxX2OOkT/3AKfOhIEo7fyfsiMsFhWFcN05903w8MT8gDC0wu+XiahjR+sN6sBFibaKMjin/UhRedhXHKAwAuwwZZvaH/czOhBA4gCU9OyJ8JYSiMkevk;
Received: from box313.bluehost.com ([69.89.31.113]:41952 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.84) (envelope-from <lberger@labn.net>) id 1ZhiQn-0006qd-47; Thu, 01 Oct 2015 12:18:13 -0600
To: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>, Vishnu Pavan Beeram <vishnupavan@gmail.com>, Leeyoung <leeyoung@huawei.com>
References: <55E75B39.1050101@labn.net> <5603EE48.1090008@labn.net> <56043F74.7010905@labn.net> <7AEB3D6833318045B4AE71C2C87E8E1729D233FE@dfweml706-chm> <CA+YzgTu_eso10Pj0H1R7fw-Kc+_LyiWX2UZHjOq_yCK1h7uVtw@mail.gmail.com> <4A1562797D64E44993C5CBF38CF1BE4812A29EE0@ESESSMB301.ericsson.se> <3cc986486830469883e5cc16ee5dba4c@ATL-SRV-MBX1.advaoptical.com> <4A1562797D64E44993C5CBF38CF1BE4812A2DE24@ESESSMB301.ericsson.se> <39ea453d879144d2b50a505dbf848bf9@ATL-SRV-MBX1.advaoptical.com> <7AEB3D6833318045B4AE71C2C87E8E1729D23916@dfweml706-chm> <4A1562797D64E44993C5CBF38CF1BE4812A381A6@ESESSMB301.ericsson.se> <2d639fc1306c48a2ac2feca23021417f@ATL-SRV-MBX1.advaoptical.com> <CA+YzgTvr2tH-Ff-bWCdYw-PhEhq19tFAZ+ZjhhvjBEd-7YKCnQ@mail.gmail.com> <7AEB3D6833318045B4AE71C2C87E8E1729D242FD@dfweml706-chm> <CA+YzgTudu4LA5C1SCxC=CAvaHLKVb94F_5KNpFti2kb1ghphxQ@mail.gmail.com> <6D32668528F93D449A073F45707153D8BEBB9F6A@US70UWXCHMBA03.zam.alcatel-lucent.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <560D78DD.4080306@labn.net>
Date: Thu, 01 Oct 2015 14:18:05 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <6D32668528F93D449A073F45707153D8BEBB9F6A@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/ymuSe2V-7z_oB214MQNZ8xLqmRI>
Cc: Igor Bryskin <IBryskin@advaoptical.com>, Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>, TEAS WG <teas@ietf.org>, "draft-lee-teas-actn-requirements@ietf.org" <draft-lee-teas-actn-requirements@ietf.org>
Subject: Re: [Teas] Proposed ACTN Definition Text (Re: 答复: 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: Thu, 01 Oct 2015 18:18:28 -0000
Even your proposed changes are in quotes: ACTN solutions will build on existing TE mechanisms "(i.e., TE constructs and TE protocol mechanisms)" wherever possible and appropriate; "however, this should not be construed as constraining protocol extension solutions if satisfying requirements necessitates this". how about *in place* of your changes NEW ACTN solutions will build on, and extend, existing TE constructs and mechanisms wherever possible and appropriate. Lou On 10/1/2015 12:55 PM, Varma, Eve L (Eve) wrote: > > Hi, > > > > Some additional clarifying text added on etherpad J > > > > Best regards, > > Eve > > > > *From:*Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com] > *Sent:* Tuesday, September 29, 2015 8:17 PM > *To:* Leeyoung > *Cc:* Igor Bryskin; Daniele Ceccarelli; Lou Berger; TEAS WG; Varma, > Eve L (Eve); draft-lee-teas-actn-requirements@ietf.org > *Subject:* Re: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > draft-lee-teas-actn-requirements-01 a WG documents) > > > > Young, Hi! > > The primary intent behind proposing the first statement ("build on > existing TE mechanisms") is to explicitly specify that the ACTN > solutions will build on existing TE constructs (TE-Tunnels/LSPs/Paths; > TE-Topological elements - TE-nodes/TE-links, etc) and TE protocol > mechanisms wherever possible and appropriate. > > The intent behind proposing the second statement ("controller based > approaches") is to explicitly indicate the inclusion of solutions > where the VN operations (as stated in the ACTN definition) are > orchestrated/controlled by one or more logically centralized entities > (controllers). > > Please feel free to edit the these two statements on etherpad (to > capture the above intent). > > Regards, > > -Pavan > > > > On Tue, Sep 29, 2015 at 12:11 PM, Leeyoung <leeyoung@huawei.com > <mailto:leeyoung@huawei.com>> wrote: > > Hi Pavan, > > Can you elaborate what "existing TE mechanisms" is meant? Some > examples you have in mind for this term may help understand the text > better? > > In addition, what do you mean "controller-based" approaches? > > Thanks. > Young > > -----Original Message----- > From: Vishnu Pavan Beeram [mailto:vishnupavan@gmail.com > <mailto:vishnupavan@gmail.com>] > Sent: Monday, September 28, 2015 8:59 PM > To: Igor Bryskin > Cc: Daniele Ceccarelli; Leeyoung; Lou Berger; TEAS WG; Varma, Eve L > (Eve); draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > Subject: Re: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > draft-lee-teas-actn-requirements-01 a WG documents) > > We (Lou and I) would like to propose the following additional language > (see the text on etherpad towards the end of the ACTN definition - > http://etherpad.tools.ietf.org:9000/p/teas-actn-def): > > "ACTN solutions will build on existing TE mechanisms wherever possible > and appropriate. Support for controller-based approaches is > specifically included in the possible solution set." > > Thoughts? Please feel free to make edits on the etherpad. > > Regards, > -Pavan (and Lou) > > On Mon, Sep 28, 2015 at 8:34 AM, Igor Bryskin > <IBryskin@advaoptical.com <mailto:IBryskin@advaoptical.com>> > wrote: > > > Hi Daniele, > > > > > > > > Please, see in line. > > > > Cheers, > > > > Igor > > > > > > > > *From:* Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com > <mailto:daniele.ceccarelli@ericsson.com>] > > *Sent:* Saturday, September 26, 2015 3:29 PM > > *To:* Leeyoung <leeyoung@huawei.com <mailto:leeyoung@huawei.com>>; > Igor Bryskin < > > IBryskin@advaoptical.com <mailto:IBryskin@advaoptical.com>>; Vishnu > Pavan Beeram <vishnupavan@gmail.com <mailto:vishnupavan@gmail.com>> > > *Cc:* Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>; TEAS > WG <teas@ietf.org <mailto:teas@ietf.org>>; Varma, > > Eve L (Eve) <eve.varma@alcatel-lucent.com > <mailto:eve.varma@alcatel-lucent.com>>; > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* RE: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > Igor, > > > > > > > > Young elaborated pretty well on my statements (thanks). > > > > > > > > I would say that a) and b) in your bullets perfectly define what I > > meant as infrastructure. > > > > > > > > c) is in my opinion a perfect example of connectivity service. You say > > that VPNs do not follow under the connectivity services category as > > they are not TE relate. Well a VPN does not provide TE, but connecting > > a VPN to a TE infrastructure in my opinion does. If a customer wants > > connectivity between 3 points with given TE constraints, why a VPN on > > top or a TE infrastructure shouldn’t meet that requirement? > > > > > > > > IB>> Current TEAS WG work – Abstract TE Topology model – does allow > > configuring customized TE topologies on per VPN basis. There is also a > > work being discussed to model topologies that combine routing and TE > > topologies as well as SPRING related information. Can you elaborate > > what exactly is missing from the ACTN point of view? > > > > > > > > On the virtual network function service, as Young mentioned, there are > > several use cases in ACTN and building the interaction between WAN SDN > > and Cloud SDN is a very common and requested use case. We could argue > > it’s not TEAS…well, if you correctly remember we tried to open a new > > working group because we thought that not 100% of the ACTN scope was > > covered by TEAS J > > > > > > > > IB>> This sounds like a good project for a company like ERICSSSON, > > however, what exactly are the problems you want to solve that have not > > been or are not being worked on in other WGs? > > > > > > > > Cheers > > > > Daniele > > > > > > > > > > > > > *From:* Leeyoung [mailto:leeyoung@huawei.com > <mailto:leeyoung@huawei.com> <leeyoung@huawei.com > <mailto:leeyoung@huawei.com>>] > > *Sent:* venerdì 25 settembre 2015 22:45 > > *To:* Igor Bryskin; Daniele Ceccarelli; Vishnu Pavan Beeram; Leeyoung > > *Cc:* Lou Berger; TEAS WG; Varma, Eve L (Eve); > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* RE: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > Hi Igor, > > > > > > > > I agree with you from a pure TE connectivity perspective. > > > > > > > > What Daniele is talking about is case where a TE connectivity has some > > constraints related with “customer’s” VN service policy. One example, > > a DCI case where the decision in selecting a destination for VM > > migration through TE networks may have not only QoS requirement but > > also other factors beyond QoS. Among them can be DC location > > (end-point) profile, preference/policy and capability; VNF mapping to > > the DC location, etc. Of course, these factors are not a pure TE > > connectivity constraints, but these factors may impact how to choose > a destination of a TE connectivity from a source. > > > > > > > > So the argument is who are the customer of such services? A couple of > > use-cases for ACTN addressed this kind of issues and they all > > concerned about DCI issues. Some of them are application providers > > that need to move massively large amount of data sets across DCNs > and multiple WAN domains. > > > > > > > > Here’s the link for relevant use-cases: > > > > > > > > https://www.ietf.org/archive/id/draft-lopez-actn-vno-multidomains-01.t > > xt > > > > https://tools.ietf.org/html/draft-fang-actn-multidomain-dci-00 > > > > > > > > I see neither L2VPN or L3VPN alone can solve this type of issues. VPN > > operators can also be viewed as a customer to ACTN-enabled networks. > > In such case, there would be coordination across VPN providers and > > Transport providers to meet the end-customer’s need. > > > > > > > > We can clearly start with a pure TE connectivity model, but not > > limited to this pure model. What do you think? > > > > > > > > Regards, > > > > Young > > > > > > > > > *From:* Igor Bryskin [mailto:IBryskin@advaoptical.com > <mailto:IBryskin@advaoptical.com> > > <IBryskin@advaoptical.com <mailto:IBryskin@advaoptical.com>>] > > *Sent:* Friday, September 25, 2015 10:54 AM > > *To:* Daniele Ceccarelli; Vishnu Pavan Beeram; Leeyoung > > *Cc:* Lou Berger; TEAS WG; Varma, Eve L (Eve); > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* RE: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > Hi Daniele, > > > > Please, see in line. > > > > > > > > Igor > > > > > > > > *From:* Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com > <mailto:daniele.ceccarelli@ericsson.com> > > <daniele.ceccarelli@ericsson.com > <mailto:daniele.ceccarelli@ericsson.com>>] > > *Sent:* Friday, September 25, 2015 9:56 AM > > *To:* Igor Bryskin <IBryskin@advaoptical.com > <mailto:IBryskin@advaoptical.com>>; Vishnu Pavan Beeram < > > vishnupavan@gmail.com <mailto:vishnupavan@gmail.com>>; Leeyoung > <leeyoung@huawei.com <mailto:leeyoung@huawei.com>> > > *Cc:* Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>; TEAS > WG <teas@ietf.org <mailto:teas@ietf.org>>; Varma, > > Eve L (Eve) <eve.varma@alcatel-lucent.com > <mailto:eve.varma@alcatel-lucent.com>>; > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* RE: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > I knew it was a topic worth being raised J > > > > > > > > Igor, I’ll use my personal definitions that didn’t end up in the final > > ACTN definition but it can be useful to understand each other. I see > > these > > 3 entities: > > > > > > > > 1. *Infrastructure*: nodes, links, but mostly LSP building the > > virtual networks between end points > > > > IB>> According to TE topology modeling we have: > > > > a) Provider native TE topology (provider network nodes and links), > > could be used as underlay supporting abstract TE topologies > > (overlays); > > > > b) Abstract TE topologies (customized per-client) (abstract nodes > > inter=connected by abstract links), overlays supported, for example, > > by provider native TE topology, could be configured by either > > provider, client or both > > > > c) Transport services provided to the client: traffic engineered > > connections connecting provider WRT a given service ingress/egress > > access links (i.e. links connecting client devices to the provider > > network). The service paths and parameters could be expressed by the > > client in terms of abstract topology elements, translated by the > > provider controller into terms of the provider native topology. > > > > > > > > 2. *Connectivity Services*: services built on top of the > > infrastructure to connect the clients, e.g. L2VPN, L3VPN. The > > customers asks for connectivity (with characteristics that will be > > mapped intor the > > infrastructure) identifying the end points. > > > > IB>> Why this is a part of ACTN? Don’t we have other WGs working on > this? > > > > Considering that this is TEAS WG work, what this has to do with TE? > > > > > > > > 3. *Virtual Network Function Services*: Services where the > customer > > needs a virtual function FOR one of its sites (e.g. VM instantiation). > > In most cases this is a request for connectivity towards A > > datacenter…which one is not of any importance for the customer. This > > is what is collected in Luyan’s use cases. > > > > IB>> The same questions > > > > > > > > I guess what you call “transport service” refers to the > > infrastructure? Or maybe both infrastructure and connectivity services? > > > > IB>> Please, see above > > > > > > > > Cheers > > > > Daniele > > > > > > > > *From:* Igor Bryskin [mailto:IBryskin@advaoptical.com > <mailto:IBryskin@advaoptical.com> > > <IBryskin@advaoptical.com <mailto:IBryskin@advaoptical.com>>] > > *Sent:* venerdì 25 settembre 2015 15:04 > > *To:* Daniele Ceccarelli; Vishnu Pavan Beeram; Leeyoung > > *Cc:* Lou Berger; TEAS WG; Varma, Eve L (Eve); > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* RE: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > Daniele, > > > > > > > > You are right. What you call “connectivity service” I call “transport > > service”, which is really “traffic engineered connectivity service”. > > You may think about “connectivity service” in a broader sense, e.g. IP > > or Ethernet non-TE (reachability based) connectivity, and it is a good > > question if such connectivity should be part of ACTN. I personally > > think not. > > > > > > > > One other type of service provided by network to client is Customized > > Abstract Topology itself, i.e. when the Customized Abstract Topology > > is (re-)configured by the client, as opposite to another use case when > > the Customized Abstract Topology is configured by the network operator > > and presented to the client in read-only mode. > > > > > > > > Cheers, > > > > Igor > > > > > > > > > > > > *From:* Teas [mailto:teas-bounces@ietf.org > <mailto:teas-bounces@ietf.org>] *On Behalf Of *Daniele > > Ceccarelli > > *Sent:* Friday, September 25, 2015 8:13 AM > > *To:* Vishnu Pavan Beeram <vishnupavan@gmail.com > <mailto:vishnupavan@gmail.com>>; Leeyoung < > > leeyoung@huawei.com <mailto:leeyoung@huawei.com>> > > *Cc:* Lou Berger <lberger@labn.net <mailto:lberger@labn.net>>; TEAS > WG <teas@ietf.org <mailto:teas@ietf.org>>; Varma, > > Eve L (Eve) <eve.varma@alcatel-lucent.com > <mailto:eve.varma@alcatel-lucent.com>>; > > draft-lee-teas-actn-requirements@ietf.org > <mailto:draft-lee-teas-actn-requirements@ietf.org> > > *Subject:* Re: [Teas] Proposed ACTN Definition Text (Re: 答复: Poll on > > > draft-lee-teas-actn-requirements-01 a WG documents) > > > > > > > > Thanks Igor for the comment on the policies, when shrinking it into > > the text we did too much “zipping” and lost some bits of info > > > > > > _______________________________________________ > Teas mailing list > 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