[Detnet] 回复: Moving forward on queuing mechanism

刘 鹏 <liupengyjy@outlook.com> Fri, 23 April 2021 03:46 UTC

Return-Path: <liupengyjy@outlook.com>
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 71EC53A0BCA for <detnet@ietfa.amsl.com>; Thu, 22 Apr 2021 20:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RnjzqP2XdA-9 for <detnet@ietfa.amsl.com>; Thu, 22 Apr 2021 20:46:14 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255024.outbound.protection.outlook.com [40.92.255.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 387FE3A0BC5 for <detnet@ietf.org>; Thu, 22 Apr 2021 20:46:13 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=c0dIc3Kh8LM+Etb/HYF0DrGv1mCCHdCkoS0428eo0yfBTkduXNwC4Wgyyop9T1K8Vi6b5sCa8oJVYexO67P2hxdk5x1DEcye00JEz2CM3JSzvYr6oPjJrVXRLBZsoelGY5Aw+Er9G88TRAkVtPohdviqZUDvFsCXhIkGnW0l68GXNxwv1+38wNsHEU8CTtwSOgQuUUbEiziEtOeubKH8v6zO3kdDW+Oo+xEAOEA2spBp+sck+MGcy02ZjyeIoo4SL81AOhYEWWLHsKXLq3UKifSRx0MfFMDstQ7cwd3X3l1f64kzjd/le2TkB8CRHMmt0suscbfq0YMG9sBt7f/A1A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=v9ZXhVV/fzuBLsbGFCjsrZi1EavOk9MbSmgspK9r2yI=; b=lfqGzheCrGzjP8CvnsqOv2/HmkprIZcNn4EUByiblxkUvERuGbytmHPzaOpl/j7HsfEMDefRoNvGU1p9kaGRD8rbeyRekQwITkFqv5b3CEPY/iRI8RyimtfYCkQhWWIDMaKjrJ91Z7oL45jbjiNA3RzyLCLfF+63vRbRZvQNhYyV/2aG8s9oZlpajb4TEksstLFmjOea47NCB/pRHEKLd1FILS2VzA/R5zWKX/24f2+1OevcfejB8iIf8CCKUa/fRgfNI0YNTNATp8cUwcKDElUYwkdrp0wVoXBTzw+zOBQJwPLCKltQ0Ro3WxSyq6A54oZZs5JrC3eNHQSHxdpTkQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=v9ZXhVV/fzuBLsbGFCjsrZi1EavOk9MbSmgspK9r2yI=; b=Ubjdlsfkg3bS+hyW6RCZJbul/4gmF5BYjJh0odmdMa651sXfiHnMMwA4igKcPQFYFigOIKuUw9lVRJyrvHzlSaCwAVy9G/Rv8T0fkDC1aO7IvcRSfvRhH9xRBdpIQFCbWY1t0cPSIIwgXG0lVCgpTAM+yue5c3jdm5yKMJJTczAYTgkebQKbemav98FNqBCd7Ueh5p934QSU/B1ThRiHdHkQVA8JSKrjx8ercMTXxpBM2LVJ6ZcTVyhad+/Kxl/5VgwCbRsXKhQIT6Ls8/ywHGrd4wDp/u5R/Zk6jY+58v8hba0Tqiei/yQrWwCu7XXpML3DemUjmQ3MZqfwL1oWGA==
Received: from SLXP216CA0056.KORP216.PROD.OUTLOOK.COM (2603:1096:100:5::18) by TY2PR0101MB3134.apcprd01.prod.exchangelabs.com (2603:1096:404:e4::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4065.21; Fri, 23 Apr 2021 03:46:09 +0000
Received: from PU1APC01FT014.eop-APC01.prod.protection.outlook.com (2603:1096:100:5:cafe::b3) by SLXP216CA0056.outlook.office365.com (2603:1096:100:5::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.21 via Frontend Transport; Fri, 23 Apr 2021 03:46:09 +0000
Received: from TYCPR01MB6656.jpnprd01.prod.outlook.com (2a01:111:e400:7ebe::4b) by PU1APC01FT014.mail.protection.outlook.com (2a01:111:e400:7ebe::224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4065.21 via Frontend Transport; Fri, 23 Apr 2021 03:46:09 +0000
Received: from TYCPR01MB6656.jpnprd01.prod.outlook.com ([fe80::484d:5f44:6ace:5721]) by TYCPR01MB6656.jpnprd01.prod.outlook.com ([fe80::484d:5f44:6ace:5721%6]) with mapi id 15.20.4065.021; Fri, 23 Apr 2021 03:46:09 +0000
From: =?gb2312?B?wfUgxfQ=?= <liupengyjy@outlook.com>
To: Lou Berger <lberger@labn.net>, DetNet WG <detnet@ietf.org>
Thread-Topic: [Detnet] Moving forward on queuing mechanism
Thread-Index: AQHXLT4mCDZF3JMjyUOTng08BLiIAarARbaAgAFFQjw=
Date: Fri, 23 Apr 2021 03:46:09 +0000
Message-ID: <TYCPR01MB6656D95B92236A728100D8A7DA459@TYCPR01MB6656.jpnprd01.prod.outlook.com>
References: <c3780792-86c8-42ed-2c95-97291531a16e@labn.net>, <2189c2879a074ae88711630b2cd40ec0@huawei.com>
In-Reply-To: <2189c2879a074ae88711630b2cd40ec0@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:215183748CB0738B7BC6E24768D1D462CD8E95EA4664FE44B13E3A90D97580DE; UpperCasedChecksum:A2098B39C8539B44CC902AFA754E9E8AEF891499006C5865946FF890BEFA2BA5; SizeAsReceived:6926; Count:43
x-tmn: [3uXkvfT3Q/qVv6H3kPv7UpnA6WPuY8jw5zVjSbM3y8w=]
x-ms-publictraffictype: Email
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 17a414df-18e9-4e2f-d377-08d9060a551b
x-ms-traffictypediagnostic: TY2PR0101MB3134:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Ztj1CFfOf+6EY5v0RRr8GbRFnysaQV6LbLcNIbKT1tqI21Ayffhzs8xCuKzQdsGbwKSWK6T15qY0CD7ICDivPcbL1XKCFmsnxbMmCNb3DxPYyxC5PBLzR6NGa2rzjNGoUPp/vy3hPWY/MQHR51qvJ56MLgjTMLCxJSWw/idf0SzJ7iq39dSAlt+9C9yXDV5/y3/ozarRXdYgUHAJkZLH/sZTExAEeuPVzsSZv+uOgQTTLnFK5QlDsNM2SsKUgDA7aS/q+uGseOFFJxikwvMAtu/wGj0+O/1fi1dzLl4QsWp/PkYdCoJLDCgrVcsqANWLKKM4pSGWTWHGjF027EQpDwQqlhcFGra5u4c2C3MmZ4xbJnw4Rmlq2dIBXwTaYLyuKNtb9F8VZvGWEh3sDMr7fYonz6TSFf4FsbYmD+MHZu8=
x-ms-exchange-antispam-messagedata: ps46+FyTO2ev7wNYA4HKqa8BqlJBWiqCJO3K4MclGStQ1x4OAQcv1bCIvJJpa6QxqHXBGgoDainuN+8HEUyf7UlhUPDN5yX7KbWklMUUB91CVC0x/tl1RgvKMIFKJdeYvbse/SpOZv+18pkc2HiYrg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_TYCPR01MB6656D95B92236A728100D8A7DA459TYCPR01MB6656jpnp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: PU1APC01FT014.eop-APC01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 17a414df-18e9-4e2f-d377-08d9060a551b
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Apr 2021 03:46:09.5697 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY2PR0101MB3134
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/ARm2m0luUZPiUw-0T7pP5H492Z8>
Subject: [Detnet] =?gb2312?b?u9i4tDogIE1vdmluZyBmb3J3YXJkIG9uIHF1ZXVpbmcg?= =?gb2312?b?bWVjaGFuaXNt?=
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 23 Apr 2021 03:46:20 -0000

Hi chairs, all,

I think this topic is meaningful, and there are some drafts about queuing mechanism at present.

I also believe more people will be interested in it and look forward to the following discussion.

Regards,
Peng Liu
________________________________
发件人: detnet <detnet-bounces@ietf.org> 代表 Dirk Trossen <dirk.trossen@huawei.com>
发送时间: 2021年4月22日 16:18
收件人: Lou Berger <lberger@labn.net>et>; DetNet WG <detnet@ietf.org>
主题: Re: [Detnet] Moving forward on queuing mechanism

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.

Best,

Dirk

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

WG,

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
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet
_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet