Re: [Detnet] Queueing mechanism evaluation examples Thu, 09 November 2023 09:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 25DCBC151061; Thu, 9 Nov 2023 01:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sMFQfbGCyMB8; Thu, 9 Nov 2023 01:36:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 66E96C14CF05; Thu, 9 Nov 2023 01:36:50 -0800 (PST)
Received: from (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (FangMail) with ESMTPS id 4SQxg13FBfz8XrRG; Thu, 9 Nov 2023 17:36:45 +0800 (CST)
Received: from ([]) by with SMTP id 3A99afm0052188; Thu, 9 Nov 2023 17:36:41 +0800 (+08) (envelope-from
Received: from mapi (njb2app05[null]) by mapi (Zmail) with MAPI id mid201; Thu, 9 Nov 2023 17:36:44 +0800 (CST)
Date: Thu, 09 Nov 2023 17:36:44 +0800
X-Zmail-TransId: 2afd654ca82c6da-2ca05
X-Mailer: Zmail v1.0
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: 3A99afm0052188
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 654CA82D.000/4SQxg13FBfz8XrRG
Archived-At: <>
Subject: Re: [Detnet] Queueing mechanism evaluation examples
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Nov 2023 09:36:57 -0000

Hi Jinoo,

I believe we have the same topology in mind.
The 10 hops showed in the figure is just the path passed through by flow i.
Please see the further updated figure that contains other nodes that passed through by other flows. 

However, if it is not the same topology in your mind yet, can you add another example-2 in the slides ?



From: JinooJoung <>
To: 彭少富10053815;
Cc: <>; <>; <>;
Date: 2023年11月09日 16:44
Subject: Re: [Detnet] Queueing mechanism evaluation examples

I think it is still too simple and specific.
Topology does not include mesh. Flows are monotonic.

My suggestion is to reflect the "real" situation, as much as possible.


On Thu, Nov 9, 2023 at 5:11 PM <> wrote:

Hi Jinoo,

Thanks for your comments. The slides is updated.
For the topology envisioned in my mind is actually the same as what Toerless provided before. I think it may cover the simulation topology as shown in your paper.



From: JinooJoung <>
To: 彭少富10053815;
Cc: <>; <>; <>;
Date: 2023年11月09日 12:20
Subject: Re: [Detnet] Queueing mechanism evaluation examples

Shofu, thanks for the suggestion.
Your scenario seems to contain only a single hop with the flows of monotonically increasing latency bounds specifications.   
I suggest that for a scenario to be effective in evaluating our queuing solutions, the following requirements should be met.

1. The network should have a large enough diameter, such as more than 8 hops or so.
2. The network should have a complex topology including mesh or ring.
3. The flows should have TSpecs, including max burst size and average rate.
4. The flows should have RSpecs, which reflect realistic latency & jitter bounds such as those of video, XR gaming, or industrial control loop.

My paper below has the simulation setup which meets these requirements.
If you are interested, please take a look. 

Joung J., Kwon J., Ryoo J-D., Cheung T., "Scalable flow isolation with work conserving stateless core fair queuing for deterministic networking" IEEE Access, vol. 11, Sep. 2023. doi: 0.1109/ACCESS.2023.3318479

Best regards,

On Thu, Nov 9, 2023 at 12:11 PM <> wrote:

Hi WG,

During the session, most people hope to have one or several common examples to evaluate various queueing mechanisms. 
I provided an initial example (see the attachement). 
Hope it can be helpful and welcome more examples with typical and real requirements can be added.


 detnet mailing list