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

Weiqiang Cheng <chengweiqiang@chinamobile.com> Tue, 14 June 2022 08:43 UTC

Return-Path: <chengweiqiang@chinamobile.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 E0E0BC1649D1; Tue, 14 Jun 2022 01:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=ham autolearn_force=no
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 VV4DboXcMlX1; Tue, 14 Jun 2022 01:43:38 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id EEC4BC1649C1; Tue, 14 Jun 2022 01:43:36 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.15]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee262a84a356d1-2f544; Tue, 14 Jun 2022 16:43:35 +0800 (CST)
X-RM-TRANSID: 2ee262a84a356d1-2f544
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[10.2.54.108]) by rmsmtp-syy-appsvr08-12008 (RichMail) with SMTP id 2ee862a84a3583a-9ff69; Tue, 14 Jun 2022 16:43:34 +0800 (CST)
X-RM-TRANSID: 2ee862a84a3583a-9ff69
From: Weiqiang Cheng <chengweiqiang@chinamobile.com>
To: "'Zafar Ali (zali)'" <zali@cisco.com>, 'Loa Andersson' <loa@pi.nu>, mpls@ietf.org
Cc: mpls-chairs@ietf.org, pals-chairs@ietf.org, 'DetNet Chairs' <detnet-chairs@ietf.org>
References: <6e5c6fa9-539f-80c3-7c92-5b97ad67560c@pi.nu> <998A24B2-6938-4402-B0AF-A2DFF4A60EA6@cisco.com>
In-Reply-To: <998A24B2-6938-4402-B0AF-A2DFF4A60EA6@cisco.com>
Date: Tue, 14 Jun 2022 16:43:32 +0800
Message-ID: <01e001d87fca$d47aab40$7d7001c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHYdGtSVPd1R0hyFkiAw3Z/WCl3ra1BgRiAgA0oc0A=
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/pYSfLPzvW0iMPwPQuB6afmB6TG0>
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: Tue, 14 Jun 2022 08:43:41 -0000

Hi,
I reviewed the draft draft-decraene-mpls-slid-encoded-entropy-label-id. It looks feasible and efficient.
I agree with Ali that we can consider to progress the draft.

B.R.
Weiqiang Cheng

-----邮件原件-----
发件人: Zafar Ali (zali) [mailto:zali@cisco.com] 
发送时间: 2022年6月6日 11:36
收件人: Loa Andersson; mpls@ietf.org
抄送: mpls-chairs@ietf.org; pals-chairs@ietf.org; DetNet Chairs; Zafar Ali (zali)
主题: Re: [mpls] Poll 2: New SPL vs re-purposed ELI for carrying Network Action Indicators

Dear chairs and the WG: 

I feel, we need to qualify the scope of the “(2) re-purposing the ELI SPL” question 
I.e., we need to answer the poll from a short term perspective and the long term view

As discussed during the PALS session at IETF113, https://datatracker.ietf.org/doc/draft-decraene-mpls-slid-encoded-entropy-label-id/ meets our immediate needs; thanks to the following attributes: 
* Hardware efficient 
    + It minimized the label stack (EL is used for both the load-balancing and the immediate additional use-cases with "8" indicators) 
* Enables faster and incremental deployments 
    + Thanks to wide support of ELI on current HW
    + Preserves the backward compatibility (with legacy devices) 
* Reuses control plan 
    + Does not require extensions to signal support (in BGP, ISIS, OSPF, BGP-LS, LDP, RSVP-TE, etc.)

In summary, IMO the progression of draft-decraene-mpls-slid-encoded-entropy-label-id as the “starting” point should not be mixed up with the question in this poll

Thanks

Regards … Zafar
 

On 5/30/22, 5:22 PM, "mpls on behalf of Loa Andersson" <mpls-bounces@ietf.org on behalf of 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