From nobody Sat May 27 19:06:26 2023 Return-Path: X-Original-To: rfc-interest@ietfa.amsl.com Delivered-To: rfc-interest@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC02C14F726 for ; Sat, 27 May 2023 19:06:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.894 X-Spam-Level: X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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=rtfm-com.20221208.gappssmtp.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 o7VcrPN9ZTGu for ; Sat, 27 May 2023 19:06:20 -0700 (PDT) Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (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 8EE03C15106F for ; Sat, 27 May 2023 19:06:20 -0700 (PDT) Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-565ca65e7ffso8375207b3.0 for ; Sat, 27 May 2023 19:06:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1685239579; x=1687831579; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HxUiWHQn4lHvRp+Wtb9YuP1Ae7KQY/oHJyfPOEl/+os=; b=QGQ4WvQsLW67/1sjmz29Til8mkWd9foOdwLsCpOoNrqNstTt/ceuOR7eXWvAH98CtI z6GQY44xHtCdBDDFctHPngyuLegcViCjWlENgNW2aRq5c6rlOIaTxzjBXU1BAA80qzdp ChHvmX0FgUHhjd3HLeSmJfq1vodQONDgRGGCXJpQ+zE0ti6tRgsiwI40s7nanscT+UkZ 1mqcpTuzl01HKctsL236Xuqdjo9MdqkfiZoF4dHfm2l49AcyV5YjfwbgXhsY/jqb+F0F 3lLelinWhUpZFdphWNktDl1FKns1qSWd2j4frEchIc7bM5/TfiBoXCjD8ezCHJ4c9eq+ qLMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685239579; x=1687831579; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=HxUiWHQn4lHvRp+Wtb9YuP1Ae7KQY/oHJyfPOEl/+os=; b=AG5xuxLJtKzEyR6QILE6GVTmbXYK+e5vtpshrucdAK23Z2Uofn8gB9mOt5QCUggVUN o151keMyxSAoPEVb/GnSv69KKiKoMRV1TCCt/CcLNsZ23jw0ExxOGut5P2UFjPBp/rlW tNggIPxOj3xr6jKmj9RjxxE8U/tqOFe+qNSG2QPSPfResql2YTaypaZP6KJ42GoHpFqM j61wh4YDOTWolocb1Z4RiwZeICZaaZikIGW48n830/p8L/gcufqxGhEq7TTNC1+VCetm HYbAR6sva12dbjKmsc2+ysMFfUj69EZazLKrZw5dv1RirLUWm7cCok3GG+nVYOztSX0k 02RA== X-Gm-Message-State: AC+VfDzPEf3Ff1CM/fQYAsfw+Vpx+CHWDCAIweh6hWyjZo+DIOj6E0H2 iW1D0LebTc7BQ5qf47itD9xYmcYDfVnOpJfjUZN5LTcFyBYHH6Jc X-Google-Smtp-Source: ACHHUZ7IUcsNsTSmXO5TTlHwo9VHLCylfMQ1MzzyDx5qdWdRHf8HljhjGbPbZAhUYTsnMYLGVFdSF6ZByhKtdPW3ZCI= X-Received: by 2002:a0d:e891:0:b0:565:d517:e714 with SMTP id r139-20020a0de891000000b00565d517e714mr2814751ywe.25.1685239579534; Sat, 27 May 2023 19:06:19 -0700 (PDT) MIME-Version: 1.0 References: <949aa033-47a7-9914-e8d9-2a4bd45909c5@gmail.com> In-Reply-To: <949aa033-47a7-9914-e8d9-2a4bd45909c5@gmail.com> From: Eric Rescorla Date: Sat, 27 May 2023 19:05:43 -0700 Message-ID: To: Brian E Carpenter Cc: tools-discuss , RFC Interest Content-Type: multipart/alternative; boundary="000000000000800c1705fcb76a86" Archived-At: Subject: Re: [rfc-i] Broken relative links to I-Ds in RFCs X-BeenThere: rfc-interest@rfc-editor.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: "A list for discussion of the RFC series and RFC Editor functions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2023 02:06:24 -0000 --000000000000800c1705fcb76a86 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, May 27, 2023 at 7:01=E2=80=AFPM Brian E Carpenter < brian.e.carpenter@gmail.com> wrote: > 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: > > > > [ACME-CAA] Landau, H., "CAA Record Extension= s > for Account URI and ACME Method Binding", Work in Progress, href=3D"./draft-ietf-acme-caa-06">draft-ietf-acme- href=3D"./draft-ietf-acme-caa-06">caa-06, 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 RF= C > and others. > > Oops, it looks as if the .html files at rfc-editor are exact copies of th= e > htmlized versions at datatracker.ietf.org, where that form of relative > URL works fine. > Unfortunately, this seems to be the version that both DDG and Google offer (though Google actually shows tools.ietf.org first). -Ekr --000000000000800c1705fcb76a86 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, May 27, 2023 at 7:01=E2=80=AF= PM Brian E Carpenter <bri= an.e.carpenter@gmail.com> wrote:
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=3D"ref-ACME-CAA">ACME-CAA</a>] Landau, H.= , "CAA Record Extensions for Account URI and ACME Method Binding"= , Work in Progress, <a href=3D"./draft-ietf-acme-caa-06">dr= aft-ietf-acme-</a><a href=3D"./draft-ietf-acme-caa-06"&g= t;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 R= FC 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 relativ= e URL works fine.

Unfortunately, this s= eems to be the version that both DDG and Google offer (though Google actual= ly shows tools.ietf.org first).

-Ekr
--000000000000800c1705fcb76a86--