[mpls] Re: Potential MNA technical issue - late follow up

Loa Andersson <loa@pi.nu> Sun, 27 April 2025 03:55 UTC

Return-Path: <loa@pi.nu>
X-Original-To: mpls@mail2.ietf.org
Delivered-To: mpls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5092B21A3585 for <mpls@mail2.ietf.org>; Sat, 26 Apr 2025 20:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEaX2xuDOHGt for <mpls@mail2.ietf.org>; Sat, 26 Apr 2025 20:55:18 -0700 (PDT)
Received: from srv.pi.nu (srv.pi.nu [46.246.39.30]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 885EC21A357E for <mpls@ietf.org>; Sat, 26 Apr 2025 20:55:18 -0700 (PDT)
Message-ID: <a171b923-0d29-4d0b-a0a7-4c447c96ce17@pi.nu>
Date: Sun, 27 Apr 2025 11:55:12 +0800
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
References: <026801db83da$30a3ec40$91ebc4c0$@olddog.co.uk> <9D3BA859-A778-4DE6-9839-401ACA913861@tony.li> <027901db83e1$104f6300$30ee2900$@olddog.co.uk> <db7fc5cb1f4544f6a03014274351e515@huawei.com> <D24A6A00-D558-4CAD-9ECB-8F664291658C@tony.li>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <D24A6A00-D558-4CAD-9ECB-8F664291658C@tony.li>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: ARRDU5ZBU7ZEEQXGQ2SFQQFNMEB7EEEB
X-Message-ID-Hash: ARRDU5ZBU7ZEEQXGQ2SFQQFNMEB7EEEB
X-MailFrom: loa@pi.nu
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mpls] Re: Potential MNA technical issue - late follow up
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/5NtmJabwkyYOcSTu1OHmwyqzwfo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Tony.

Sorry for the very late response. Some comments and a question. Inline plz.

Den 21/02/2025 kl. 15:19, skrev Tony Li:
> 
> Hi Jie Dong,
> 
> 
>> Another open issue is where should the PSD indication mechanism be specified. To my understanding PSD indication is part of the general MNA solution and is orthogonal to the encoding of Post-stack data, thus it is more suitable to be covered in the MNA header draft.
> 
> 
> We still have not resolved how PSD will be indicated.  We have four proposals on the table.  When we come to consensus, then it will be obvious where to put it.
> 
> a) P-bit in the ISD header. This lacks any offset, which makes it difficult to find the PSD on mid-path nodes where other post-stack information might be above it.

I think that the P-flag can only be used if PSD immediately follows the 
LSE that has the BoS set.

You say that using the P-flag is a problem for transit nodes "where 
other post-stack information might be above it". Why does not the egress 
node have the same problem?


> b) An offset as an opcode.
> c) Offsets per PSD action.
> d) Some combination of the above.
> 
> I favor option b as it’s simple and sufficient.

You say you favor option b, I might agree with you. I option b that we 
have an OpCode (indicating "PSD present") followed by a 13 or 16 bit 
field (depending on type of LSE) containing the offset?

Like this:


     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Opcode=PSD  |      Offset             |R|IHS|S|U|  NASL | NAL |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                  Figure 2: LSE Format B: The initial opcode


    LSE Format C is used to encode the subsequent opcodes in the NAS.

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Opcode=PSD  |            Offset             |S|U|  Data | NAL |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                  Figure 3: LSE Format C: Subsequent opcodes

Then setting the P-flag would be semantically equal to having an offset 
of "0", and I see no harm in including it.

Did I understand you correctly?

/Loa
> 
> 
>> During the interim this week we didn't get chance to discuss the possible PSD indication mechanisms. This may be considered as a remaining open technical issue for further discussion.
> 
> 
> That was not on the agenda as we were hoping to resolve the SPL and ISD status issues first.
> 
> T
> 
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org

-- 
Loa Andersson
Senior MPLS Expert
Bronze Dragon Consulting
loa@pi.nu
loa.pi.nu.@gmail.com