Re: [mpls] mail on ISD encodding

Tony Li <tony.li@tony.li> Tue, 12 March 2024 04:58 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 A43CCC14F682; Mon, 11 Mar 2024 21:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.509
X-Spam-Level:
X-Spam-Status: No, score=-1.509 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.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 gCGDZfVQp9E6; Mon, 11 Mar 2024 21:58:25 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 9D137C15106A; Mon, 11 Mar 2024 21:58:20 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id d9443c01a7336-1dd84ecfc47so14953515ad.1; Mon, 11 Mar 2024 21:58:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710219500; x=1710824300; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=FohW3uJXJgIOUIC2r7hAHIhc1CN+hHBFlJmy9uQVtzo=; b=PaiYAiop1fXEQAspoWzqxmY25qWkyosLBW61EmiWCPQNdf78xMpAdHxSDKjwOLYYma 1jqfxNiVtCMIeQ1z4mtnSEhWJ70EkoqBqO95D1De3M4/XOlcJIqbZRNtI0llOP1FbCuH VdWJhVoM5CWCzuLnLtTCFU+Ol9DGZFtb4cavRvsIrsnrO3crtqIMUPJdoUrr+/xMA0BS OYA4qR7b6DWd7nRvykMROq4TrfXCG+gNHNUSO4DmGSxYL6KerGRp6lacqhM13oUwkwP8 8MLY62jTPgZKTUQkO1KifZ5c5m9c/79+fen2Ei1axmjR6+VGYVUcC8tS+30FzRnkLmzz wLjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710219500; x=1710824300; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=FohW3uJXJgIOUIC2r7hAHIhc1CN+hHBFlJmy9uQVtzo=; b=TZvnA37Yup3/7wt2hZtVRgb18VG1oOOP3Dd6Z+oYzqDqqw49oRNyuXxPqh1b3V67LV y8HUxLIJWRyPjrB7Fiq0Dy+g+H/dwpaCG7mqFx9ZR6QDbFOZgscW6M6dOq/1hg6zWYK9 RqSRHMJKt4tOLLyj8fK4LcMNufFkWgx+H79phr8qHTw4UbTuwkuvZGj2agwVABAR5hLI PWW0srNkinWDVBfhfigs0JRc3uNomoXYVhczVX7FGahPIGvM1ed9ouJ4eNxhbRmT3/if QP6fhqRKKzLWplqm9wpfKm3/n8MFw7kxr11AdSmB/Yzrdm0B+fxMXjcjKGYW829xFi+W 7fcg==
X-Forwarded-Encrypted: i=1; AJvYcCWr/V6ECekL03X0nmECXMH6uVlW/itEP2dmTukFJYWeUB4sTQ22gK3bltlPQg78UoSmQJ06EOnB9HXkTlMwmrcg/93KhuCgF/ko5OaqzZCrQ3u9XelG7r8IohIUwlu43g==
X-Gm-Message-State: AOJu0YzxZkNgx82IozgodDG/J7gdnxQwQJuQsywYv9aHDHVGu1BoZMaR SotS42F3tAEUQa2vMNvb/M1hQyJXgsFKjEWbiPpYnzhXhhs5r+yI
X-Google-Smtp-Source: AGHT+IGXXBPazKsRIZ1ahgkpvVOwLnPEnQ5aoPD197yk9ZJcpQ0JZl89HDJOwtVwX/gZxOJCw4Ifcg==
X-Received: by 2002:a17:902:da86:b0:1dd:76e0:a19a with SMTP id j6-20020a170902da8600b001dd76e0a19amr668434plx.34.1710219499809; Mon, 11 Mar 2024 21:58:19 -0700 (PDT)
Received: from smtpclient.apple (c-73-158-206-100.hsd1.ca.comcast.net. [73.158.206.100]) by smtp.gmail.com with ESMTPSA id k8-20020a170902c40800b001dca9b21267sm5600403plk.186.2024.03.11.21.58.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Mar 2024 21:58:19 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Tony Li <tony.li@tony.li>
X-Priority: 3 (Normal)
In-Reply-To: <028fd6bc5f68b201de7749fff654dfb0.squirrel@pi.nu>
Date: Mon, 11 Mar 2024 21:58:08 -0700
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "draft-ietf-mpls-mna-hdr@ietf.org" <draft-ietf-mpls-mna-hdr@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E1B6D5A-D9E4-4EDB-8BDD-8F6ACE706488@tony.li>
References: <62ae3e9892a9ff01f67d13e40a0a8f74.squirrel@pi.nu> <3F70B458-AEBE-4950-B721-A19BF2C2C8D7@tony.li> <457af2ed166e9f886d9966ed872bb1e7.squirrel@pi.nu> <4C50D0C5-0591-4D11-A531-C2237243768C@tony.li> <1ed6fa19af1fb4947068cdf40eb0b223.squirrel@pi.nu> <AB864AB0-CFBA-40AD-B2F7-6A807479E7B4@tony.li> <9f461dae2006b484a27a82ba650dac85.squirrel@pi.nu> <8369752E-0133-4F7B-9D2B-82A210F66567@tony.li> <2efd1677f0bae7abf6d7df260f0beafd.squirrel@pi.nu> <4CD54316-3715-4B57-A4A6-F3F4E7AE3ED9@tony.li> <973B7D13-A77A-47DB-9FED-9EBB0D403FFA@gmail.com> <e439ebbc51f6c41285892f9d5b7328d5.squirrel@pi.nu> <4DAC5095-2359-40BA-8AE0-DCCE9C8F6FB0@tony.li> <085a8d103a9a42549398d22ef5f9d7aa@huawei.com> <1C428D73-D8E0-4432-A3D8-59D788114318@tony.li> <028fd6bc5f68b201de7749fff654dfb0.squirrel@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/bu-7ziPYWuGUEGjXjH-vsAcEv8A>
Subject: Re: [mpls] mail on ISD encodding
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, 12 Mar 2024 04:58:26 -0000

[WG chair hat: off]

Hi Loa,


> So you mean we should first break what is not broken, then "steal a bit"
> for the U-bit, that was there from the start?


I don’t understand this comment.  

As your original example showed, we currently cannot attach Format D LSEs after Format B LSEs.  I proposed one way of allowing that, which would hopefully make some common cases more efficient as there would be fewer cases where there would be a NOP opcode in the Format B LSE.

You objected to my proposal saying that we should have at least one reserved bit. I’m fine with that, we can simply take one more bit from the Format B data space.


> Or did you mean steal for
> the p-bit which also seems unnecessary, since the R-bit sits there in
> draft-ietf-mpls-mna-hdr, and draft-jags-mpls-ps-mna-hdr nicely allocates
> it as a p-bit? How about just leaving the bit allocation as is?


I cannot follow this at all.

In any case, I take it that you dislike my proposal. That’s fine.


> However, there is one thing about where the allocations are done.
> 
> The p-bit is one of the ISD-flags, it points at OSD, but it is really a
> piece of the ISD. Should be allocated in the draft-ietf-mpls-mna-hdr.


I disagree.  As I mentioned, in the ISD header, that should simply be a reserved bit.  It should not be assigned for PSD.  We may never use PSD. It would be poor engineering to prevent its use in perpetuity.  If we do not use PSD, then that reserved bit might be pressed into service for some other purpose.

Flexiblity in future design would seem to be an overriding principle here.


> Also the instruction (for R-bit), "set to zero when sending and ignore
> when received" is problematic. Let us forget about the R-bit and put the
> p-bit where it belongs. There should be a description of how
> a non-PSD capable node treats a packet with the p-bit set.


I disagree.  That is how we always deal with reserved bits.

There is no point in arguing about PSD and non-PSD nodes until we decide to commit to PSD.

Tony