Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
Greg Mirsky <gregimirsky@gmail.com> Tue, 26 October 2021 21:31 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ABAC3A18D5; Tue, 26 Oct 2021 14:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Yc65Gk8n1Qph; Tue, 26 Oct 2021 14:31:26 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 F1E533A1935; Tue, 26 Oct 2021 14:28:37 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id z20so2182031edi.0; Tue, 26 Oct 2021 14:28:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yrfkmXdOIe3cazMUUcOWm5SwrkBQxJphsUv7QeM7Bpw=; b=Ukd5UyStltw5ZaOc7Vai9b8cABOnGMZ6NEPgV6dAYv35VbuIZGBTnUulM2Hgp1fVk0 y2omwUbK2cY0U6p7NPJwVVtyExyvvvYSsKUfjdmnXNlTX8WfvDj0Oli+B45emyZQtzA0 u7LA1Koz/FR5ULh/pPFbe3/YEPNZHYX2EToEi294RRNOSyE+qA5mX/rfOzUHtx+iYQ7Y HmEbxbe4gGxAChuL1ViXEXwSw+stW18wgHSgoxJq1a+XRDiyWiRN3LFcev7hrn3u3MW9 ph2Lz6IwNqbkDoKZx9hhIK5Gp3BJx5Vo4pT8/F1cpTmqmPCfH18cPdrOTyP5z0TZXD3j HqqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yrfkmXdOIe3cazMUUcOWm5SwrkBQxJphsUv7QeM7Bpw=; b=tT7+2pra+E5MUM8Nk6dHdzUgj4JRDw9+HBtsNWx2PQOIYLIDvBcRkM7IQXXDghA7D+ 8QcnxuV+D/434U3ueydvBseHhxLRDtOQN1d4jJQRCE3bAKRFkYLDOhJSoF2Dg/195txs Z0VXu5qfwDcfwvHEAdtADoNjkDgODyVG/5fcjj7oOsPn7ZBfofIbrNoz424n1J5L/trO 0Fz+OpBe4lWoeJB4h1qx3HHg8/WU85+moTxlDgAfAIWQvJuQ69UF6mmzAYoLWOkXbh5l 6nJ5jU885yYa167VcKtSV8G/GW5cvpY4oV4Tq4usuegyTLG0+5br6oB6wLItB7xEKzJk vczw==
X-Gm-Message-State: AOAM533uYTJSgLCATz/nkFYvYoyDK55di3y8nAUwLpeDgpyWk5WfGXYx qQTzhomvoFhSltCV/Cp2uDKvX9qEPNfQxNGiwsMgD3g7AaE=
X-Google-Smtp-Source: ABdhPJyndW7GY2S+SPrB2LQie5CPd732gGF/RbjWwlBshRBuIov84OAt2PTBSCZybmDq9b3vARFAyFUT8+B3cgBeZ1E=
X-Received: by 2002:a17:907:2d06:: with SMTP id gs6mr13656357ejc.477.1635283711375; Tue, 26 Oct 2021 14:28:31 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR13MB4204AEAF9D0F44DA0E4E0C4CD2AB9@DM6PR13MB4204.namprd13.prod.outlook.com> <DM8PR11MB5719868719840728F04A360EC9AE9@DM8PR11MB5719.namprd11.prod.outlook.com> <BL0PR05MB531610C8939F7E0C741E165AAEAF9@BL0PR05MB5316.namprd05.prod.outlook.com> <BN0PR11MB57263566709BA15200E44CBAC9AF9@BN0PR11MB5726.namprd11.prod.outlook.com> <BL0PR05MB53169700BE4620420B3F3BAEAEAF9@BL0PR05MB5316.namprd05.prod.outlook.com> <CAOj+MMGiPUq71C_hEeR74JT18jWYpmSHBihZKeRJZeeprL-Ldg@mail.gmail.com> <CA+RyBmXDe8Qsg9JBt0KPzNUDtCOTsF_+3SDEUoWgrssqSfK91Q@mail.gmail.com> <CO6PR11MB5650080ED84067C3943ACD66ACB09@CO6PR11MB5650.namprd11.prod.outlook.com> <CA+RyBmWWHfni+oqjo1-a0o0gtTnoUDuL7gRFSLwQYvfRGPdtwg@mail.gmail.com> <CO6PR11MB56507C80A718DB505DC97C73ACB19@CO6PR11MB5650.namprd11.prod.outlook.com> <CA+RyBmW_AvaMjpBSJMqoM8wG5OXo2q8j=yGa+qO75JGyC8uGbg@mail.gmail.com> <CO6PR11MB5650A1361A5F75A4827904EAACB29@CO6PR11MB5650.namprd11.prod.outlook.com> <CA+RyBmXo_wDmFO9jRFAo6ok_irOtSWzEaDpU8oSRsBN+k63q0A@mail.gmail.com> <CO6PR11MB565063F24696D8B96D2276B6ACB79@CO6PR11MB5650.namprd11.prod.outlook.com>
In-Reply-To: <CO6PR11MB565063F24696D8B96D2276B6ACB79@CO6PR11MB5650.namprd11.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 26 Oct 2021 14:28:20 -0700
Message-ID: <CA+RyBmVwg89psA=5U9RRS+oh6Ref5ehnHnpvrR1ucasJB08R9g@mail.gmail.com>
To: "Francois Clad (fclad)" <fclad@cisco.com>
Cc: Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, James Guichard <james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b93d7405cf48287b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/NdvpzXKcfiC71iytAJ-M-u41XyA>
Subject: Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Oct 2021 21:31:32 -0000
Dear Francois et al., I appreciate your consideration of the scenarios when both compression methods were used. I'll be looking for the next update of the draft. I hope the authors will add a section with a clear description of scenarios when the two compression methods can be used. But in the meantime, I am still strongly concerned that adoption of the draft in its current version would violate the decision of the WG (as I understand the result of the earlier poll) to adopt a single compression method (not a single document that defines two (at the minimum) incompatible methods to compress SRv6 SIDs. I've read multiple notes that asserted that in the testing, the ability to mix REPLACE-C-SID and NEXT-C-SID was verified and confirmed. It seems to me that sharing more information about these tests could address my concern. But at this time, I strongly object to SPRING WG's adoption of the current draft version as it would violate the earlier decision reached by the WG. Regards, Greg On Wed, Oct 13, 2021 at 3:56 AM Francois Clad (fclad) <fclad@cisco.com> wrote: > Hi Greg, > > > > Your understanding is correct. The C-SID flavors cannot be randomly mixed > within the same C-SID container. > > > > We can clarify the details related to the combination of flavors in a > C-SID container in an upcoming version of the draft. For example, the last > entry of a C-SID container can carry a C-SID bound to any behavior, > including one with another C-SID flavor. > > > > Thanks, > > Francois > > > > *From: *Greg Mirsky <gregimirsky@gmail.com> > *Date: *Friday, 8 October 2021 at 22:21 > *To: *Francois Clad (fclad) <fclad@cisco.com> > *Cc: *Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica= > 40juniper.net@dmarc.ietf.org>, James Guichard < > james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, > spring-chairs@ietf.org <spring-chairs@ietf.org> > *Subject: *Re: [spring] WG Adoption call for > https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ > > Hi Francois, > you've said that different flavors of C-SID can be present not only in the > same SRH but also in the same C-SID container. The latter case got me > thinking about several potential scenarios. Have to admit that I got stuck > trying to understand how they can work. I hope you can help me out. Please > consider the two cases described below. > > Consider, for all cases, that we are handling a container with entries A, > B, C, and D, of some mix of NEXT-C-SID and REPLACE-C-SID flavors. > > Case 1: > Suppose that A was the REPLACE-C-SID flavor C-SID and B is the NEXT-C-SID > flavor. When A is processed, B will be copied into the IPv6 DA, retaining > the prefix before A in the container. So far, so good. Then, when the > packet arrives at the node that processes B, it will say "NEXT". The > remaining bits will be? I thought zero, but actually, it will presumably be > two bits with the value two? So the subsequent behavior will shift that two > up? Even if the NEXT-C-SID flavor guesses that the two should be zero, it > would skip C and D and pick up the entry from the next C-SID container in > the SRH. So it seems to either work wrong or work oddly? > > Case 2: > Suppose that A was the NEXT-C-SID flavor. So it simply shifts B, C, D > upwards in the IPv6 DA. Suppose B is the REPLACE-C-SID flavor. It will > interpret the upper bits of the C C-SID as the arg for selecting the > position in the C-SID container to pull an entry from. It will also modify > the C C-SID to perform the decrement it thinks it needs. It will then > overwrite itself with the randomly chosen entry from the container. > > It seems that neither scenario works. At least, I cannot figure out how it > can work. I would greatly appreciate it if you could have a look and > clarify it for me. > > Regards, > > Greg > > > > On Fri, Oct 8, 2021 at 10:12 AM Francois Clad (fclad) <fclad@cisco.com> > wrote: > > Hi Greg, > > > > Thank you for the confirmation. I am glad that the matter of combining > C-SIDs of different flavors is clear now. > > > > Thanks, > > Francois > > > > *From: *Greg Mirsky <gregimirsky@gmail.com> > *Date: *Thursday, 7 October 2021 at 20:15 > *To: *Francois Clad (fclad) <fclad@cisco.com> > *Cc: *Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica= > 40juniper.net@dmarc.ietf.org>, James Guichard < > james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, > spring-chairs@ietf.org <spring-chairs@ietf.org> > *Subject: *Re: [spring] WG Adoption call for > https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ > > Hi Francois, > > thank you for your detailed response and confirming that C-SIDs of > different flavors/behavior may be present in the same SRH and even the same > CSID container. I've noticed Ron's proposal as I was trying to formulate my > question. His proposal highlighted what I am trying to understand - the > relationship between NEXT-C-SID and REPLACE-C-SID. I concur with Ron. The > WG has adopted the compression analysis draft > <https://datatracker.ietf.org/doc/draft-ietf-spring-compression-analysis/>, > and the updates and an additional analysis Ron proposed will keep the > discussion and decision-making process on the firm technical foundation. > > > > Regards, > > Greg > > > > On Thu, Oct 7, 2021 at 9:17 AM Francois Clad (fclad) <fclad@cisco.com> > wrote: > > Hi Greg, > > > > It is the role of the SR Source Node [Section 3.1 of RFC 8754] to form the > segment list in the SRH. It learns about the available SIDs in the network > with their associated behavior and flavors via control plane and/or > management plane protocols, as described in Section 8 of RFC 8986, and > selects the SIDs that are the most appropriate for the segment list. > > > > Each SR Segment Endpoint Node [Section 3.3 of RFC 8754] simply executes > the pseudocode of a locally instantiated SID when it receives a packet > matching that SID. The SR Segment Endpoint Node does not need to bother > about the behavior/flavor of the subsequent SRv6 SIDs. > > > > This SRv6 logic applies to the C-SID flavors as well. The choice of > flavors for the SIDs in the SID List is up to the SR Source Node. > > > > It is indeed possible to mix SIDs of different C-SID flavors in the same > SRH, and even in a single C-SID container. > > > > Thanks, > > Francois > > > > > > *From: *Greg Mirsky <gregimirsky@gmail.com> > *Date: *Wednesday, 6 October 2021 at 19:19 > *To: *Francois Clad (fclad) <fclad@cisco.com> > *Cc: *Robert Raszuk <robert@raszuk.net>, Ron Bonica <rbonica= > 40juniper.net@dmarc.ietf.org>, James Guichard < > james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, > spring-chairs@ietf.org <spring-chairs@ietf.org> > *Subject: *Re: [spring] WG Adoption call for > https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ > > Hi Francois, > > thank you for the clarification. It is still not clear how a node selects > which flavor of CSID to use on the next compressed CSID that may happen > also be in the next CSID container. As I understand it, a CSID container > must use the same flavor of compression but CSID containers with different > compression flavors in the same SRH are allowed. Is that correct > understanding? > > > > Regards, > > Greg > > > > On Wed, Oct 6, 2021 at 7:05 AM Francois Clad (fclad) <fclad@cisco.com> > wrote: > > Hi Greg, > > > > A node that supports this draft in its entirety can instantiate SRv6 SIDs > (e.g., End and End.X SIDs) with any of the three C-SID flavors. > > > > In particular, a node can instantiate multiple SRv6 SIDs bound to > different C-SID flavors, possibly with different C-SID lengths. It can also > instantiate SRv6 SIDs with behaviors and flavors defined in RFC 8986. > > > > As defined in Section 4.3 of RFC 8754 and again in Section 3 of RFC 8986, > upon receiving an IPv6 packet with a destination address matching a FIB > entry that represents one of these locally instantiated SIDs, the node > processes the packet according to the behavior (and flavor(s)) (i.e. > pseudocode) of that SID. > > > > RFC 8754 and 8986 have already standardized these mechanisms and the C-SID > draft only leverages the same SRv6 dataplane to introduce new endpoint > flavors for compression. > > > > > > Francois > > > > *From: *spring <spring-bounces@ietf.org> on behalf of Greg Mirsky < > gregimirsky@gmail.com> > *Date: *Tuesday, 5 October 2021 at 23:37 > *To: *Robert Raszuk <robert@raszuk.net> > *Cc: *Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, James Guichard < > james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, > spring-chairs@ietf.org <spring-chairs@ietf.org> > *Subject: *Re: [spring] WG Adoption call for > https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ > > Hi Robert, > > as I understand it, you believe everything that is written in the draft. I > hope you can help me find an answer to one simple question: > > Can a node that supports this draft in its entirety, i.e., supports all > "flavors" defined in the document, process received SRv6 packet with the > SRH encoded according to the specification? > > So far, the proponents of the draft referred to "planning" how flavors of > SRv6 SID compressed. To the best of my understanding, that is is a clear > demonstration of the incompatibility between flavors defined in the CSID > draft. Regardless of what is written in it. > > > > Regards, > > Greg > > > > On Tue, Oct 5, 2021 at 1:24 PM Robert Raszuk <robert@raszuk.net> wrote: > > Ron & SPRING WG chairs, > > > > Through this discussion we first have seen a debate if we need one or more > data planes to compress SIDs in SRv6. WG clearly stated we need one. > > > > Following that we have observed a first terminology shift to see if asking > how many solutions should be supported will work any better. To that many > WG members clearly stated that they support one solution. > > > > Well please notice that the draft in question in its introduction states: > > > > Abstract > > This document defines a compressed SRv6 Segment List Encoding in the > Segment Routing Header (SRH). *This solution* does not require any SRH > data plane change nor any SRv6 control plane change. *This solution* > leverages the SRv6 Network Programming model. > > > > So based on my understanding of English the entire draft talks about a > single solution. > > > > Then suddenly a new question popped up: how many behaviours are > acceptable. > > > > I bet number of folks including myself said "one" keeping in mind previous > discussions and the definition of "one" meaning based on the SRv6 data > plane in compliance to [RFC8402], [RFC8754] and [RFC8986]. > > > > Interestingly enough the draft in question defines not behaviours but > flavors as new variants of the already defined behaviors in Standards Track > RFCs. Namely it defines: > > > > 4.1. NEXT-C-SID Flavor > > 4.2. REPLACE-C-SID Flavor > > > > The newly defined behaviour End.XPS is optional. > > So if there is anything to ask here is to check if WG is ok with two > flavors or not. I do not recall that question has ever been asked formally > during the WG adoption call. > > > > With that let's note that optimal compressed SID size may be different > network to network. One size does not fit all. Draft says: > > 6.1. C-SID Length > > The NEXT-C-SID flavor supports both 16- and 32-bit C-SID lengths. A > * C-SID length of 16-bit is recommended.* > > The REPLACE-C-SID flavor supports both 16- and 32-bit C-SID lengths. > * A C-SID length of 32-bit is recommended.* > > > > While I personally think 8-bit should be an option, if we choose a single > flavor we will introduce suboptimality for no good reason. Hardware > capable of supporting any flavor clearly can do LPM on locator. Also > hardware capable of supporting one flavor can support few other flavors as > this is pretty much just an offset game. > > > > Kind regards, > > Robert > > > > > > > > On Tue, Oct 5, 2021 at 9:43 PM Ron Bonica <rbonica= > 40juniper.net@dmarc.ietf.org> wrote: > > Pablo, > > > > Ae you sure? Please look at the question as Joel asked it ( > https://mailarchive.ietf.org/arch/msg/spring/nS2gnQ_jxvpbmcxs_d3JAbUCT1I/ > ). > > > > > Ron > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring > >
- [spring] WG Adoption call for https://datatracker… James Guichard
- Re: [spring] WG Adoption call for https://datatra… Huaimo Chen
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Shraddha Hegde
- Re: [spring] WG Adoption call for https://datatra… Andrew Alston
- Re: [spring] WG Adoption call for https://datatra… Andrew Alston
- Re: [spring] WG Adoption call for https://datatra… Tony Li
- Re: [spring] WG Adoption call for https://datatra… Gyan Mishra
- Re: [spring] WG Adoption call for https://datatra… James Guichard
- Re: [spring] WG Adoption call for https://datatra… Gyan Mishra
- Re: [spring] WG Adoption call for https://datatra… Andrew Alston
- Re: [spring] WG Adoption call for https://datatra… Melchior Aelmans
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… James Guichard
- Re: [spring] WG Adoption call for https://datatra… Andrew Alston
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Gyan Mishra
- Re: [spring] WG Adoption call for https://datatra… Qiuyuanxiang
- Re: [spring] WG Adoption call for https://datatra… liu.aihua
- Re: [spring] WG Adoption call for https://datatra… linchangwang
- Re: [spring] WG Adoption call for https://datatra… Yangfan(Fan,IP Standards)
- Re: [spring] WG Adoption call for https://datatra… Daniam Henriques
- Re: [spring] WG Adoption call for https://datatra… Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [spring] WG Adoption call for https://datatra… Daniam Henriques
- Re: [spring] WG Adoption call for https://datatra… Zafar Ali (zali)
- Re: [spring] WG Adoption call for https://datatra… Keyur Patel
- Re: [spring] WG Adoption call for https://datatra… Linda Dunbar
- Re: [spring] WG Adoption call for https://datatra… Gaurav Dawra
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Pablo Camarillo (pcamaril)
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Pablo Camarillo (pcamaril)
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Robert Raszuk
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Greg Mirsky
- Re: [spring] WG Adoption call for https://datatra… Darren Dukes (ddukes)
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Voyer, Daniel
- Re: [spring] WG Adoption call for https://datatra… Mankamana Mishra (mankamis)
- Re: [spring] WG Adoption call for https://datatra… Dirk Steinberg
- [spring] R: WG Adoption call for https://datatrac… angelo tulumello
- Re: [spring] WG Adoption call for https://datatra… Rakesh Gandhi (rgandhi)
- Re: [spring] WG Adoption call for https://datatra… Kamran Raza (skraza)
- Re: [spring] WG Adoption call for https://datatra… Ahmed Bashandy
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Ahmed Bashandy
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Darren Dukes (ddukes)
- Re: [spring] WG Adoption call for https://datatra… Antonio Cianfrani
- Re: [spring] WG Adoption call for https://datatra… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [spring] WG Adoption call for https://datatra… Stefano Salsano
- Re: [spring] WG Adoption call for https://datatra… Bernier, Daniel
- Re: [spring] WG Adoption call for https://datatra… Kireeti Kompella
- Re: [spring] WG Adoption call for https://datatra… Colby Barth
- Re: [spring] WG Adoption call for https://datatra… Kireeti Kompella
- Re: [spring] WG Adoption call for https://datatra… bruno.decraene
- Re: [spring] WG Adoption call for https://datatra… Tarek Saad
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Tarek Saad
- Re: [spring] WG Adoption call for https://datatra… Francois Clad (fclad)
- Re: [spring] WG Adoption call for https://datatra… Jeffrey (Zhaohui) Zhang
- Re: [spring] WG Adoption call for https://datatra… gongliyan@chinamobile.com
- Re: [spring] WG Adoption call for https://datatra… Sales, Bernard (Nokia - BE/Antwerp)
- Re: [spring] WG Adoption call for https://datatra… Giulio Sidoretti
- Re: [spring] WG Adoption call for https://datatra… Martin Horneffer
- Re: [spring] WG Adoption call for https://datatra… Srihari Sangli
- Re: [spring] WG Adoption call for https://datatra… Andrew Alston
- Re: [spring] WG Adoption call for https://datatra… James Guichard
- [spring] 回复: WG Adoption call for https://datatra… 苏远超(以泰)
- Re: [spring] WG Adoption call for https://datatra… Parag Kaneriya
- Re: [spring] WG Adoption call for https://datatra… Swadesh Agrawal (swaagraw)
- Re: [spring] WG Adoption call for https://datatra… Dongjie (Jimmy)
- Re: [spring] WG Adoption call for https://datatra… Xiejingrong (Jingrong)
- Re: [spring] WG Adoption call for https://datatra… Ahmed MostafaSaleh ElSawaf
- Re: [spring] WG Adoption call for https://datatra… Laurent Metzger
- Re: [spring] WG Adoption call for https://datatra… liujh.cc
- Re: [spring] WG Adoption call for https://datatra… Luc-Fabrice Ndifor Ngwa [ MTN Cameroon ]
- Re: [spring] WG Adoption call for https://datatra… Tianran Zhou
- Re: [spring] WG Adoption call for https://datatra… Huzhibo
- Re: [spring] WG Adoption call for https://datatra… Peter Psenak
- Re: [spring] WG Adoption call for https://datatra… liupengyjy@outlook.com
- Re: [spring] WG Adoption call for https://datatra… duzongpeng@foxmail.com
- Re: [spring] WG Adoption call for https://datatra… DiVincenzo, Mike
- Re: [spring] WG Adoption call for https://datatra… Ron Bonica
- Re: [spring] WG Adoption call for https://datatra… Rishabh Parekh
- Re: [spring] WG Adoption call for https://datatra… Kang, Haitao
- Re: [spring] WG Adoption call for https://datatra… Francesco Lombardo
- Re: [spring] WG Adoption call for https://datatra… Marco Bonola
- Re: [spring] WG Adoption call for https://datatra… Carmine Scarpitta
- Re: [spring] WG Adoption call for https://datatra… Sébastien Parisot
- Re: [spring] WG Adoption call for https://datatra… Mike Koldychev (mkoldych)
- Re: [spring] WG Adoption call for https://datatra… Pier Luigi Ventre
- Re: [spring] WG Adoption call for https://datatra… Mark Smith
- Re: [spring] WG Adoption call for https://datatra… Paolo Lungaroni
- Re: [spring] WG Adoption call for https://datatra… Andrea Mayer
- Re: [spring] WG Adoption call for https://datatra… David Lo Bascio
- Re: [spring] WG Adoption call for https://datatra… Primadi Hendra Kusuma
- Re: [spring] WG Adoption call for https://datatra… Mach Chen
- Re: [spring] WG Adoption call for https://datatra… Satoru Matsushima
- Re: [spring] WG Adoption call for https://datatra… Wanghaibo (Rainsword)
- Re: [spring] WG Adoption call for https://datatra… Dhruv Dhody
- Re: [spring] WG Adoption call for https://datatra… Thomas.Graf
- Re: [spring] WG Adoption call for https://datatra… Sudarshan, Reshma
- Re: [spring] WG Adoption call for https://datatra… Julian Klaiber
- Re: [spring] WG Adoption call for https://datatra… Severin Dellsperger
- [spring] 答复: WG Adoption call for https://datatra… fuyuexia
- Re: [spring] WG Adoption call for https://datatra… Kentaro Ebisawa
- Re: [spring] WG Adoption call for https://datatra… Weiqiang Cheng
- Re: [spring] WG Adoption call for https://datatra… Joel M. Halpern
- Re: [spring] WG Adoption call for https://datatra… David Melman
- Re: [spring] WG Adoption call for https://datatra… zhuyq8@chinatelecom.cn
- Re: [spring] WG Adoption call for https://datatra… Chengli (Cheng Li)
- Re: [spring] WG Adoption call for https://datatra… Paul Mattes
- [spring] 回复: WG Adoption call for https://datatra… Xing James Jiang (jamjiang)
- Re: [spring] WG Adoption call for https://datatra… Tetsuya Murakami
- Re: [spring] WG Adoption call for https://datatra… Takuya Miyasaka
- Re: [spring] WG Adoption call for https://datatra… Bao,Guixin
- Re: [spring] WG Adoption call for https://datatra… Bao,Guixin
- Re: [spring] WG Adoption call for https://datatra… Shay Zadok
- Re: [spring] WG Adoption call for https://datatra… Kalyani Rajaraman
- Re: [spring] WG Adoption call for https://datatra… andre beliveau
- Re: [spring] WG Adoption call for https://datatra… Giuseppe Siracusano
- Re: [spring] WG Adoption call for https://datatra… Luis M. Contreras
- Re: [spring] WG Adoption call for https://datatra… 田辉
- Re: [spring] WG Adoption call for https://datatra… TIAN
- Re: [spring] WG Adoption call for https://datatra… 庞冉(联通集团中国联通研究院-本 部)
- Re: [spring] WG Adoption call for https://datatra… John Scudder