[dispatch] Dispatch IETF 118 outcomes & minutes

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Mon, 06 November 2023 21:15 UTC

Return-Path: <pengshuping@huawei.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD14BC151989; Mon, 6 Nov 2023 13:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 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, 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 sZTWu_hZ_YeL; Mon, 6 Nov 2023 13:15:33 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 114E3C1519BD; Mon, 6 Nov 2023 13:15:33 -0800 (PST)
Received: from lhrpeml500003.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SPPHT4XMBz67TK2; Tue, 7 Nov 2023 05:14:29 +0800 (CST)
Received: from canpemm100006.china.huawei.com (7.192.104.17) by lhrpeml500003.china.huawei.com (7.191.162.67) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Mon, 6 Nov 2023 21:15:29 +0000
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm100006.china.huawei.com (7.192.104.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 7 Nov 2023 05:15:27 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2507.031; Tue, 7 Nov 2023 05:15:27 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: dispatch <dispatch@ietf.org>
CC: "dispatch-chairs@ietf.org" <dispatch-chairs@ietf.org>, "dispatch-ads@ietf.org" <dispatch-ads@ietf.org>
Thread-Topic: Dispatch IETF 118 outcomes & minutes
Thread-Index: AdoQ9lazzs/wxcPBQcWohHpbuHvTHw==
Date: Mon, 06 Nov 2023 21:15:27 +0000
Message-ID: <7d1e8c35af594d9c9e65b80acecba4f7@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.152.236]
Content-Type: multipart/alternative; boundary="_000_7d1e8c35af594d9c9e65b80acecba4f7huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/VtS5Ez5G1a8xz324dRGo3vncEok>
Subject: [dispatch] Dispatch IETF 118 outcomes & minutes
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2023 21:15:37 -0000

Dispatchers,

Thanks to all our presenters for sharing their work with us in the dispatch session, and thanks to the attendees who helped us in finding dispatching consensus on-list, in-person or virtually. We will be contacting presenters directly to help progress the work in-line with what was agreed.

A summary of the dispatch outcomes follows:

1.      Suggested to having a working group, AD wants to see more evidence
of community before forming one.

2.      More discussions needed, CBOR is not the right place, try to get
feedback from JSON Shema

3.      Narrow down the scope, if a working group to be formed, a research
group is suggested.

4.      Coordinate more closely with M3AAWG than perhaps form a WG.
The first capture of the minutes -00 has been published (many thanks to our note taker Bron Gondwana):
https://datatracker.ietf.org/doc/minutes-118-dispatch-202311060830/
If you have any comments, corrections or questions, please get in touch with the chairs.

We wish you a great rest of the week at IETF!

Shuping & Jim