[spring] Re: Question for the working group - regarding segment types

Joel Halpern <jmh@joelhalpern.com> Fri, 06 March 2026 17:56 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@mail2.ietf.org
Delivered-To: spring@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4F8BDC5C06B8 for <spring@mail2.ietf.org>; Fri, 6 Mar 2026 09:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 bqXtrNpvgxOh for <spring@mail2.ietf.org>; Fri, 6 Mar 2026 09:56:00 -0800 (PST)
Received: from mailb1.tigertech.net (mailb1.tigertech.net [208.80.4.153]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 96E4EC5C064D for <spring@ietf.org>; Fri, 6 Mar 2026 09:55:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1772819756; bh=Ssoa/2s1uh9Te7ZuNTxrC4j/b6J+qiOsqjMtXZ7Alag=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=UEOp0LCoKnUEctfafqa5BA9jiiO2q1K5e2/x25Rv+4b/maiOTrAfUksQib+A7yyA8 SFUvq6oTQYh/8LZm1chvHgr10MCAGwOqRWogoO5kXYyRsm6VoIUvnRpzbBHoBFV1RQ IC8BzQJ5UpYDDu2ePamZHLq4IAoXPwuLMpq21Wto=
Received: from localhost (localhost [127.0.0.1]) by mailb1.tigertech.net (Postfix) with ESMTP id 4fSDbc049qz5c571; Fri, 6 Mar 2026 09:55:56 -0800 (PST)
X-Quarantine-ID: <vvBgQBSKFQ58>
X-Virus-Scanned: Debian amavis at b1.tigertech.net
Received: from [IPV6:2600:8806:103:9500:b02f:88cc:d1ed:f174] (unknown [IPv6:2600:8806:103:9500:b02f:88cc:d1ed:f174]) (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 mailb1.tigertech.net (Postfix) with ESMTPSA id 4fSDbb2j2pz5c54g; Fri, 6 Mar 2026 09:55:55 -0800 (PST)
Message-ID: <fd2b55cd-4cdb-4944-89ea-384ced69973f@joelhalpern.com>
Date: Fri, 06 Mar 2026 12:55:53 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Tony Li <tony.li@tony.li>
References: <5ee04659-206e-467a-8133-89398511d31b@joelhalpern.com> <90724603-B2A2-4330-9E44-443452EEB3E4@tony.li>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <90724603-B2A2-4330-9E44-443452EEB3E4@tony.li>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: ZT2KSQ4UNZOP63G2XJXA4ZFLHDLLSPHO
X-Message-ID-Hash: ZT2KSQ4UNZOP63G2XJXA4ZFLHDLLSPHO
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: SPRING WG <spring@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: Question for the working group - regarding segment types
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/AYmfJxlppQ00BDnB3YqGXeN-I0A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>

Note that while the Spring working group is consulted about new segment 
types by the registry designated expert, the registry is "specification 
required", so any WG can create entries if they so choose.

Yours,

Joel

On 3/6/2026 12:52 PM, Tony Li wrote:
>
>> On Mar 6, 2026, at 9:25 AM, Joel Halpern - jmh.direct at joelhalpern.com <mailforwards@cloudmails.net> wrote:
>>
>> In regard to Segment Routing Policy as defined by RFC 9256 and the MPLS Network Action (MNA) work that is being standardized by the MPLS working group, please express an opinion as to whether:
>>
>> 1) An MNA Substack may never be considered a segment in the sense of RFC 9256 section 4;
>>
>> 2) Some MNA substacks may be considered segments in the sense of RFC 9256 Section 4 (possibly with a new segment type, possibly with an existing segment type)
>>
>> 3) MNA substacks are segments in the sense of RFC 9256 section 4 (possibly with a new segment type, possibly with an existing segment type)
>
> An MNA ISD Substack is a set of LSEs. It contains no forwarding labels. To my read, it does not fall into any of the types currently defined in RFC 9256 section 4.
>
> Whether or not we want to declare a new segment type is of course up to the WG, and depends entirely on whether there is benefit to doing so.  I am not yet convinced that there is benefit, but am open to constructive arguments.
>
> Regards,
> Tony
>
> _______________________________________________
> spring mailing list -- spring@ietf.org
> To unsubscribe send an email to spring-leave@ietf.org