Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators
bruno.decraene@orange.com Mon, 20 June 2022 16:37 UTC
Return-Path: <bruno.decraene@orange.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8E0C15AAEC; Mon, 20 Jun 2022 09:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 45mYjbIfET7I; Mon, 20 Jun 2022 09:37:10 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F4CDC15AAEB; Mon, 20 Jun 2022 09:37:09 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4LRb013WRXzCqwy; Mon, 20 Jun 2022 18:37:05 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1655743025; bh=Fbn00eRTGk+1q+Lam7RSYyxyIYlymAFvXCVsjYoJYzI=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=wfMWGcq2qbxYf/4l0CQITEnpYNp1GGOKsx0Q0e8rOmSlovrj7BdSVVjul0WD37vFJ umZ2qWf/nq0c8U0J8BWjOE2D1hG90ehCQH4Z4qMTwAanyH1SjnlCxUeIQNhV3ar3sG JO+5nlhovkzf5rWKoc4vfT5JJcm4EnSXpcZcGZ3ylv1kEvKmF9tx57WLGs+KzWGJv+ GJKH6f+4nGJFJw2Z2fJel66iiJic0UXTyOLm5R/ZakZ4JUt2FjfmAwU2D81j3pXfs0 daHqA+g35WFscHooefnjewEeznr3enHyO48XtjEC8zf3//oy8/AgBtGnwAxFnNhm+X fmvR5sMK3CHqw==
From: bruno.decraene@orange.com
To: Greg Mirsky <gregimirsky@gmail.com>
CC: Tony Li <tony.li@tony.li>, "Zafar Ali (zali)" <zali@cisco.com>, "mpls@ietf.org" <mpls@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
Thread-Topic: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators
Thread-Index: AQHYhMFvbByd4Y31YEOzBMMeaOtS0a1YfJ+Q
Date: Mon, 20 Jun 2022 16:37:05 +0000
Message-ID: <12072_1655743025_62B0A231_12072_496_1_bac2dc28194a40239816b27f1e2dca12@orange.com>
References: <6e5c6fa9-539f-80c3-7c92-5b97ad67560c@pi.nu> <447_1654704927_62A0CB1F_447_309_1_1f59cd955500419a988e2218a3f2246e@orange.com> <9F79E3D5-7ACE-4D15-83D7-8BF3FF60F671@gmail.com> <C9D1FD4A-2549-49C0-8904-84E3F559E85C@cisco.com> <988F5CAF-1A12-4209-92B5-B9AE75477B5C@tony.li> <4D3BA352-6E89-489D-A849-2B72A5D0DC1F@cisco.com> <1F0A4345-C258-4BE6-92D4-C846C0B77048@tony.li> <7111_1655456559_62AC432F_7111_124_1_196adfdc44ba4f44bd7e59deb7e6410a@orange.com> <CA+RyBmWVnt0V=MD=P-ieGB0iKCibF=ctn-rCVFEVyveXwOMAHA@mail.gmail.com> <25852_1655484843_62ACB1AB_25852_28_1_7229e1a9bb9a4920b5e6f0c5fc3e445c@orange.com> <CA+RyBmUvyvaL+LSynNhBtNKz=_uC4Uy8z19rikA+zOGn8Z0aZw@mail.gmail.com> <24410_1655739516_62B0947C_24410_315_1_f9eb9e59046d4b809385eaeabd26d323@orange.com> <CA+RyBmUWPSkhhVK1Bg4EUt_M0AU5TXY_iXAN-zJXLQYQcr3S=A@mail.gmail.com>
In-Reply-To: <CA+RyBmUWPSkhhVK1Bg4EUt_M0AU5TXY_iXAN-zJXLQYQcr3S=A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Enabled=true; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SetDate=2022-06-20T16:37:03Z; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Method=Standard; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_Name=Orange_restricted_external.2; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ActionId=5da3911a-1a3b-4368-b0ce-2043179a89a6; MSIP_Label_f47c794b-e3ab-43f0-9e0f-29fc3e503192_ContentBits=2
x-originating-ip: [10.115.27.53]
Content-Type: multipart/alternative; boundary="_000_bac2dc28194a40239816b27f1e2dca12orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/c0PEaguG_68kkeNo5Uo1Saekj5M>
Subject: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jun 2022 16:37:14 -0000
Hi Greg, From: Greg Mirsky <gregimirsky@gmail.com> Sent: Monday, June 20, 2022 6:19 PM To: DECRAENE Bruno INNOV/NET <bruno.decraene@orange.com> Cc: Tony Li <tony.li@tony.li>; Zafar Ali (zali) <zali@cisco.com>; mpls@ietf.org; pals-chairs@ietf.org; mpls-chairs@ietf.org; DetNet Chairs <detnet-chairs@ietf.org> Subject: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators Hi Bruno, thank you for the clarification, that helps a lot. From the perspective of MNA requirements, I'd imagine that supporting the association of meta-data with MNAI is essential and any proposal we adopt must have it. If that is the case, what is the role of a stand-alone document that is limited to EL and Slice-ID? Why wouldn't it be a section of a document that addresses all the MNA requirements? Why would all components of the solutions (e.g. indicators, post-stack data, in-stack data) would need to be defined in a single document? And even assuming a single "document that addresses all the MNA requirements", why would that document could not reference other documents for some components? At this point of editorial comments, I guess that you don't have further technical comments on draft-decraene-mpls-slid-encoded-entropy-label-id. Regards, --Bruno Regards, Greg On Mon, Jun 20, 2022 at 8:38 AM <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> wrote: Hi Greg, Please see inline [Bruno] From: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> Sent: Friday, June 17, 2022 9:56 PM Hi Bruno, thank you for the expedient response. If I understand you correctly, PSD can be used as part of draft-decraene-mpls-slid-encoded-entropy-label-id. [Bruno] I would phrase it differently: - draft-decraene-mpls-slid-encoded-entropy-label-id can be used to carry 8 indicators in the stack while being usable with existing LSP Egress (more indicators would require extension on the LSP egress) - one of these indicators may be used to indicate the presence of PSD. The format/solution for PSD is orthogonal; one example being https://datatracker.ietf.org/doc/html/draft-jags-mpls-ext-hdr-00#section-5 Regards, --Bruno If that is the case, I think adding more information on how PSD can be used by the mechanism described in draft-decraene-mpls-slid-encoded-entropy-label-id would be helpful. Regards, Greg On Fri, Jun 17, 2022 at 9:54 AM <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> wrote: Hi Greg, Please see inline [Bruno] From: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> Sent: Friday, June 17, 2022 5:46 PM To: DECRAENE Bruno INNOV/NET <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> Cc: Tony Li <tony.li@tony.li<mailto:tony.li@tony.li>>; Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>; mpls@ietf.org<mailto:mpls@ietf.org>; pals-chairs@ietf.org<mailto:pals-chairs@ietf.org>; mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>; DetNet Chairs <detnet-chairs@ietf.org<mailto:detnet-chairs@ietf.org>> Subject: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators Hi Bruno, you've said that your proposal allows for up to 8 MNA indicators. How do you envision the encoding of data associated with these indicators? [Bruno] Two paths : - post stack data. - in-stack data located after the ELI, EL e.g. as proposed in draft-jags-mpls-ext-hdr (but different encoding would also work) At this point, post-stack data is probably my preference as the use of the label stack is already specified/used hence brings constraints. Regards, --Bruno Re-use the EL space? Or these can be only no-data MNAIs? Regards, Greg On Fri, Jun 17, 2022 at 2:03 AM <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> wrote: Tony, Orange Restricted Orange Restricted Orange Restricted Orange Restricted From: Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>> On Behalf Of Tony Li Sent: Friday, June 17, 2022 5:26 AM To: Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>> Cc: Kireeti Kompella <kireeti.ietf@gmail.com<mailto:kireeti.ietf@gmail.com>>; DECRAENE Bruno INNOV/NET <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>; mpls@ietf.org<mailto:mpls@ietf.org>; pals-chairs@ietf.org<mailto:pals-chairs@ietf.org>; mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>; DetNet Chairs <detnet-chairs@ietf.org<mailto:detnet-chairs@ietf.org>> Subject: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators Zafar, Again, my problem with Bruno's draft is that the limited space found in the ELI/EL LSE's is clearly insufficient to begin to capture the use cases that we already can foresee for MNA, much less provide any room for growth. It doesn't scale. We need more bits. [Bruno] Thank you for providing a technical argument. draft-decraene-mpls-slid-encoded-entropy-label-id provides 8 indicators while being backward compatible with existing egress/signaling. If more are required, solution can be extended to provide more indicators (and data) but at the cost of requiring new dataplane feature on the LSR egress (and new signaling). Just like the proposals using a new SPL. The net benefit is that in the short/medium term more devices/deployments can start using those 8 indicators, while waiting for the new generation to support the new proposal. Regards, --Bruno For that reason alone, Bruno's draft is not a tenable solution to MNA and discussing it further is pointless. Tony On Jun 16, 2022, at 7:32 PM, Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>> wrote: Tony, Kireeti, So "I do not want to modify my current implementation" is the argument to stop people interested in Bruno's draft from using it? If such HW can/ need be modified to implement the new complex encoding scheme you proposed, why it cannot implement simple encoding in Bruno's draft? Please also look at https://datatracker.ietf.org/doc/html/draft-decraene-mpls-slid-encoded-entropy-label-id-04#section-4.4 and https://datatracker.ietf.org/doc/html/draft-decraene-mpls-slid-encoded-entropy-label-id-04#section-4.5 Thanks Regards ... Zafar From: Tony Li <tony1athome@gmail.com<mailto:tony1athome@gmail.com>> on behalf of Tony Li <tony.li@tony.li<mailto:tony.li@tony.li>> Date: Thursday, June 16, 2022 at 3:10 PM To: "Zafar Ali (zali)" <zali@cisco.com<mailto:zali@cisco.com>> Cc: Kireeti Kompella <kireeti.ietf@gmail.com<mailto:kireeti.ietf@gmail.com>>, "bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>" <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>>, "mpls@ietf.org<mailto:mpls@ietf.org>" <mpls@ietf.org<mailto:mpls@ietf.org>>, "pals-chairs@ietf.org<mailto:pals-chairs@ietf.org>" <pals-chairs@ietf.org<mailto:pals-chairs@ietf.org>>, "mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>" <mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>>, DetNet Chairs <detnet-chairs@ietf.org<mailto:detnet-chairs@ietf.org>> Subject: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators The draft has been implemented for the exact (SLID) use-case on hardware platforms based on Broadcom Jericho2 family of ASIC Please take a look at https://datatracker.ietf.org/doc/html/draft-decraene-mpls-slid-encoded-entropy-label-id-04#section-7 No such issue was noted And Jericho2 is the only thing that counts in the entire world? T _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ mpls mailing list mpls@ietf.org<mailto:mpls@ietf.org> https://www.ietf.org/mailman/listinfo/mpls _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- [mpls] Poll 2: New SPL vs re-purposed ELI for car… Loa Andersson
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Gyan Mishra
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Joel Halpern
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… UTTARO, JAMES
- Re: [mpls] [EXTERNAL] Re: Poll 2: New SPL vs re-p… Alexander Vainshtein
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Dongjie (Jimmy)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Kireeti Kompella
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Jeffrey (Zhaohui) Zhang
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Adrian Farrel
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Adrian Farrel
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Mach Chen
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Rakesh Gandhi
- Re: [mpls] [E] RE: Poll 2: New SPL vs re-purposed… Jalil, Luay
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Weiqiang Cheng
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Kireeti Kompella
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tianran Zhou
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Gyan Mishra
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tianran Zhou
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Tony Li
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Zafar Ali (zali)
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Robert Raszuk
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… Greg Mirsky
- Re: [mpls] Poll 2: New SPL vs re-purposed ELI for… bruno.decraene