IETF Logo Mail Archive

Re: [Gendispatch] A gendispatch session at IETF 118?

Jim Reid <jim@rfc1035.com> Wed, 06 September 2023 06:11 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D27C151064 for <gendispatch@ietfa.amsl.com>; Tue, 5 Sep 2023 23:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ET_A99MBeuru for <gendispatch@ietfa.amsl.com>; Tue, 5 Sep 2023 23:11:38 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4A2CC151065 for <gendispatch@ietf.org>; Tue, 5 Sep 2023 23:11:38 -0700 (PDT)
Received: from [10.255.116.128] (unknown [101.96.112.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 6898324211D6; Wed, 6 Sep 2023 06:11:36 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <e3aee3c9-fb21-2e83-a351-d8f347e0f764@lear.ch>
Date: Wed, 06 Sep 2023 07:15:04 +0100
Cc: GENDISPATCH List <gendispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFACE665-5B2F-46A4-A005-A875C267A763@rfc1035.com>
References: <CAChr6SwpLsJ0S4jkvWL4DPys0Y9pvJwWhZtbr7E6fvFioRpsEQ@mail.gmail.com> <e3aee3c9-fb21-2e83-a351-d8f347e0f764@lear.ch>
To: Eliot Lear <lear@lear.ch>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/eLKoHKnZF_JgqttvQ2w_jpP0SrU>
Subject: Re: [Gendispatch] A gendispatch session at IETF 118?
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2023 06:11:44 -0000


> On 6 Sep 2023, at 06:54, Eliot Lear <lear@lear.ch> wrote:
> 
>> Doing things this way will let you just publish an I-D in the old way, and I think that way is better.
>> 
> What was the old way?

More importantly, what's the new way? I didn't get the memo.

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