IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Wed, 06 September 2023 05:54 UTC

Return-Path: <lear@lear.ch>
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 02F75C14CE4D for <gendispatch@ietfa.amsl.com>; Tue, 5 Sep 2023 22:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.189
X-Spam-Level:
X-Spam-Status: No, score=-2.189 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, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=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 (1024-bit key) header.d=lear.ch
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 LU_QJBH1mZVi for <gendispatch@ietfa.amsl.com>; Tue, 5 Sep 2023 22:54:27 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2a00:bd80:aa::2]) (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 640F6C14CE2C for <gendispatch@ietf.org>; Tue, 5 Sep 2023 22:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1693979661; bh=+WJCOhorSw2DyGzFxLZFlfbf/L4wXSQW/z2mSVrkdos=; h=Date:Subject:To:References:From:In-Reply-To:From; b=WayDCmXNI1x1iijdXf6GsSC5gMn45FF0ga7AG4vzunF+ZAbvTpejHybKQzOT6znGw QHBMNM2kz1ez7oYrePjFl48GdZteyDIf7iQKZ8lu6axBL4yKn6E7iYNp8LE0rKPCs1 dVD00fyMCAXDXy89plsmlN3AGE9HFh+gKyoyyET8=
Received: from [192.168.0.99] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 3865sK4g2188604 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 6 Sep 2023 07:54:21 +0200
Message-ID: <e3aee3c9-fb21-2e83-a351-d8f347e0f764@lear.ch>
Date: Wed, 06 Sep 2023 07:54:20 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.15.0
Content-Language: en-US
To: Rob Sayre <sayrer@gmail.com>, GENDISPATCH List <gendispatch@ietf.org>
References: <CAChr6SwpLsJ0S4jkvWL4DPys0Y9pvJwWhZtbr7E6fvFioRpsEQ@mail.gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <CAChr6SwpLsJ0S4jkvWL4DPys0Y9pvJwWhZtbr7E6fvFioRpsEQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------BYiod1O4wD3pBxRypFXwCPw5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/qZlXmrmlA_i65_D6Amxyick4fUQ>
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 05:54:32 -0000

On 06.09.23 06:38, Rob Sayre wrote:
> Hi,
>
> > Paul and I just submitted 
> https://datatracker.ietf.org/doc/html/draft-thomson-gendispatch-no-expiry-01
>
> I'm in favor, but maybe not for the same reasons.
>
> 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?

Eliot

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