Re: [Detnet] Materials for April 26 open meeting

peng.shaofu@zte.com.cn Wed, 10 May 2023 03:14 UTC

Return-Path: <peng.shaofu@zte.com.cn>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C41E2C152565 for <detnet@ietfa.amsl.com>; Tue, 9 May 2023 20:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.796
X-Spam-Level:
X-Spam-Status: No, score=-6.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 RtPeD7IW-TaF for <detnet@ietfa.amsl.com>; Tue, 9 May 2023 20:14:34 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B9CFC14CE55 for <detnet@ietf.org>; Tue, 9 May 2023 20:14:33 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4QGKrR5KTmz8RTWr for <detnet@ietf.org>; Wed, 10 May 2023 11:14:31 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4QGKqr1ymJz4y3ZQ; Wed, 10 May 2023 11:14:00 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl2.zte.com.cn with SMTP id 34A3DiFa037039; Wed, 10 May 2023 11:13:44 +0800 (+08) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid201; Wed, 10 May 2023 11:13:45 +0800 (CST)
Date: Wed, 10 May 2023 11:13:45 +0800
X-Zmail-TransId: 2aff645b0be9ffffffffc67-00a69
X-Mailer: Zmail v1.0
Message-ID: <202305101113457723208@zte.com.cn>
In-Reply-To: <a92643fe30544836b8dd0f442d019e67@huawei.com>
References: MN2PR19MB4045ED569844FAAEEFA3BFD6836F9@MN2PR19MB4045.namprd19.prod.outlook.com, 10a822698a5e451abff7da395af17929@huawei.com, 1564e2d90d4c4261b5bf66208d349bce@huawei.com, MN2PR19MB4045FE6AF63D96A6C5D3C8D883709@MN2PR19MB4045.namprd19.prod.outlook.com, a92643fe30544836b8dd0f442d019e67@huawei.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: gengxuesong=40huawei.com@dmarc.ietf.org
Cc: David.Black@dell.com, gengxuesong=40huawei.com@dmarc.ietf.org, detnet@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 34A3DiFa037039
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 645B0C17.000/4QGKrR5KTmz8RTWr
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/uFnyRXvx8KoysTAVEwGq3DOuW8k>
Subject: Re: [Detnet] Materials for April 26 open meeting
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2023 03:14:38 -0000

Hi Xuesong,






Thanks for your presentation of CSQF, a good work to enhance the TSN CQF. 


My questions is:


    How to distinguish if there is an actually true conflict or false conflict between multiple flows arrived on a transit node  ?



    For example, flow-1 originated on source-1 whith some TSpec, packets of low-1 will arrive at the transit node P, and consume the cycle-id 2, as you said, the controller will allocate resource from cycle-id 2 for the flow-1. Suppose that the burst interval of flow-1 is one hour, that means source-1 will send packets of flow-1 again 1 hour later and the packets will arrive the node P and consume the cycle-id 2 again. Here, we suppose that there are 3-buffer (each for cycle-id 0, 1, 2 respectively) for the underlay multi-CQF mechanism, and ecah cycle is 10 us.


    Consider there is another flow-2 originated on source-2 with the same TSpec, packets of low-2 will also arrive at the transit node P, but just later than flow-1 1 minutes, and also consume the cycle-id 2.  So, it can be see that these two flows did not actually collide, but they both wish to allocate the resource of cycle-id 2. If flow-1 exhaust the total resources of cycle-id 2, can flow-2 still allocate resources from cycle-id 2 ? I hope the answer is YES, so that will support more service scale, but the complexity is that controll should maintain the release time of each flow on the network entry, and know what time the packet arrived at each transit node and check if there is true conflict between multiple arrived flows, that is, for the above example, if it is true conflict, flow-2 can not allocate cycle-id 2, otherwise it can. Right ?






Regards,


PSF











Original



From: Gengxuesong(GengXuesong) <gengxuesong=40huawei.com@dmarc.ietf.org>
To: Black, David <David.Black@dell.com>;Gengxuesong (Geng Xuesong) <gengxuesong=40huawei.com@dmarc.ietf.org>;detnet@ietf.org <detnet@ietf.org>;
Date: 2023年05月08日 09:50
Subject: Re: [Detnet] Materials for April 26 open meeting


_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet

 

Hi David,


 


Thanks for arranging the time which is perfect and I will prepare some material for discussion.


 


Thanks!


Xuesong


 




From: Black, David [mailto:David.Black@dell.com] 
 Sent: Sunday, May 7, 2023 10:20 AM
 To: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Gengxuesong (Geng Xuesong) <gengxuesong=40huawei.com@dmarc.ietf.org>; detnet@ietf.org
 Cc: Black, David <David.Black@dell.com>
 Subject: RE: Materials for April 26 open meeting




 


Hi Xuesong,


 


Excellent timing, thank you!  I’ve just put CSQF on the agenda for the May 9 open working meeting (May 10 in many time zones, including China) for the “(2) In-depth presentation” slot at the end of the meeting.


 


Will that work, or is it too soon?  There will be additional opportunities in the future.


 


As part of the presentation and discussion, please compare/contrast CSQF with TCQF (draft-eckert-detnet-tcqf-02  and draft-yizhou-detnet-ipv6-options-for-cqf-variant-02).  E.g., do all three drafts define a common queueing/scheduling mechanism that has per-draft alternatives/differences for carrying the cycle identification between DetNet nodes, or is there something specific to SR in the CSQF queueing/scheduling mechanism that would make CSQF inapplicable outside of use by SR?


 


Thanks, --David



 



From: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com> 
 Sent: Saturday, May 6, 2023 3:32 AM
 To: Gengxuesong (Geng Xuesong); Black, David; detnet@ietf.org
 Cc: Black, David
 Subject: RE: Materials for April 26 open meeting




 

[EXTERNAL EMAIL]



Some additional information about CSQF for your reference:


 


This mechanism has been discussed in WG since IETF 105 : https://datatracker.ietf.org/meeting/104/materials/slides-104-detnet-detnet-srv6-data-plane-encapsulation [datatracker.ietf.org] 


There are also very similar idea like: https://datatracker.ietf.org/doc/html/draft-stein-srtsn-00 [datatracker.ietf.org] 


Related academic work, mainly on controller algorithms:  https://www.sciencedirect.com/science/article/pii/S0140366420319642 [sciencedirect.com] 


 


Best


Xuesong



From: detnet [mailto:detnet-bounces@ietf.org] On Behalf Of Gengxuesong (Geng Xuesong)
 Sent: Saturday, May 6, 2023 3:10 PM
 To: Black, David <David.Black=40dell.com@dmarc.ietf.org>; detnet@ietf.org
 Cc: Black, David <David.Black@dell.com>
 Subject: Re: [Detnet] Materials for April 26 open meeting




 


Hi David,


 


Thanks a lot for uploading the material.


We have a document about CSQF mechanism for bounded latency, which also would like to be discussed in the DT (It could be found: https://datatracker.ietf.org/doc/html/draft-chen-detnet-sr-based-bounded-latency-01 [datatracker.ietf.org])


Do we have agenda for next week’s discussion? Shall we request a timeslot for this mechanism?


 


Best


Xuesong


 



From: detnet [mailto:detnet-bounces@ietf.org] On Behalf Of Black, David
 Sent: Wednesday, May 3, 2023 2:09 AM
 To: detnet@ietf.org
 Cc: Black, David <David.Black@dell.com>
 Subject: [Detnet] Materials for April 26 open meeting




 


With apologies for delays caused by my day job (… and some badly needed vacation …):

Slides have been uploaded and are available from here: https://datatracker.ietf.org/meeting/interim-2023-detnet-02/session/detnet [datatracker.ietf.org]

Meeting notes are in the Notepad (linked to the same page) – please check them if you haven’t already.

The meeting should have been recorded, but I don’t know where the recording is.


 


Thanks, --David


 


David L. Black, Sr. Distinguished Engineer, Technology & Standards


Infrastructure Solutions Group, Dell Technologies


mobile +1 978-394-7754 David.Black@dell.com