Re: [Alldispatch] Tombstones, Taking draft-thomson-gendispatch-no-expiry-03 forward

Benjamin Kaduk <kaduk@mit.edu> Sat, 27 January 2024 20:25 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F863C14F689 for <ietf@ietfa.amsl.com>; Sat, 27 Jan 2024 12:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=mit.edu
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 kzg72Ib2ZiaO for <ietf@ietfa.amsl.com>; Sat, 27 Jan 2024 12:25:47 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68320C14F68D for <ietf@ietf.org>; Sat, 27 Jan 2024 12:25:47 -0800 (PST)
Received: from kduck.mit.edu (c-73-235-241-23.hsd1.ca.comcast.net [73.235.241.23]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 40RKPeJv017994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 27 Jan 2024 15:25:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1706387145; bh=LpVx9QyxTfjiHYscUzK/4mpgoOlPRkUuRMGiYigItTs=; h=Date:From:Subject:Message-ID:MIME-Version:Content-Type; b=kC2AwQNpfoaLuBi1nfLhpJq/bB1PLZaJsD0MiWBWHUNmdwmySSq/6tNtfGwqwFQhj fFUeLxcUA28GhINflDzIvvEz6qKI184pLrSWL/JzY2LDIB8dERe+R6rASn+uijeqee y2I+YLCUe6INAQYCJsBdsr9dFUJ3SgHdCt4PvpA9EH6H07DvOZm5/gKtgWHujP6RT6 +MDDhjwsanNhnh8gt17T3gXz1Io+iXj2QgezF2DbkrzECjmg4QMvhY7cZC6qsAMO1F HTlga1/X5/le1ra8kFhw+68U61YSSKsfeMcrDmedt6V/QfuZh8Wvg8+g/y36jTqHa3 ms/CVBvtlwg7w==
Date: Sat, 27 Jan 2024 12:25:40 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: John R Levine <johnl@taugh.com>
Cc: alldispatch@ietf.org, IETF general list <ietf@ietf.org>
Subject: Re: [Alldispatch] Tombstones, Taking draft-thomson-gendispatch-no-expiry-03 forward
Message-ID: <ZbVmxD6evfDhrP5g@kduck.mit.edu>
References: <0c95d612-e2f6-f3ce-2d5b-3956afd6dacd@taugh.com> <ZbQhJqsYJjdfCBij@kduck.mit.edu> <f0b39919-8640-c612-4952-e03b1c59b610@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <f0b39919-8640-c612-4952-e03b1c59b610@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/69jfYEhC0JJ5FHzSIR3LsZT_P70>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2024 20:25:51 -0000

On Fri, Jan 26, 2024 at 05:09:31PM -0500, John R Levine wrote:
> On Fri, 26 Jan 2024, Benjamin Kaduk wrote:
> > > Unless the plan is to have the tombstone contain text from the authors
> > > explaining why they abandoned the draft (good luck with that), what
> > > advantage would that have over the datatracker saying the draft is inactive?
> > 
> > It makes it harder to jump directly to the text of the draft without having
> > seen the notation about the draft's status.  (That is, if you start just
> > from a draft name or a version-less link, you get the tombstone; you'd need
> > to go straight to a version-specific link to skip it.)
> 
> When I go to the URL with the draft name and no version, I see the
> datatracker page that says Expired in a couple of places and has an ugly
> orange box that says in bold face "This Internet-Draft is no longer active."
> 
> I'm trying to imagine a scenario where someone fails to understand what that
> means and instead needs to download a file that also says "It's dead, Jim."
> What am I missing?

In the circles I frequent, there's a decent number of links to the
html(ized) version of a draft, such as
https://datatracker.ietf.org/doc/html/draft-ietf-kitten-gssapi-v3-guide-to
where "expired" is hiding in a sidebar that I (at least) have trained
myself to basically ignore.  The situation is more as you describe if I
were to go to the main datatracker page,
https://datatracker.ietf.org/doc/draft-ietf-kitten-gssapi-v3-guide-to/ .
So I think it rather depends on which "URL with the draft name and no
version" you are thinking of/visiting.

> I suppose if you rsync the I-D directory you only see the drafts, but I'd
> think the overlap between people who are motivated enough to set up rsync
> and those don't understand how to check for expired or inactive would be
> rather small.

Agreed.

-Ben