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

Tony Li <tony.li@tony.li> Fri, 17 June 2022 13:41 UTC

Return-Path: <tony1athome@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 F39E3C14CF00; Fri, 17 Jun 2022 06:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.508
X-Spam-Level:
X-Spam-Status: No, score=-1.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 yQVMYg1z5vtx; Fri, 17 Jun 2022 06:41:56 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 C274AC15AAE3; Fri, 17 Jun 2022 06:41:56 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id q140so4093023pgq.6; Fri, 17 Jun 2022 06:41:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VZpsGVW6applDLbsWa4wm+2ZIIkw0VQDljdR6yEI8vk=; b=Y4ia/5pchlGN3VQoa5sk7tKyS2zMs4h93YM6aPSQy5Do7P8QepE+OxmNZIRIsBhHn3 p+8J99QL2mI/ggZWvopwQKzOEv2fdeZxI9pMRWEONZUVHdC0k1mDOg2GVIQCSLHEAVc8 7c3LW0VP+vTUzIJZu+/rVkeiHo9X6gLZLhB1XIKn7WK1UGxuV98CrOYY1Fv66T62uPH9 KOwgbhWvVeZ16LhlOQEf40N9Z19iPFDFbEyL9bixmBFsfvAq//+KLgKdS4uk6xbFyv33 ++oCrjpuE7+9Kizd0vGXLOUrW04AobxSbSaaM6uBRBATS7aUJmtCiIoJrDukWS9GjtGo yjsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VZpsGVW6applDLbsWa4wm+2ZIIkw0VQDljdR6yEI8vk=; b=ZfkZN0xLfQpCuXPb28nD0qOYd+ohBsIfas6MSMsLWQD81PsbCADdstyRhMMfF32SHD IY1+/g8PP1f8zteBvKZ4w84eYPq9aZjmGLtKzit+WZc30+WqpxSCumtMK3LAQ7HyR7QQ yEmzi9BoQ+6mLfZhewKsTFadJ/9l91B16aDEOP8UhM53aYGlUCIDeowCtLHEJnLOabtq heBygwDSCaAIEmewDNTkR9cmIE1o7mEon8q/HVBw7DZ+byqSKx2m2klaEgjw5Viyiisp urMLUo1MYjsrvL+csdSHJQntqW54tVGnwlnqQ7t5BaY7FIQYiqLgqm2ltJB8oNpkAlzR q9hg==
X-Gm-Message-State: AJIora8cCb0/xahKg2CM2maXr4Jr+NIuCs9+gk1rpEG1nOeEvgRejnjy leHiLOm6vodOYdiBT9nCeGs=
X-Google-Smtp-Source: AGRyM1s8WSKM3eR/w97xg2KWugq6abutHpVRrZpHBcajaxTn038HuPN6UkKBPk2POFlZiPrJATCarA==
X-Received: by 2002:a63:9d41:0:b0:40c:67af:1fed with SMTP id i62-20020a639d41000000b0040c67af1fedmr534218pgd.185.1655473316090; Fri, 17 Jun 2022 06:41:56 -0700 (PDT)
Received: from smtpclient.apple (c-67-169-103-239.hsd1.ca.comcast.net. [67.169.103.239]) by smtp.gmail.com with ESMTPSA id i3-20020a63a843000000b003fd7e217686sm3846539pgp.57.2022.06.17.06.41.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Jun 2022 06:41:54 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <CB42DAF5-9E23-4F41-BF3D-9945A6274921@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8F074B1C-F1BA-438A-8F63-6A8F7BBB9F01"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Fri, 17 Jun 2022 06:41:53 -0700
In-Reply-To: <7111_1655456559_62AC432F_7111_124_1_196adfdc44ba4f44bd7e59deb7e6410a@orange.com>
Cc: "Zafar Ali (zali)" <zali@cisco.com>, Kireeti Kompella <kireeti.ietf@gmail.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>
To: bruno.decraene@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>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/yysTKq9Lq1Jor3MtyVboLCozGfk>
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: Fri, 17 Jun 2022 13:41:59 -0000

Bruno,

> 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.


And, contrary to that old TV show, 8 is not enough. :)


> 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.


But then you would run afoul of extending the ELI with one or more LSEs. And that’s much more scary because now you’re risking legacy devices misinterpreting the additional LSE’s. We’ve discussed this, it’s the same problem with Jags’ draft.


> 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.


So we pay twice? Why not just have one solution?

The only thing we’re really waiting for is for people to stop arguing.

Tony