[Detnet] Re: New Version Notification for draft-varga-detnet-srv6-data-plane-03.txt

peng.shaofu@zte.com.cn Tue, 03 February 2026 02:33 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F2F87B0EF1D3 for <detnet@mail2.ietf.org>; Mon, 2 Feb 2026 18:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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 JHeCz2Tz0RpZ for <detnet@mail2.ietf.org>; Mon, 2 Feb 2026 18:33:37 -0800 (PST)
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 8D2A2B0EF1CC for <detnet@ietf.org>; Mon, 2 Feb 2026 18:33:36 -0800 (PST)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (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 4f4nbW14nGz8Xs6y; Tue, 03 Feb 2026 10:33:27 +0800 (CST)
Received: from njb2app05.zte.com.cn ([10.55.22.121]) by mse-fl1.zte.com.cn with SMTP id 6132XMVn097278; Tue, 3 Feb 2026 10:33:22 +0800 (+08) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid201; Tue, 3 Feb 2026 10:33:23 +0800 (CST)
X-Zmail-TransId: 2afb69815e73028-48517
X-Mailer: Zmail v1.0
Message-ID: <20260203103323355hG23u_Mz-48VwkXWuRiq3@zte.com.cn>
In-Reply-To: <AM0PR07MB5938B8D0FD6CCAE0E9356E8AAC9AA@AM0PR07MB5938.eurprd07.prod.outlook.com>
References: 176994994828.2170338.109229306162198409@dt-datatracker-77f8b84995-z4hzn,AM0PR07MB5938B8D0FD6CCAE0E9356E8AAC9AA@AM0PR07MB5938.eurprd07.prod.outlook.com
Date: Tue, 03 Feb 2026 10:33:23 +0800
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: balazs.a.varga=40ericsson.com@dmarc.ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 6132XMVn097278
X-TLS: YES
X-SPF-DOMAIN: zte.com.cn
X-ENVELOPE-SENDER: peng.shaofu@zte.com.cn
X-SPF: None
X-SOURCE-IP: 10.5.228.132 unknown Tue, 03 Feb 2026 10:33:27 +0800
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 69815E77.000/4f4nbW14nGz8Xs6y
Message-ID-Hash: NPBYOIN23537A5BIB76XP62OIMSOSA5S
X-Message-ID-Hash: NPBYOIN23537A5BIB76XP62OIMSOSA5S
X-MailFrom: peng.shaofu@zte.com.cn
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: detnet@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] Re: New Version Notification for draft-varga-detnet-srv6-data-plane-03.txt
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/ANuPNaCTXBDMAWKM7T8EkfuKFeg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>

Hi Bala'zs,

Thanks for sharing this document.

After reading the document, I still have quesitons about the setting of flow-id and don't understand how it works.

There is some text in the document as below:
"
Flow-IDs MUST be allocated by the entity that controls the service sub-layer receiving node's Flow-ID space.  Because Flow-IDs are local to each node rather than being a global identifier within a domain, they MUST be advertised to their upstream DetNet service-aware peer nodes (i.e., a DetNet SRv6 End System or a DetNet Relay or Edge Node).
"

My quesiton is: why is flow-id designed to be local rather than global? Seems it brings unnecessary complex about flow-id advertisement, inconsistency of identifying the same APP flow.

Can you give some illustrations on how to set flow-id based on the example topology (fig 3 of draft-ietf-spring-sr-redundancy-protection-05) ? 

Regards,
PSF


Original


From: BalázsVargaA <balazs.a.varga=40ericsson.com@dmarc.ietf.org>
To: DetNet WG <detnet@ietf.org>;
Date: 2026年02月03日 01:31
Subject: [Detnet] Re: New Version Notification for draft-varga-detnet-srv6-data-plane-03.txt

Hi,
 
Changes in the new version of the "Deterministic Networking SRv6 Data Plane" draft
https://datatracker.ietf.org/doc/draft-varga-detnet-srv6-data-plane/
was made in order to be fully in-line with the Spring WG Redundancy Protection draft
 
The technical contents of the draft is quite stable, thanks for all the feedbacks during
its discussions.
 
Please, provide your review if you have any questions/comments/possible improvements.
Supportive feedbacks are also welcome.
 
Thanks & Cheers
Bala'zs
 
Ps: the Spring WG Redundancy Protection draft is available here:
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-redundancy-protection/
 
-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: Sunday, February 1, 2026 1:46 PM
To: Balázs Varga A <balazs.a.varga@ericsson.com>; Ferenc Fejes <ferenc.fejes@ericsson.com> 
Subject: New Version Notification for draft-varga-detnet-srv6-data-plane-03.txt
 
A new version of Internet-Draft draft-varga-detnet-srv6-data-plane-03.txt has been successfully submitted by Balazs Varga and posted to the IETF repository.
 
Name:     draft-varga-detnet-srv6-data-plane
Revision: 03
Title:    Deterministic Networking SRv6 Data Plane
Date:     2026-02-01
Group:    Individual Submission
Pages:    17
URL:      https://www.ietf.org/archive/id/draft-varga-detnet-srv6-data-plane-03.txt
Status:   https://datatracker.ietf.org/doc/draft-varga-detnet-srv6-data-plane/
HTMLized: https://datatracker.ietf.org/doc/html/draft-varga-detnet-srv6-data-plane
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-varga-detnet-srv6-data-plane-03
 
Abstract:
 
   This document specifies the Deterministic Networking (DetNet) data
   plane when operating over an IPv6/SRv6 Packet Switched Network.  It
   leverages existing IPv6 encapsulations and behaviors.  It uses the
   Redundancy SIDs in DetNet scenarios and optionally the Traffic
   Engineering mechanisms provided by SRv6.  This document builds on the
   DetNet architecture and data plane framework.
 
 
 
The IETF Secretariat
 
 
_______________________________________________
detnet mailing list -- detnet@ietf.org
To unsubscribe send an email to detnet-leave@ietf.org