Re: [Detnet] Moving forward on queuing mechanism

Dirk Trossen <> Thu, 22 April 2021 08:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 845C53A1CEF for <>; Thu, 22 Apr 2021 01:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U8HgBHk2p67Y for <>; Thu, 22 Apr 2021 01:18:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3C1483A1CEC for <>; Thu, 22 Apr 2021 01:18:44 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4FQqtH2V1Yz67yxR; Thu, 22 Apr 2021 16:13:11 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2176.2; Thu, 22 Apr 2021 10:18:39 +0200
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Thu, 22 Apr 2021 09:18:39 +0100
Received: from ([]) by ([]) with mapi id 15.01.2176.012; Thu, 22 Apr 2021 09:18:39 +0100
From: Dirk Trossen <>
To: Lou Berger <>, DetNet WG <>
Thread-Topic: [Detnet] Moving forward on queuing mechanism
Thread-Index: AQHXLT5MyoKryHLl40aDUeSRb7evEarART+Q
Date: Thu, 22 Apr 2021 08:18:39 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Detnet] Moving forward on queuing mechanism
X-Mailman-Version: 2.1.29
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, 22 Apr 2021 08:18:49 -0000

Dear chair, all,

My apologies for the delay in replying; not sure how this email fell through. I wanted to express my interest in moving this topic forward, particularly with the concise problem and related work items that will help to position this properly within DetNet; this is a crucial next step.



-----Original Message-----
From: detnet [] On Behalf Of Lou Berger
Sent: 09 April 2021 14:45
To: DetNet WG <>
Subject: [Detnet] Moving forward on queuing mechanism


There has been some discussion on if/where new DetNet related queuing mechanism should be specified.  One possibility is DetNet.  For us to undertake this work, which is atypical for a routing area WG, we will need to revise our charter to reflect the intended scope of our work. We'd like to get the discussion started on this scope.

We think the next step is for those who are interested in working on new queuing mechanisms for DetNet to help by providing a concise problem statement and possible related work items. The WG can then discuss any proposals, agree on the problem to be solved and work to be done.

Thank you,

Lou and Janos

detnet mailing list