IETF Logo Mail Archive

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

Alexey Melnikov <aamelnikov@fastmail.fm> Mon, 23 October 2023 12:59 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 0EE88C16F3F7; Mon, 23 Oct 2023 05:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Level:
X-Spam-Status: No, score=-7.196 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b="X4lYokPZ"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="YHYOtRcQ"
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 prYuVaRxd005; Mon, 23 Oct 2023 05:59:39 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 376F8C151557; Mon, 23 Oct 2023 05:59:39 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 77CB15C02D4; Mon, 23 Oct 2023 08:59:38 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 23 Oct 2023 08:59:38 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1698065978; x=1698152378; bh=8X9eA0avBm2vNfx41Ed0G+i48dC1NgidTJ1 U6nA3uQA=; b=X4lYokPZGkNRut8lwFhEahgK9dbc0XmdIrsqBq16+06W15vg/Gc qJxCUYajbl4mg7CrOwKn0EmzslTn07k+ipF/yeXwDXRuLPQUcQaKz1+ofAvCrmc2 pGKxWWcv2xCe5cF0evGManI7mW1iEF3S9irwhZLXbwM0qxVye+gx7n8A7x9+Mht+ 85J+rkx9rwL3/DJOdHmJbCvMJ1qiWWh/npUb6XKjZa76Jh3VRSGUa7MSMq2Cd6AE xQCBxPEHfS1dvbXTu30/ud2dyaKRf2xd+cW1HTkjsn1wyoKrfNVlrsDxk5mfNJnp 1PhpLC1lsH26lfKb2tEis9KJunh5+FV2hgw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1698065978; x=1698152378; bh=8X9eA0avBm2vNfx41Ed0G+i48dC1NgidTJ1 U6nA3uQA=; b=YHYOtRcQ4qQvEL+UFzbzQFQbPiTWrjTFFP+JDB1lMXG3NjimBF8 ghJCjY4FEeHxXgIEt5t/JPw04HJagggW0ytfl4vI/qs6fMmRc2QMZJ84HmAKrNjB 9QTmjQ0ZIvJJWjJRnApDSsdd+HB8I5urAbavgDYpWa+PHUB1wcBPFbeURirHKeOH D2RzlUGfR6i81pF8goOYmoiCT82Irl2FS57ML8GbtaHC75TKE10KzxKNfUPbBz4G mtezPO5lBrB3bP6dKGZZKyGypxxKyTFHcHf9YG0fUAJXRk9rtWOZOxU5zUJHA7Ov GK7t4gIxzcSaIx5b3jDmKwIdZT1xMEmhoAA==
X-ME-Sender: <xms:Om42ZSXTlLkss3o_-kvziFWkHx3TF5_KP8WBxxcznFXrkc9r3Viyww> <xme:Om42ZelAI76rFnyW1NZbeEpi-konFt-tmBX4iCA2JWP5eASqNIVjpSqNi_Oz9Fhaf fP38KAajAS6LeVGzA>
X-ME-Received: <xmr:Om42ZWZRgH2yzK7hrhBw34ztN0Kd8fbdFSRHfJAVgdGVVvp49cUzWBY2EOa6nf8Ckg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrkeeigdehjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomheptehlvgig vgihucfovghlnhhikhhovhcuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh eqnecuggftrfgrthhtvghrnhepfeetgfdufffhfeejfeduleeitdegvefhheeiveeijeeh veeufefgjefgudehleegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggrmhgvlhhnihhkohhvsehfrghsthhmrghilhdrfhhm
X-ME-Proxy: <xmx:Om42ZZW4r3t95B9h2pTCdZMWuWA2MHFe5qt70P1V02dgID3mrQc3bA> <xmx:Om42Zck5RyXjAstMiRlJ388cqKXk_96BgxocBgDygpP4DaAhXL2b6g> <xmx:Om42ZefMcPF6pnysOjKE74ZYa9hGPPcRyua5nHPyrOgf3wTPZ0iamg> <xmx:Om42ZbvVymSbX7BBpetOO3AR-Pjv5sEpVDeYQ6iVOL0D1GuKu8HV9Q>
Feedback-ID: if62040e7:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 23 Oct 2023 08:59:37 -0400 (EDT)
Message-ID: <755c1248-0d8a-6f1f-3c4e-9b0a732c3222@fastmail.fm>
Date: Mon, 23 Oct 2023 13:59:33 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
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@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>
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>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
In-Reply-To: <bff6715c-0861-4647-96fb-385d21fbccaf@betaapp.fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/B7ZPzM1IFXeZL3ngczA88sAHwkw>
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: Mon, 23 Oct 2023 12:59:44 -0000

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.

v2.27.8 | Report a Bug | By Email | System Status