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

Joel Halpern <jmh@joelhalpern.com> Mon, 04 September 2023 03:55 UTC

Return-Path: <jmh@joelhalpern.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 079A4C151522 for <gendispatch@ietfa.amsl.com>; Sun, 3 Sep 2023 20:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level:
X-Spam-Status: No, score=-2.198 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, URIBL_BLOCKED=0.001, 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=joelhalpern.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 ZW2wOwXJfSfS for <gendispatch@ietfa.amsl.com>; Sun, 3 Sep 2023 20:55:19 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 15C36C151099 for <gendispatch@ietf.org>; Sun, 3 Sep 2023 20:55:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4RfFCV6F1mz6G83W; Sun, 3 Sep 2023 20:55:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1693799718; bh=x10L7D62xCJZr+R8g3W+CPUXNKwhnPXz4M4WRy4/D08=; h=Date:Subject:From:To:References:Cc:In-Reply-To:From; b=W3jCB3iZ6DCSAwBKVLslCLVd5hS66VC70XOk0bajuhlw6sfHdjMrfDOcQWQNjE89t vKv7AZVTA98Ka1JoS5nkSYINl+v1KVfiGTPT65NxnFyHNQM1DHfVLnirDzjuc2H+/9 mAN8edD081ehnlfJcw+Y4kiqys0LORQ90dFUwuUo=
X-Quarantine-ID: <srChj8r0Yd0u>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.20.19] (unknown [50.233.136.230]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4RfFCV05cZz6G7hL; Sun, 3 Sep 2023 20:55:17 -0700 (PDT)
Message-ID: <14f3eea4-972b-30b7-5c0b-bcca398d15ca@joelhalpern.com>
Date: Sun, 03 Sep 2023 23:55:13 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
To: Martin Thomson <mt@lowentropy.net>, "gendispatch@ietf.org" <gendispatch@ietf.org>
References: <6036cbfa3f204dcebdd2a2393a6101ab@huawei.com> <9b9a6c68-877b-42c5-9231-e95f0df4e190@betaapp.fastmail.com> <4cb7e10e-673d-27cf-1115-d721c5aa1a1e@cs.tcd.ie> <ed7b3d50-25d2-d82d-3514-3d5282f18c56@joelhalpern.com> <90816281-ce30-2112-4ea5-355e14105e06@gmail.com> <f99e9200-1650-a011-e3b3-e9554ff3832b@joelhalpern.com>
Cc: Paul Hoffman <paul.hoffman@icann.org>
In-Reply-To: <f99e9200-1650-a011-e3b3-e9554ff3832b@joelhalpern.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/cX_IwkeBypGOWo3vP9cqIM5_rY4>
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 03:55:23 -0000

In hopes that it will help, let me try asking the question a different way.

One of the things the datatracker does is report on the Internet Drafts 
that are associated with a working group, but not currently adopted.  It 
does not include in that report expired Internet Drafts.  That 
limitation is very helpful.  If we remove expiration, do you propose 
that we instead put in a date mark that tells the system when to stop 
including the draft in the associated drafts list?  If so, how is that 
substantively different from the current practice?

Yours,

Joel

On 9/3/2023 10:57 PM, Joel Halpern wrote:
> I can live with that.  There probably are several ways to skin this 
> cat so that new folks looking at our IDs don't get confused about what 
> is current and what is not being considered.
>
> Yours,
>
> Joel
>
> On 9/3/2023 10:52 PM, Brian E Carpenter wrote:
>> On 04-Sep-23 13:22, Joel Halpern wrote:
>>> I think forcing tombstones would be a very good idea.  Deciding when to
>>> do so may be more than a little interesting.
>>
>> Tombstones were nothing but a nuisance when they existed. What's the 
>> point?
>> It just adds cruft to https://www.ietf.org/archive/id/.
>>
>> Of course, if an author *wants* to submit an I-D saying "This idea has
>> been abandoned", that would be fine, but I don't think there will be
>> many takers.
>>
>> My suggestion (just sent) is simply to make drafts >1 year old invisible
>> in the default search.
>>
>>    Brian
>>
>>>
>>> Yours,
>>>
>>> Joel
>>>
>>> On 9/3/2023 9:06 PM, Stephen Farrell wrote:
>>>>
>>>> Hiya,
>>>>
>>>> On 04/09/2023 01:23, Martin Thomson wrote:
>>>>
>>>>> 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.
>>>>
>>>> The draft seems fine to me. I'd suggest adding a
>>>> recommendation that it'd be useful to publish a
>>>> tombstone version for drafts that are no longer
>>>> under consideration (at that point in time) as I
>>>> do think we have a small problem with drafts that
>>>> are going nowhere, but that not being visible to
>>>> readers. Not a big deal, but could be worthwhile,
>>>>
>>>> Cheers,
>>>> S.
>>>>
>>>>
>>>
>