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

Eliot Lear <lear@lear.ch> Mon, 04 September 2023 07:34 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 21859C15155F; Mon, 4 Sep 2023 00:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.988
X-Spam-Level:
X-Spam-Status: No, score=-0.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" 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 P53kHMl5taKV; Mon, 4 Sep 2023 00:34:40 -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 7D41EC151544; Mon, 4 Sep 2023 00:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1693812852; bh=bN5DFEFhGyCYx2/pRgjHxoWraxY8KmK69S08Cn0fyfs=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=cIoA7uqj75n2w4SnF06vCiLfzEhJxi6HaS78Vmgg9YwhbZmVx7IkJT1oyPqsmT+Yq lpTWLVi1EmplqlzBP74rBTCQJb3K0q2s6sk8FkeaHEb/XUb8W5zM0vXic/GilpNTNb 9cQsFBsCZzM/AXuiwfBMHJ5sNfK2tlX0l8K09tkY=
Received: from [IPV6:2001:420:c0c0:1011::d] ([IPv6:2001:420:c0c0:1011:0:0:0:d]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-22ubuntu3) with ESMTPSA id 3847YB1e1428997 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 4 Sep 2023 09:34:12 +0200
Message-ID: <7f90dd25-9d77-b97c-04a4-98950713c652@lear.ch>
Date: Mon, 04 Sep 2023 09:34:09 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US
To: Martin Thomson <mt@lowentropy.net>, "gendispatch@ietf.org" <gendispatch@ietf.org>
Cc: GENDISPATCH Chairs <gendispatch-chairs@ietf.org>, Paul Hoffman <paul.hoffman@icann.org>
References: <6036cbfa3f204dcebdd2a2393a6101ab@huawei.com> <9b9a6c68-877b-42c5-9231-e95f0df4e190@betaapp.fastmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <9b9a6c68-877b-42c5-9231-e95f0df4e190@betaapp.fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/crLrgPEFzqpb5ivQQfGI-6RyZi0>
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: Mon, 04 Sep 2023 07:34:45 -0000

I don't mind drafts hanging out somewhere accessible, but can we 
separate expiry from removal or archiving?

We already have a problem with internet-drafts being misrepresented as 
being more than they are.  Right now, at least someone reading the thing 
can point to the top and say, “Hey! This draft expired!”  In fact, I 
would love to add a watermark on a draft that is expired; diagonal for 
HTML and PDF, and more prominent top and bottom for text.

Also, I would suggest that rsync and other tools not have to retrieve 
expired work.  The drafts directory is cluttered as it is.

Also, as ISE I use the expiration as a signal that the authors may have 
lost interest in their work.  I'm sure WG chairs do the same.

Eliot

On 04.09.23 02:23, Martin Thomson wrote:
> On Fri, Sep 1, 2023, at 16:48, Pengshuping (Peng Shuping) wrote:
>> Do you feel the need that we meet at IETF 118?
>> Please let us know if you have any topic you'd like to discuss.
> Paul and I just submitted https://datatracker.ietf.org/doc/html/draft-thomson-gendispatch-no-expiry-01
>
> We've talked about this in the past.  This version contains a suggested response to the criticism that the last version received.
>
> This might not be justification for a meeting on its own, but if the group is meeting, we'd appreciate some time to discuss.
>