Re: [Tools-discuss] disappearing IDs on www.ietf.org

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 10 September 2020 17:45 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF043A0BCD for <tools-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 10:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhiKgdAD-BUU for <tools-discuss@ietfa.amsl.com>; Thu, 10 Sep 2020 10:45:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCC8F3A0E61 for <tools-discuss@ietf.org>; Thu, 10 Sep 2020 10:45:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id D93C7389DD for <tools-discuss@ietf.org>; Thu, 10 Sep 2020 13:24:13 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kFSeQ1Oeb9F6 for <tools-discuss@ietf.org>; Thu, 10 Sep 2020 13:24:13 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id EC7C7389DC for <tools-discuss@ietf.org>; Thu, 10 Sep 2020 13:24:12 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6B5127B for <tools-discuss@ietf.org>; Thu, 10 Sep 2020 13:45:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss@ietf.org
In-Reply-To: <84c8d593-c7b6-4327-338f-9b2b0e7a36e0@levkowetz.com>
References: <8657.1599751932@localhost> <84c8d593-c7b6-4327-338f-9b2b0e7a36e0@levkowetz.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 10 Sep 2020 13:45:24 -0400
Message-ID: <8656.1599759924@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/zttP0bVimMwaNiKE_z5gdSMVit0>
Subject: Re: [Tools-discuss] disappearing IDs on www.ietf.org
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2020 17:45:41 -0000

Henrik Levkowetz <henrik@levkowetz.com> wrote:
    > On 2020-09-10 17:32, Michael Richardson wrote:
    >>
    >> I had given a link to a document:
    >> https://www.ietf.org/id/draft-richardson-opsawg-securehomegateway-mud-04.html
    >>
    >> I thought I was smart and modern to give them the HTML rendered link.
    >> But, two hours later, I found a few stupid typos and posted -05.  The
    >> -04 content above went away.  This is a surprising change from how
    >> tools.ietf.org copy behaves.

    > The URL path that behaves the same way as tools.ietf.org/id/ is this:

    >   https://www.ietf.org/archive/id/

okay.
  "archive" because that's where the draft goes after it's no longer current.

1) Would some kind of 30x redirect make sense?
2) Or maybe a custom 404 error document that suggested maybe look there?
   {obviously, both are somewhat active content, which may be undesireable}

I think that we need to think about how to deal with the many different links
we have.  (this is a group question, not a Henrik-only question...)

In the meantime, I guess the DT status page is the best way to refer to a
document.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide