Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators

Greg Mirsky <gregimirsky@gmail.com> Wed, 08 June 2022 15:51 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 C8D4BC14CF0F; Wed, 8 Jun 2022 08:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 6YJrAonfgUR8; Wed, 8 Jun 2022 08:51:51 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 E0F48C14F693; Wed, 8 Jun 2022 08:51:50 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id g25so23188139ljm.2; Wed, 08 Jun 2022 08:51:50 -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=M1a+7OIteSBYqykpSepD2qlg5lzBphu3kR7falyNlvE=; b=PovVB1K8wEPDYneKbuyNjoXKWxXZFFp3qJZQdIqPgC8vWmNY6CUzfyYOU5DXIKwaH/ 4RA89KRqBGdEZ7caD3qZXKej8Zggi8f9VQZlVysrCVtQDCLrADH/74Sqlzmou0d94Nd8 FqWJyO1mru/JLm89fUpUqbBN9+CKCEV2+X++EcOSJB7oOMk8bL5j7Vis56nb8aVeJfOJ ff4bkrKyOpDYQtrWy04jlGpq9KhZOJF5sv5Hah+tO7zdLeFHJh8Yp8YM/ZSkE3h7a3dm YoIoEhLH4S9dpJH2zfljZaKYgNBGzEhbv/k+YxhUsiT8kWTmpKqTFYTR6zdNn7Wa1fl5 YIog==
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=M1a+7OIteSBYqykpSepD2qlg5lzBphu3kR7falyNlvE=; b=Cy1jzIsm5DeLc74DP/9z44t4bZcZ21VoKspkxGlLof+p/9b/IzDxv7rdfsQkcIG02t Ye8PTRZfbFYHryjLtRkjvXxOOKtfRdUaS+OF0dLFWOUD/5WykW0lr8znPlKsLRGn+O/8 Tu4DY+PWv2kFtuxNsckbjQ2Gpdc8OJM2pamzEItFjd6eHwubl6ffkRHt+ZjPfHk2EzTu AdiDseUI8WOicjtHwTtVfTjM+O25Z/JtJBXlMgjs4UVOw092U90RTwgq+0vPtwt/WN9z jqmJyAjSgRXn22mOM2dF7HlDLQy4r3JDnKVT7/vn2JvEvop3PU2hRfhMPeu3KMSHY9PB DWEg==
X-Gm-Message-State: AOAM5339ChQ3aRQ360tvkEtVPtfhxpKcvx3oF4gxUnHCrZLhaL7V71Ig 5V7q/LU4rZROygfe0W4OtVS/OWMuF56x0fqYWB4=
X-Google-Smtp-Source: ABdhPJwGsu8Lz8laRDt61PETrgx2uT+XgLdd/gFCtoIQF3UI+BmqtVDT6SQ1cShMonJxcV4MRbhBaeqQONckHR3sjvo=
X-Received: by 2002:a2e:b0d0:0:b0:255:9be1:a472 with SMTP id g16-20020a2eb0d0000000b002559be1a472mr8365174ljl.453.1654703508775; Wed, 08 Jun 2022 08:51:48 -0700 (PDT)
MIME-Version: 1.0
References: <6e5c6fa9-539f-80c3-7c92-5b97ad67560c@pi.nu> <CA+RyBmXc6UQh9yGzVo2Fskvfz7XdroKiA8RKR3x7USS3pmxSHg@mail.gmail.com> <20261_1654703045_62A0C3C5_20261_169_1_5975e1f8053045cfbbd3052864912eed@orange.com>
In-Reply-To: <20261_1654703045_62A0C3C5_20261_169_1_5975e1f8053045cfbbd3052864912eed@orange.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 08 Jun 2022 08:51:35 -0700
Message-ID: <CA+RyBmXciFOUSOwR7X9Ago=91sJDFRrc8S3K1x2BbNqNiCGbsQ@mail.gmail.com>
To: Bruno Decraene <bruno.decraene@orange.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>, Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary="000000000000d969ff05e0f1aefb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/V85PZmH_6OFcwTLWB6Gq0Ee244U>
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: Wed, 08 Jun 2022 15:51:51 -0000

Hi Bruno,
thank you for pointing that out to me. I recall our earlier discussion
about this, and I feel that I need to clarify my position:

   - draft-decraene-mpls-slid-encoded-entropy-label-id, by itself, does not
   address the MNA requirements listed in
   draft-ietf-mpls-miad-mna-requirements
   - to address the MNA requirements using ELI, one needs to
   use draft-jags-mpls-ext-hdr
   - draft-jags-mpls-ext-hdr is not backward compatible with RFC 6790 and
   RFC 8662.

I hope that makes my point clearer. I greatly appreciate your questions and
comments.

Regards,
Greg

On Wed, Jun 8, 2022 at 8:44 AM <bruno.decraene@orange.com> wrote:

> Greg,
>
>
>
> Extending the ELI as per draft-decraene-mpls-slid-encoded-entropy-label-id
> does not break RFC 6790 nor RFC8662.
>
> If you believe that it does, please cites the sentences from both
> draft-decraene-mpls-slid-encoded-entropy-label-id and RFC/6790/8662 that
> would contradict each other or would be incompatible.
>
>
>
> Thank you,
>
> --Bruno
>
>
>
> *From:* mpls <mpls-bounces@ietf.org> *On Behalf Of *Greg Mirsky
> *Sent:* Tuesday, May 31, 2022 4:44 PM
> *To:* Loa Andersson <loa@pi.nu>
> *Cc:* mpls@ietf.org; mpls-chairs@ietf.org; pals-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
>
>
>
> Dear Loa, MPLS WG Chairs, Open DT, et al.,
>
> I believe that re-using ELI to address the requirements listed in
> draft-ietf-mpls-miad-mna-requirements will definitely break implementations
> of RFC 6790 and RFC 8662. Thus I oppose re-using ELI to indicate the
> presence of an MNA in a packet. I think that the specifics of the mechanism
> indicating the presence of an MNA should be discussed separately from the
> framework document.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Mon, May 30, 2022 at 2:21 PM Loa Andersson <loa@pi.nu> wrote:
>
> MPLS Working Group, MPLS Open DT,
>
> The MPLS Network Actions (MNA) framework requires a method of indicating
> the presence of a Network Action and any Ancillary Data.
>
> Is the consensus of the working group that we do this by:
>
>    (1) allocating a new SPL for Network Action Indicators?
>
>    (2) re-purposing the ELI SPL?
>
>    (3) using some other method of indicating this such as making it an
>        additional property of an ordinary label?
>
> Please respond to the MPLS WG mail list.
>
> Loa Andersson
> for the Open DT wg chairs
>
> --
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert                          loa.pi.nu@gmail.com
> Bronze Dragon Consulting             phone: +46 739 81 21 64
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
> Orange Restricted
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
>