Re: [dispatch] IETF 118 - do you have something for DISPATCH?

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Tue, 24 October 2023 02:40 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 99ED5C1705EB; Mon, 23 Oct 2023 19:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] autolearn=unavailable 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 6jp0wnaoX_QK; Mon, 23 Oct 2023 19:40:15 -0700 (PDT)
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 2DC53C151981; Mon, 23 Oct 2023 19:40:15 -0700 (PDT)
Received: from lhrpeml100003.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SDx901TY4z67yl7; Tue, 24 Oct 2023 10:39:32 +0800 (CST)
Received: from canpemm500007.china.huawei.com (7.192.104.62) by lhrpeml100003.china.huawei.com (7.191.160.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 24 Oct 2023 03:40:11 +0100
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm500007.china.huawei.com (7.192.104.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Tue, 24 Oct 2023 10:40:09 +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, 24 Oct 2023 10:40:09 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, Martin Thomson <mt@lowentropy.net>, Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>, Francesca Palombini <francesca.palombini@ericsson.com>
CC: "dispatch@ietf.org" <dispatch@ietf.org>, "dispatch-chairs@ietf.org" <dispatch-chairs@ietf.org>, "art-ads@ietf.org" <art-ads@ietf.org>, "tsv-ads@ietf.org" <tsv-ads@ietf.org>
Thread-Topic: [dispatch] IETF 118 - do you have something for DISPATCH?
Thread-Index: Adn4wEvVY/ti/L0eTOmtDA7S4xkwWwMuXufw//+B8gCAAAmPgIAAiW6D//+rt4CAACc3gP/+lVQg
Date: Tue, 24 Oct 2023 02:40:09 +0000
Message-ID: <6bb01f9acc24409cb3a829f7d25aded0@huawei.com>
References: <8866efbb55914ff3b3d2dac9ba52393f@huawei.com> <e7af4a430aeb42deb6f9de857d71b2f2@huawei.com> <258D2726-CF49-4675-8230-9548E2BD3E44@mnot.net> <AS1PR07MB86162B208AA31E4D08F30FD598D8A@AS1PR07MB8616.eurprd07.prod.outlook.com> <F7FEC59F-3264-43D2-8F32-DE4412263628@mnot.net> <bff6715c-0861-4647-96fb-385d21fbccaf@betaapp.fastmail.com> <755c1248-0d8a-6f1f-3c4e-9b0a732c3222@fastmail.fm>
In-Reply-To: <755c1248-0d8a-6f1f-3c4e-9b0a732c3222@fastmail.fm>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.41.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/6wxA8ZOKsvIXTv1q2MR5KJ8MQag>
Subject: Re: [dispatch] IETF 118 - do you have something for DISPATCH?
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: Tue, 24 Oct 2023 02:40:20 -0000

Maybe we could segment a single DISPATCH session into multiple parts, e.g. Cross-area, ART area, WIT area and SEC area, and allocate the received requests into each corresponding part. This allocation could be requested by the presenters or suggested by Chairs or Community in the mailing list. 

In the current dispatch agenda, we put time for each presentation to give people a rough indication about the session schedule, aiming to assist people to make their own time schedule.

If we've got more requests that cannot be held with one DISPATCH, then we could consider to request a couple of slots for DISPATCH in the IETF agenda. 

Shuping


-----Original Message-----
From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm] 
Sent: Monday, October 23, 2023 9:00 PM
To: Martin Thomson <mt@lowentropy.net>; Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>; Francesca Palombini <francesca.palombini@ericsson.com>
Cc: dispatch@ietf.org; dispatch-chairs@ietf.org; art-ads@ietf.org; tsv-ads@ietf.org
Subject: Re: [dispatch] IETF 118 - do you have something for DISPATCH?

On 23/10/2023 11:39, Martin Thomson wrote:

> On Mon, Oct 23, 2023, at 18:39, Mark Nottingham wrote:
>> I would strongly suggest that we combine SECDISPATCH into DISPATCH 
>> and make its scope ART, WIT, and SEC. There is already too much venue 
>> shopping / confusion between SECDISPATCH and DISPATCH, and adding a 
>> third (which your message implies will be necessary) will only add to 
>> the chaos. Getting cross-area review is very healthy at early stages.
> I'd have to agree.  I've seen the same presentation at both DISPATCH and SECDISPATCH now on several occasions.  And one occasion where it was the same topic at both of those meetings and another working group.  A cross-area DISPATCH group seems like a good idea.
(I would probably keep GENDISPATCH separate.)

I like this idea, but this probably means multiple DISPATCH sessions during an IETF week.