Re: [mpls] Poll on way forward for MNA solution

Greg Mirsky <gregimirsky@gmail.com> Tue, 13 September 2022 12:24 UTC

Return-Path: <gregimirsky@gmail.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 D4AEAC15791D for <mpls@ietfa.amsl.com>; Tue, 13 Sep 2022 05:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQOhMYf0bFSo for <mpls@ietfa.amsl.com>; Tue, 13 Sep 2022 05:23:56 -0700 (PDT)
Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 48F87C14CF12 for <mpls@ietf.org>; Tue, 13 Sep 2022 05:23:56 -0700 (PDT)
Received: by mail-lf1-x133.google.com with SMTP id k10so19786025lfm.4 for <mpls@ietf.org>; Tue, 13 Sep 2022 05:23:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=P7CMSRKHj+CfAAsaRnpwZ5glq5fqfxbbu+O1cc5M0Ww=; b=kSroSbq1kKfaNiJBegQ94Aes1XaDx4gf3b7cECi4PnE7YkGzphz4Xtfwgzo2vs+OLo A3kIbRjxuHYPdvlfF8JMm3Cj6LnnkLZPqjAdfqEPhPph2WB0xPD/acxcr2wNOfwvZksF 9IJZM/k9h8G0JtA4ejCJX2+NZDppHdY5JdJBgXu59yd7erJ9En9cBdkB3M3obtpPHZRO SXuJbKwdNXxyr/Tn/bJXncY7i7+SYusCDzuQZzSHpjoF76eOSAxR+6vZso3li27AHR67 cF6Oc3+b5CCksnCTYCpvBXYNOh6TAQxM5QBPbk0Xy4THG5PlkRYJMVzCrTZmUjPHg4FG I0qA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=P7CMSRKHj+CfAAsaRnpwZ5glq5fqfxbbu+O1cc5M0Ww=; b=Wu6BSNKUCz8bWccqBEJGhqS9dPxLksv5L8f7rBmYHBXVSBYXDfR8KCAMT83jkZWj0H ipN5CwZuB5da0q6S8lT8HqFLO1g8Dm/8hwZNPvsu2tYhj1Pl1ugyk9qLDa7S2WtNv8I3 hvtWl9b4CY13IpagS4yGG7IwDbuWWBW1iYabRibf7aWL9bhrOGVPOq9Dr+v56NFt1DPJ 2Lx0mPNcpWNFR3tNUnzebTuSeVQRIVMPZxGTK2mW1VVwdCfXRX85WvjG6l+AWk/Nxg24 C67mvO3Hdtx9VgyOfYCRrYrSo8DR/Jkfomc0I3siUr5fXTaOtY/Ji8V6FwhqaxmCdrLr KIzA==
X-Gm-Message-State: ACgBeo0C62HQCV6Kz6vOu9815R27NvFUaUVHmubxmxKWFqxVA79oreDm RE1QltVVnd8dBbCAb5H5zIJ7Yvp3rTL8vcztjSxNgJI+REa7PnlU
X-Google-Smtp-Source: AA6agR46QC75dNU1QLbAAj88DDPkJuuXd9G/yxck8iKOISDVBGHau1V3PDq5saSyPfz9j3/Gu7VQulciDWFRAvFvt+0=
X-Received: by 2002:a05:6512:706:b0:498:b7ea:f2e8 with SMTP id b6-20020a056512070600b00498b7eaf2e8mr8621556lfs.570.1663071834513; Tue, 13 Sep 2022 05:23:54 -0700 (PDT)
MIME-Version: 1.0
References: <7c419233-7cba-1bb0-740d-34e09f149efe@pi.nu> <DS0PR19MB650143C4F4C1B9BF3E60C888FC7A9@DS0PR19MB6501.namprd19.prod.outlook.com> <bc67ab72-e36c-cd5f-27aa-0441c4ee093c@pi.nu> <DS0PR19MB65019CECC654037542FC2588FC7E9@DS0PR19MB6501.namprd19.prod.outlook.com> <VI1PR0701MB6991B4A8EEEB56202E4D377AEB439@VI1PR0701MB6991.eurprd07.prod.outlook.com> <CAPOsKjFMbqbwMt5ETzTr_zbdk7r8ApkMsHwdo0UiQFFey++=Ww@mail.gmail.com> <BL3PR11MB57310626CD47E373E9FD745BBF449@BL3PR11MB5731.namprd11.prod.outlook.com> <0459ad6f-958c-4cd3-2668-a0a88bf1d11d@joelhalpern.com> <BL3PR11MB5731155791027C8154EB4B2CBF449@BL3PR11MB5731.namprd11.prod.outlook.com> <3a6fb958-42f8-7293-ce7b-2cecf59ed3ca@joelhalpern.com> <BL3PR11MB5731A884F6E9325BD265AE0BBF449@BL3PR11MB5731.namprd11.prod.outlook.com> <CA+RyBmWWnGstWW2GqLvdEgW3fEj1qx9S5VD+h3WAO25E3hJjbw@mail.gmail.com> <BL3PR11MB573183CEF976F54E10D4E423BF479@BL3PR11MB5731.namprd11.prod.outlook.com> <CAPOsKjE9OsCUeiW-5fEb6-VERHuvv7CWk3B7CxNftJDPSwbtRg@mail.gmail.com>
In-Reply-To: <CAPOsKjE9OsCUeiW-5fEb6-VERHuvv7CWk3B7CxNftJDPSwbtRg@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 13 Sep 2022 14:23:43 +0200
Message-ID: <CA+RyBmWPcDiSd4dfh43N8Xu1i6SHs8VG817AKfemfZmvvPgNyw@mail.gmail.com>
To: Jaganbabu Rajamanickam <jaganbaburietf@gmail.com>
Cc: "Rakesh Gandhi (rgandhi)" <rgandhi=40cisco.com@dmarc.ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eea6ab05e88e159b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/LjTRR8a8aOlbUqJMXY3RtYgRVGY>
Subject: Re: [mpls] Poll on way forward for MNA solution
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: Tue, 13 Sep 2022 12:24:00 -0000

Hi Jag,
thank you for your response, though that is not what I was expecting. As I
understand, there are two options in the question asked by the WG Chair. In
your response, you've indicated your support of Option B . That, in
my opinion, contradicts the "support a single solution" position, as the
Option B, in my understanding, is to standardize one or more solutions. Is
that your intention? Further, I cannot understand "We do not support the DT
team bringing forward another solution from the piece of work which has
been already done". Is that you command the Open DT to cease and desist any
work on a solution other than yours?

Regards,
Greg



On Tue, Sep 13, 2022 at 2:16 PM Jaganbabu Rajamanickam <
jaganbaburietf@gmail.com> wrote:

> Hello Greg,
>    I agree with Rakesh and Xiao Min.
>     We support progressing the draft-jags-mpls-mna-hdr as a single
> solution.
>     We do not support the DT team bringing forward another solution from
> the piece of work which has been already done.
> Thanx,
> Jags
>
> On Tue, Sep 13, 2022 at 8:09 AM Rakesh Gandhi (rgandhi) <rgandhi=
> 40cisco.com@dmarc.ietf.org> wrote:
>
>> Hi Greg,
>>
>> We support one solution for MNA.
>>
>> And we support progressing the draft-jags-mpls-mna-hdr as that solution.
>>
>> And we do not support DT team bringing forward another solution.
>>
>>
>>
>> Thanks,
>>
>> Rakesh
>>
>>
>>
>>
>>
>>
>>
>> *From: *Greg Mirsky <gregimirsky@gmail.com>
>> *Date: *Tuesday, September 13, 2022 at 1:57 AM
>> *To: *Rakesh Gandhi (rgandhi) <rgandhi@cisco.com>
>> *Cc: *Joel Halpern <jmh@joelhalpern.com>, Tarek Saad <tsaad.net@gmail.com>,
>> mpls@ietf.org <mpls@ietf.org>
>> *Subject: *Re: [mpls] Poll on way forward for MNA solution
>>
>> Dear Jag, Rakesh, and Xiao Min,
>>
>> I feel confused. The way I understood the pool's question is whether the
>> group supports standardizing a single solution document or whether each of
>> proposed solutions can be standardized (WG Chairs, please correct me if I
>> misunderstood your question). From your previous emails, it appears that
>> you support the latter - possibly standardizing multiple data plane
>> solutions. Could you please clarify. Also, I don't find in the poll
>> question about which of the solutions, already proposed or to be proposed
>> soon, to be standardized. It seems like being disciplined and following the
>> scope of the questions will help us progress this work faster.
>>
>>
>>
>> Regards,
>>
>> Greg
>>
>>
>>
>> On Tue, Sep 13, 2022 at 12:34 AM Rakesh Gandhi (rgandhi) <rgandhi=
>> 40cisco.com@dmarc.ietf.org> wrote:
>>
>> Hi Joel,
>>
>>
>>
>> Yes, one solution. And we support progressing the draft-jags-mpls-mna-hdr
>> as that solution.
>>
>>
>>
>> Thanks,
>>
>> Rakesh
>>
>>
>>
>>
>>
>> *From: *Joel Halpern <jmh@joelhalpern.com>
>> *Date: *Monday, September 12, 2022 at 5:53 PM
>> *To: *Rakesh Gandhi (rgandhi) <rgandhi@cisco.com>, Tarek Saad <
>> tsaad.net@gmail.com>
>> *Cc: *mpls@ietf.org <mpls@ietf.org>
>> *Subject: *Re: [mpls] Poll on way forward for MNA solution
>>
>> Then we agree that we want only one solution.
>>
>> I read the poll as being agnostic on the question of what the one
>> solution would look like.  Given that there are at least two solutions that
>> seem to work (and are now quite similar) on the table, I would expect a
>> fairly typical process for getting to one good solution.
>>
>> Yours,
>>
>> Joel
>>
>> On 9/12/2022 5:50 PM, Rakesh Gandhi (rgandhi) wrote:
>>
>> Hi Joel,
>>
>>
>>
>> Thanks for your comments.
>>
>>
>>
>> Please see inline with <RG>..
>>
>>
>>
>> *From: *Joel Halpern <jmh@joelhalpern.com> <jmh@joelhalpern.com>
>> *Date: *Monday, September 12, 2022 at 5:41 PM
>> *To: *Rakesh Gandhi (rgandhi) <rgandhi@cisco.com> <rgandhi@cisco.com>,
>> Tarek Saad <tsaad.net@gmail.com> <tsaad.net@gmail.com>
>> *Cc: *mpls@ietf.org <mpls@ietf.org> <mpls@ietf.org>
>> *Subject: *Re: [mpls] Poll on way forward for MNA solution
>>
>> The phrasing in this sub-thread of messages seems a bit odd to me.
>>
>> Are you folks really saying you want to see two (or more) different
>> solutions for MNA?  That seems highly undesirable.
>>
>> <RG> We are saying - progressing the draft-jags-mpls-mna-hdr as a
>> “single” MNA solution.
>>
>> <RG> Definitely *not* two or more different solutions for MNA.
>>
>> I read the poll as choosing between one solution and many solutions.  You
>> seem to be saying you read the poll as being between crafting something new
>> and having multiple solutions??
>>
>> <RG> We are saying - progressing one solution only, which is defined in
>> draft-jags-mpls-mna-hdr.
>>
>> Thanks,
>>
>> Rakesh
>>
>>
>>
>> Yours,
>>
>> Joel
>>
>> On 9/12/2022 3:50 PM, Rakesh Gandhi (rgandhi) wrote:
>>
>> Hi WG Chairs,
>>
>>
>>
>> I support option (B) as progressing the draft-jags-mpls-mna-hdr (that is
>> well-thought of by the co-authors) as a single solution for MNA.
>>
>>
>>
>> I do not support option (A) as new authors from the open DT team to take
>> pieces from the draft and submit a new document.
>>
>>
>>
>> Thanks,
>>
>> Rakesh
>>
>>
>>
>>
>>
>>
>>
>> *From: *mpls <mpls-bounces@ietf.org> on behalf of Tarek Saad <
>> tsaad.net@gmail.com>
>> *Date: *Tuesday, 6 September 2022 at 19:50
>> *To: *mpls@ietf.org <mpls@ietf.org>
>> *Cc: *mpls-chairs@ietf.org <mpls-chairs@ietf.org>, pals-chairs@ietf.org <
>> pals-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
>> *Subject: *[mpls] Poll on way forward for MNA solution
>>
>> Dear MPLS WG and MPLS Open DT,
>>
>>
>>
>> Over the past months, the MPLS Open DT has reviewed several proposals for
>> the packet encodings for the MNA solution.
>>
>> A compilation of the multiple solutions brought forward is present at
>> https://trac.ietf.org/trac/mpls/wiki/MNADocumnets.
>>
>>
>>
>> We believe that currently there are two alternative ways to progress the
>> MNA solution.
>>
>> One of them requires a single unified solution, and the other allows for
>> individual solutions to progress independently.
>>
>> We expect any unified solution to document the pieces from the presented
>> solutions that are discussed and agreed upon in the weekly MPLS Open DT
>> meeting.
>>
>>
>> The co-chairs for the working groups hosting the Open MPLS DT are polling
>> the WG on their preference to move forward.
>>
>> Please respond with either:
>>
>>
>>     A) “I support the MPLS Open DT bringing forward a single unified
>> solution"
>>
>>     OR
>>     B) “I support progressing the individual solution(s) independently"
>>
>>
>>
>> We will allow this poll to run for two weeks (ending on Sept 19th).
>>
>>
>>
>> Regards,
>>
>> Tarek (for the MPLS Open DT co-chairs)
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>>
>>
>> _______________________________________________
>>
>> mpls mailing list
>>
>> mpls@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>