IETF Logo Mail Archive

Re: [Tools-discuss] [rfc-i] Broken relative links to I-Ds in RFCs

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 28 May 2023 02:01 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 F0CF1C14CE55 for <tools-discuss@ietfa.amsl.com>; Sat, 27 May 2023 19:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 (2048-bit key) header.d=gmail.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 YcQP03UIC7uR for <tools-discuss@ietfa.amsl.com>; Sat, 27 May 2023 19:01:47 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 3C7A0C14CF15 for <tools-discuss@ietf.org>; Sat, 27 May 2023 19:01:47 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-64d2a613ec4so1594413b3a.1 for <tools-discuss@ietf.org>; Sat, 27 May 2023 19:01:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685239306; x=1687831306; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=sSFka4SaAVLGXifyEonaskfGud/ZW2ysspPfPUQwnHs=; b=Yl7rzmrE8G05jeqAzG4pzf/zaIj6Zu6xsYyHnLTcyw86QYEJCsZZUaIXAhCsa3Dl8C ySX1Zd/DcwAq90ic1JaFX9r9YK55OeCw/XJeHndv9/o+Lr+/bz2v8DZJZbXKs/Pxl8pE yrrwrhPP3AUeARlEjWC4FsSuonFQ5xablpwFgVNUvekb57Zff0g5syturSOCmXLfQIqp RVDKTsvVn8H4l4Po/GO0Qcgct2j6/8f6cbQwUCC0dcBlM1+/sVFMLQV6QAi/zEYKIdOj bXMwonZ9L3r5RY2t7LDspsAJnIilAB/dM2/jQYRgmHBl9XkzeNu4KSIybcvapIoj2NCT 86+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685239306; x=1687831306; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=sSFka4SaAVLGXifyEonaskfGud/ZW2ysspPfPUQwnHs=; b=SGyw0JOFTBDJkvnyNVIDiwEIt2cUEUrMoyVa0tGXZSoCcGGkGtVXKk4kyAKiOcHHKp Qx/dYHyNmS34csC/9X9QU75yFBQJ/Q+BPMijGYjsjb4AmrzNJFG19ZkA7zR93sXlaqpQ A1+BAJq3uUqxCMhS+G/0QpU/cZvQzJ/OFLB9CoLORILJH5AN4rTbr+zY92Td2xdQ+NjW 6ykmSix5B6wIMsZCe40mLp9QFg2kDfXAFTKmSRcVd8M1VSIDzCFnZVKwNgQ1z9N8JUMo UEKeD6Zpjy4lhyxn8P+iapAO8uTu98vmMGVmbYU8aooSJ7BohfotpJVRcdiZx9h6Eydk o9gA==
X-Gm-Message-State: AC+VfDz56Sc2fYfnnRG3gGswPSGfFKtxT/3DSxhCGfxTIR25rhulqCVI Abtndgv+v8OK+iwgBDUEVZE=
X-Google-Smtp-Source: ACHHUZ7yHVDJ6YKqgI81QVVoxn8X1sMpqGP908Am/VJxVT5uWajG8IIo835qOJW7ISyMNB/0SIqacA==
X-Received: by 2002:a05:6a00:1492:b0:64c:c841:4e8a with SMTP id v18-20020a056a00149200b0064cc8414e8amr9787246pfu.22.1685239306312; Sat, 27 May 2023 19:01:46 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id d2-20020a631d42000000b00520f316ebe3sm4638958pgm.62.2023.05.27.19.01.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 27 May 2023 19:01:45 -0700 (PDT)
Message-ID: <949aa033-47a7-9914-e8d9-2a4bd45909c5@gmail.com>
Date: Sun, 28 May 2023 14:01:41 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Eric Rescorla <ekr@rtfm.com>, tools-discuss <tools-discuss@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>
References: <CABcZeBPn4+UyTyx6ETSnJ=twYosN1N5tmFjQOaGS5ohMMGF9Rw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CABcZeBPn4+UyTyx6ETSnJ=twYosN1N5tmFjQOaGS5ohMMGF9Rw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/6C1SEW_eopK7EiZ58k2njsm-CZw>
Subject: Re: [Tools-discuss] [rfc-i] Broken relative links to I-Ds in RFCs
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 28 May 2023 02:01:51 -0000

On 28-May-23 13:45, Eric Rescorla wrote:
> Hi folks,
> 
> I've recently noticed that the links to I-Ds in RFCs on RFC-editor.org do not work proper
> 
> For instance, here is RFC 8555 https://www.rfc-editor.org/rfc/rfc8555 <https://www.rfc-editor.org/rfc/rfc8555>. It contains a link to draft-ietf-acme-caa-06. Here is the HTML:
> 
> [<a id="ref-ACME-CAA">ACME-CAA</a>] Landau, H., "CAA Record Extensions for Account URI and ACME Method Binding", Work in Progress, <a href="./draft-ietf-acme-caa-06">draft-ietf-acme-</a><a href="./draft-ietf-acme-caa-06">caa-06</a>, January 2019.
> 
> Unfortunately, there is nothing at:
> https://www.rfc-editor.org/rfc/draft-ietf-acme-caa-06 <https://www.rfc-editor.org/rfc/draft-ietf-acme-caa-06>
> 
> Spot-checking, this seems to be true for other ID references in this RFC and others.

Oops, it looks as if the .html files at rfc-editor are exact copies of the htmlized versions at datatracker.ietf.org, where that form of relative URL works fine.

     Brian

v2.23.0 | Report a Bug | By Email