Re: [mpls] mail on ISD encodding

loa@pi.nu Tue, 12 March 2024 03:56 UTC

Return-Path: <loa@pi.nu>
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 20922C14F699; Mon, 11 Mar 2024 20:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 bp0D1DCtitvo; Mon, 11 Mar 2024 20:56:04 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD47AC14F609; Mon, 11 Mar 2024 20:56:01 -0700 (PDT)
Received: from pi.nu (localhost.localdomain [127.0.0.1]) by pipi.pi.nu (Postfix) with ESMTP id D785C3A8F49; Tue, 12 Mar 2024 04:55:58 +0100 (CET)
Received: from 124.106.198.177 (SquirrelMail authenticated user loa@pi.nu) by pi.nu with HTTP; Tue, 12 Mar 2024 04:55:58 +0100
Message-ID: <028fd6bc5f68b201de7749fff654dfb0.squirrel@pi.nu>
In-Reply-To: <1C428D73-D8E0-4432-A3D8-59D788114318@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>
Date: Tue, 12 Mar 2024 04:55:58 +0100
From: loa@pi.nu
To: Tony Li <tony.li@tony.li>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Loa Andersson <loa@pi.nu>, "draft-ietf-mpls-mna-hdr@ietf.org" <draft-ietf-mpls-mna-hdr@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/wvyZ8eVpwDYfpZV0tRPOuh9fuVY>
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 03:56:05 -0000

Tony,


Inline plz.

>
> Hi Jie,
>
>> On Mar 11, 2024, at 2:18 AM, Dongjie (Jimmy) <jie.dong@huawei.com>
>> wrote:
>>
>> Then your proposal of occupying all the reserved bits in format B for
>> NAL would prohibit the introduction of PSD or other possible extensions
>> in future.
>>
>> IMO some reserved bits need to be kept in the NAS encoding.
>
>
> That’s fine.  As I suggested, we can steal another data bit for a
> reserved bit.
>
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? 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?

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.

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.

/Loa

> T
>
>
>