[spring] Slides for SRv6-SID-Related Information Validation
liu.yao71@zte.com.cn Tue, 22 July 2025 17:50 UTC
Return-Path: <liu.yao71@zte.com.cn>
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 C845B48BD7B0; Tue, 22 Jul 2025 10:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 SgBjmBfViMw0; Tue, 22 Jul 2025 10:50:09 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [160.30.148.35]) (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 AC40248BD78A; Tue, 22 Jul 2025 10:50:08 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4bmlCf38Rjz8Xs6N; Wed, 23 Jul 2025 01:50:06 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4bmlC42FDJz5B0pQ; Wed, 23 Jul 2025 01:49:36 +0800 (CST)
Received: from njy2app04.zte.com.cn ([10.40.12.64]) by mse-fl2.zte.com.cn with SMTP id 56MHnMDq023222; Wed, 23 Jul 2025 01:49:22 +0800 (+08) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid203; Wed, 23 Jul 2025 01:49:25 +0800 (CST)
Date: Wed, 23 Jul 2025 01:49:25 +0800
X-Zmail-TransId: 2afa687fcf25137-ffd49
X-Mailer: Zmail v1.0
Message-ID: <20250723014925851RG8frebocVD62p12-pJKL@zte.com.cn>
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: srv6ops@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 56MHnMDq023222
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: liu.yao71@zte.com.cn
X-SPF: None
X-SOURCE-IP: 192.168.251.13 unknown Wed, 23 Jul 2025 01:50:06 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 687FCF4E.000/4bmlCf38Rjz8Xs6N
Message-ID-Hash: 5U4LZK2CHLUPPYTDL3H3XB3AQ2HYPULC
X-Message-ID-Hash: 5U4LZK2CHLUPPYTDL3H3XB3AQ2HYPULC
X-MailFrom: liu.yao71@zte.com.cn
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@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Slides for SRv6-SID-Related Information Validation
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/qi3xum5EGLgj5n7nE4oAzTmujxI>
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>
Hi srv6ops, Due to the limited session time, we haven't present the topic of SRv6-SID-Related Information Validation in today's session. The slides could be found at https://datatracker.ietf.org/meeting/123/materials/slides-123-srv6ops-srv6-sid-related-information-validation-00. To conclude, there're many information that can be related with both MPLS labels(SR-MPLS SIDs) as well as SRv6 SIDs, such as VPN/EVPN services, IGP-Adjacency(Adj Segment), BGP peer(EPE SID),SR path (path segment). For MPLS/SR-MPLS, there're validation mechanisms for these information based on MPLS lsp ping extensions, many of which have been adopted by WGs or published as RFCs. So the question is, is there any SID-related information that needs to be verified for SRv6 just like what we've been doing for SR-MPLS? Are there potential requirements in the operators' network? Any feedback or comments are more than welcome! Thanks, Yao