IETF Logo Mail Archive

[dispatch] Re: [Secdispatch] Re: Officially combining SEC ART WIT Dispatch into one group

Mark Nottingham <mnot@mnot.net> Sat, 09 May 2026 05:48 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id F22C9EB94712; Fri, 8 May 2026 22:48:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778305736; bh=9EBY6fuLAEZX596GK88UWOMt8D/ukUMjXFQSMauNXOo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=vESo/mjv++c/uHmAdl14et4D3BhtgREF/JWCnBa+GzECtY6s8z4gwYJ5pNh3t+iRv 5nmYPOiGM5/wAcZECrif4eERhr1xsxSUfRExyfGtFOcsAeB2YhHRamtZln1+WrbAcd 7YbDL2YTSmm8gerx0aQLFs5QA6W/uUITnpr1JOxI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="dTw0DObt"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="RjrO5LNg"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xpn88-gh5Ef4; Fri, 8 May 2026 22:48:51 -0700 (PDT)
Received: from fhigh-a8-smtp.messagingengine.com (fhigh-a8-smtp.messagingengine.com [103.168.172.159]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 611D7EB94702; Fri, 8 May 2026 22:48:51 -0700 (PDT)
Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id 3F0C71400042; Sat, 9 May 2026 01:48:45 -0400 (EDT)
Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-06.internal (MEProxy); Sat, 09 May 2026 01:48:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; 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:subject:subject:to:to; s=fm1; t=1778305725; x=1778392125; bh=XiQkvLGwx0UaeR8014+n2EYW4W/Ut2DkT3LJXEVE7BE=; b= dTw0DObtPykFN0+d3qnG7oVVB+luQlNvBHXjmoaO+5zKUEJsfnJ+JgWsUmrFlMEU RYEwoKcjLC2CdfTFLDGuzRZWwGY0l6M/bdptffV3uhaIL2sT6NKH3qI+Ubo6tJos EdConwigSvVtGDn8KXCns+ObQAAZVY/P+dbIk4t4XKAKye1R0rmxgJl1Grq553r/ SK9GUiv64r7WcUiHnj5lHxOYd+l26YJHtLU4sf7/2wKmSDoDvZLtCi6ebebvbt8T FjgRIBLXY1+0kP5CIBYqZerO2l9ep4xeUBy93bELFv0ugvN2mrTpsle21WO/6juk K9K/tTFEZCBW+8uJhz6mJw==
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:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1778305725; x= 1778392125; bh=XiQkvLGwx0UaeR8014+n2EYW4W/Ut2DkT3LJXEVE7BE=; b=R jrO5LNgvbxQvVcw2LbzNTmmgCCjMgpBCoxJ9PKcWc77SfhxgxW9jQwefvHDjuJLn iP5OSmuhk4PxzV07welwUMhkBRCDKMBXBozc14ralOiycRObzmg4EiEt8+bjskJu Ui0wtvj9mnSbE+oIHe9tUhEC8mxfew/9MPbh0+W8OUJ3hZcY+DwJGJKok3iHtfgm PdG7VX+UItoOEg9RYca4CtTFtsLO7HUhhnhU+JvkoS3dHhH0zol3QpaRpBrD3mKu zSJwLoMHbQUFCmojnPa/+XjjOgRKGkG25VnwgiQFs4iTEy+fyGZlxb5vakWpNdAE l1/BDF18W3H6IOJC9VevA==
X-ME-Sender: <xms:vcr-aeXczZmdGNI30HlrNjREr1z4EVwCNiocVmKNLuxFvpRKobcz0w> <xme:vcr-aReyZcWt9pfM0RhXnlxcWjJh4mFAYKHFNmGQJPaj4D1axaooDMk2drTMQLdMh fVTfjkvEdqHPON1yE-T4LvuWM92e9cnPXxhAn9-sVWlI43BcI3tJA>
X-ME-Received: <xmr:vcr-aasQlCyM9zPkEB2UJDm8MBcUdx76tHzBgxQg3sShyIqyzBzz3FVinYGMY1ronBV-KvwNyW8tW-UyUx4Dim5Y_1_3Gz4zWVk_JqjHUtLStjmajEKo1w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdduuddvgeefucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepfefhhfelleejjeejieekhfejfeeiheetgeejgffhudegveeigeehgefftdetudet necuffhomhgrihhnpehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurf grrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtpdhnsggprhgtphht thhopeehpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopeguvggstghoohhlvgihud esghhmrghilhdrtghomhdprhgtphhtthhopehrshgrlhiipeegtdgrkhgrmhgrihdrtgho mhesughmrghrtgdrihgvthhfrdhorhhgpdhrtghpthhtohepmhgtrhdoihgvthhfsehsrg hnuggvlhhmrghnrdgtrgdprhgtphhtthhopeguihhsphgrthgthhesihgvthhfrdhorhhg pdhrtghpthhtohepshgvtgguihhsphgrthgthhesihgvthhfrdhorhhg
X-ME-Proxy: <xmx:vcr-aQ_lSS-Oh-YJZS-Dqb0vaidHVjL6-MbjO9YqqacpWsC80fk_tA> <xmx:vcr-aV2-K-cvuXr378mWvcdf1btY2xxZEJImA8dvBQZkmLEbC_ijmw> <xmx:vcr-aVD1X-JaUBkXNZRrEByNGyJyeyoIJuphG-_zI1rnyRXzdIcC8g> <xmx:vcr-aRebOnXGYTnYDVfDzRm8BZtMshtIrIX7jikniQ5w3-iGV-fZvQ> <xmx:vcr-afDV5playgIL9maEnTyKdZg1hWlM1hGy4Y5L0GogVCQhwxDGM5aW>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 9 May 2026 01:48:43 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAGgd1Odgo7-bZkGWepU94Gc1wEDyMwUTQZepgu9vdPfjrZ6L2A@mail.gmail.com>
Date: Sat, 09 May 2026 15:48:38 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B94FCEB-9D8C-411C-ADDD-2782A9227504@mnot.net>
References: <2f13811b-50ba-457c-aac3-efbb2f9a705b@hxr.us> <8B59F5F9-AF69-4469-AE6C-E85081A56782@mnot.net> <27028.1777845238@obiwan.sandelman.ca> <3fbb345b-74aa-4cbe-8c7a-25d9c4393e62@hxr.us> <MN2PR17MB4031741942A1AB355D4B7B61CD3F2@MN2PR17MB4031.namprd17.prod.outlook.com> <CAGgd1Odgo7-bZkGWepU94Gc1wEDyMwUTQZepgu9vdPfjrZ6L2A@mail.gmail.com>
To: Deb Cooley <debcooley1@gmail.com>
X-Mailer: Apple Mail (2.3864.500.181)
Message-ID-Hash: IKCXE3CMV26RHC4W7Q7J3TGHXWUSCNT7
X-Message-ID-Hash: IKCXE3CMV26RHC4W7Q7J3TGHXWUSCNT7
X-MailFrom: mnot@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "dispatch@ietf.org" <dispatch@ietf.org>, "secdispatch@ietf.org" <secdispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Re: [Secdispatch] Re: Officially combining SEC ART WIT Dispatch into one group
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/nOYjsG8d29a15spD9btmTQUCm_8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

'Dispatch' is a single word whose meaning is relatively clear and relevant. 

These suggestions are not words; they're strange backronyms that perpetuate the IETF's tendencies towards insider baseball.

If reusing 'dispatch' is truly an issue, there are many alternatives. My local LLM suggests:

- Triage
- Intake
- Clearinghouse

I don't mind 'Triage'.

Cheers,


> On 9 May 2026, at 3:14 pm, Deb Cooley <debcooley1@gmail.com> wrote:
> 
> I agree with Andy on many points - having to explain what 'dispatch' means (over and over and over), avoiding the perception that every idea is appropriate for the dispatch group (vice what is done elsewhere in the IETF), and avoiding the perception of having closed secdispatch. 
> 
> The goal of this is to bring in both new work and new people.  There are enough completely new participants that it warrants explanation and clarity.  We need to make the process more approachable.  Note:  there is a wiki for the details of slide templates, and other guidance.  Combining the current wikis into one for the new wg will be worked on (using many of the suggestions here).
> 
> I do like WASDISPATCH (and WASNEW), thanks to ekr for that idea.
> 
> Deb
> Sec AD
> 
> On Wed, May 6, 2026 at 5:28 PM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
> 
> > I frequently have to describe what DISPATCH is to newcomers. The name-to-purpose linkage is not as intuitive as you might think.
> 
> How often are *DISPATCH presenters completely new to the IETF?  Do they also find “HOTRFC” confusing? Do you think SAWDISPATCH will reduce the amount of explanations you have to do?
> 
> > And keeping DISPATCH while closing SECDISPATCH could give the impression that SECDISPATCH is going away, not being merged.
> 
> Easily fixed by tweaking the “closed” message in the datatracker, or adding a resource that redirects.
> 
> _______________________________________________
> dispatch mailing list -- dispatch@ietf.org
> To unsubscribe send an email to dispatch-leave@ietf.org
> _______________________________________________
> dispatch mailing list -- dispatch@ietf.org
> To unsubscribe send an email to dispatch-leave@ietf.org

--
Mark Nottingham   https://www.mnot.net/

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