From ekr@rtfm.com Mon Oct 23 08:26:48 2023 Return-Path: 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 B55DCC151534 for ; Mon, 23 Oct 2023 08:26:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.904 X-Spam-Level: X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20230601.gappssmtp.com 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 BSLUzXz3xr9s for ; Mon, 23 Oct 2023 08:26:46 -0700 (PDT) Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 07D6FC1519B1 for ; Mon, 23 Oct 2023 08:26:46 -0700 (PDT) Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-5ac376d311aso9313917b3.1 for ; Mon, 23 Oct 2023 08:26:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1698074805; x=1698679605; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HNcloSzjLP7A+TXfkdFImDXYqP9eA1b/QwIB4Dw+kt0=; b=kCOmTUqbn1LtQZnLpaKLpg7ZfD+KCXjmXydoU7Dv0Y1fBm9Rq6ri81J9iJ/DSzyCGT lu7zgePHIBt7Woe4neSoqUdjmtwfOFbfcpdey9IEROzIU/dvkmLNkSmpfZPavggigetz vMOqev2413ATyUVfJD2ofxlGwYImEG4JWJNiW4Hh967YjffCeHWxzFilrdhB+ip8VJwU SGm1CfMPxBFj2fB2odF3ZDtIwQee1K3ZvWT3xskgB8AypXRR6QGDbJKGaxd6NTVlNtZD 70WEVjKB5IXhGBuDKufOPj0vxwyym2yeXXpUTmoEH5xQBb0G96RSQAWXyIVE+pMPHU8L zfKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698074805; x=1698679605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HNcloSzjLP7A+TXfkdFImDXYqP9eA1b/QwIB4Dw+kt0=; b=t3I4Xsr35wo9y38IKiXga1MRmbq+jdIy16UkKyV4KNSOEjBr8V4g6R7UCk7CyNCJvh tXON3u/88HkxktXqcsQ9PdMMD2P0l/vz8rK4L7WcLN/YSzgGkx9aw+7XrV2754CGAD5Z GroNs3e9Y3pYBkDBE3MLcF/wxVap/Y9U2Q8WGhQPPqn5kPfgadbR7nT1fffVOkfkSKAB E170rgO2nYogZ2uJJ0NqqQP/0atOaacEwpPBXqn4++QQip/EVgt5pEMi9UioP8F2rNkA d0sUSkIujHpdPV2RJaTnjT5ckXJStXpzdgfAohgf+DhhVw+WVDZeJN19dHEKDUYp4NvT SS4Q== X-Gm-Message-State: AOJu0YzqOaTYE3xacMqGwOKgx0dbN/X4gDBqk0Z22FjzFemxXkR7KUqj FKcLAmV2pbMFPZWQ05i81ZirdMURQiMXG25g/gM2CA== X-Google-Smtp-Source: AGHT+IGUJSRwfjRUre6g7+NMGX0uB+Og9YlUoGwL6QVUXSytlekvBDuHEUrxDb3ultUZv06Z4rUOGf6+Z7MQcQO/Czc= X-Received: by 2002:a25:cac7:0:b0:d9a:4fa0:dca9 with SMTP id a190-20020a25cac7000000b00d9a4fa0dca9mr9954117ybg.25.1698074804708; Mon, 23 Oct 2023 08:26:44 -0700 (PDT) MIME-Version: 1.0 References: <8866efbb55914ff3b3d2dac9ba52393f@huawei.com> <258D2726-CF49-4675-8230-9548E2BD3E44@mnot.net> In-Reply-To: From: Eric Rescorla Date: Mon, 23 Oct 2023 08:26:08 -0700 Message-ID: To: Martin Thomson Cc: Mark Nottingham , Francesca Palombini , "Pengshuping (Peng Shuping)" , "dispatch@ietf.org" , "dispatch-chairs@ietf.org" , "art-ads@ietf.org" , "tsv-ads@ietf.org" Content-Type: multipart/alternative; boundary="000000000000897c9c060863d992" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2023 15:26:48 -0000 --000000000000897c9c060863d992 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Oct 23, 2023 at 3:40=E2=80=AFAM 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 think this idea has a lot of merit, but I worry about the scheduling conflicts, which are already bad with DISPATCH and SECDISPATCH being separate. -Ekr _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > --000000000000897c9c060863d992 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Oct 23, 2023 at 3:40=E2=80=AF= AM Martin Thomson <mt@lowentropy.ne= t> 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.<= br>
I'd have to agree.=C2=A0 I've seen the same presentation at both DI= SPATCH and SECDISPATCH now on several occasions.=C2=A0 And one occasion whe= re it was the same topic at both of those meetings and another working grou= p.=C2=A0 A cross-area DISPATCH group seems like a good idea.

I think this idea has a lot of merit, but I worry abo= ut the scheduling conflicts, which are already bad with DISPATCH and SECDIS= PATCH being separate.

-Ekr

_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch
--000000000000897c9c060863d992--