Re: [rfc-i] standards for references/URLs in RFCs ? (Was: Re: archiving outlinks in RFCs)

Jay Daley <> Wed, 26 April 2023 08:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1BC47C14CF17 for <>; Wed, 26 Apr 2023 01:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Status: No, score=-6.896 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EdzjuF9n4wjM for <>; Wed, 26 Apr 2023 01:32:28 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::334]) (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 (Postfix) with ESMTPS id BB783C14CE5D for <>; Wed, 26 Apr 2023 01:32:22 -0700 (PDT)
Received: by with SMTP id 5b1f17b1804b1-3f1957e80a2so142100345e9.1 for <>; Wed, 26 Apr 2023 01:32:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1682497940; x=1685089940; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=9lDY9YPqSlNnVwGMRAVm7z4/bB01fUvonfI/ThuSQmo=; b=DLAuC3MouVC3IAWFCpVv1aToSN5Ve+EpcU1z+d7k+aSzelxC21WEZNaL63kLzaoWrI EQXUVMzOypMpAk1PGBs6A+i8UHAS5VIClT+kOYl0/RYMmz6rsRpw0ZchuJNzHb+43csX 2KJxIk0Eve1HFOHuG50QlG/+BVYFuLLJ9Tn1NMRxLbAg0/AzDmuicGzd3c3ideOQzBkO DtXjbHMTObsiY5sDyyjUPv62FnFhuQDJl7Ejk+ytDnIZEujqc+o4WwsPcZ1K7IOMSt0D SR/t3sDZGhaVbqrhQC4H3MAI8cznKO1Fq/U/rMiE4lUv4ZRmJfD2IIhzlu9d3JDgz/zi AEcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1682497940; x=1685089940; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9lDY9YPqSlNnVwGMRAVm7z4/bB01fUvonfI/ThuSQmo=; b=Is2AuHpH+HG3igFPqyKNpkjUV6BcWca9g56L/hRlcnJYFHW1Wiyx8OX7dMGRnnw0YA SpfIpNNzEvl3NbzBxCR5WNOyGtVTpN/tCjqqQiydMsyyHlsjOCAklVC7NkMRUmz/dUPs o/vT38IWdXgZ9w10RoVL5MiDqX9EvvDXULlZ/WVxcGFrGrUxMb5gyZj//qgLtKHrBU3b r9YsIvv/RNltOvDeCUokQlYtgxIOB4oiNLlK4rHvug6w4wb9k8yts2V0Z8hBIuf4Dhan R5tczy8BsRCbkAkOOcpvsu0rAl1sU5TIYzzBvq1MqFhP6a/+tM7tEfjdov6+7mtO6l48 bvDQ==
X-Gm-Message-State: AC+VfDy2KRiNrN2Kme9JRaz8a70/Ps5O/BwA7sw+w7kmAJ9GkUW7fvGz iup/Lh46evk3XpGQUrcLH/qfJw==
X-Google-Smtp-Source: ACHHUZ61uaRBCcXt0C5D+ComDM/TJubOC42YYftS/Rq/9Q0ipbxiLfrLi2khh2MRtm2HDf7ahZBfQA==
X-Received: by 2002:a05:6000:1a41:b0:2ef:bac1:9c48 with SMTP id t1-20020a0560001a4100b002efbac19c48mr1117423wry.6.1682497940217; Wed, 26 Apr 2023 01:32:20 -0700 (PDT)
Received: from ( []) by with ESMTPSA id m10-20020a5d56ca000000b002c54c9bd71fsm15101983wrw.93.2023. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2023 01:32:19 -0700 (PDT)
From: Jay Daley <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E29B8C3F-43F0-4AE8-A35F-29C778AE3393"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Wed, 26 Apr 2023 09:32:10 +0100
In-Reply-To: <ZEjKrJK/>
Cc: Alexis Rossi <>,
To: Toerless Eckert <>
References: <> <ZEjKrJK/>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <>
Subject: Re: [rfc-i] standards for references/URLs in RFCs ? (Was: Re: archiving outlinks in RFCs)
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: Wed, 26 Apr 2023 08:32:32 -0000

Hi Toerless

See for the specifics of referencing GitHub.


> On 26 Apr 2023, at 07:54, Toerless Eckert <> wrote:
> Alexis,
> Thanks a lot for the initiative, but before having more opinion about it, i would
> like to reconfirm our current policies for new draft->RFC, and what type of
> references/URLs are permitted/required by our process (IETF and RFC-editor).
> For example, in one of my ongoing WG drafts, WG members made the comment that
> a reference to a github location would not be looked upon favorably by RFC editor.
> Aka: inappropriate reference because it is not stable.
> In that particular case, the github file was part of a presentation given at a
> WG meeting in the past, so our plan for this reference is to use the IETF proceeding URL
> for the presentation instead.
> [ Which should be considered to be an eternally stable URL, one would hope, unless we
>  do get IETF LLC? web admins that like in almost all commercial web pages of our industry
>  seem to be run by admins that like to drive users mad by randomnly deleting important
>  reference/history information or just changing URLs for spite or some new wb page tooling
>  that "did not allow us to keep existing URLs" (typical excuse i hear). /rant ]
> Aka: I am totally unclear what type of URLs are or are not seen as
> appropriate today by IETF process/RFC-Editor, and if someone could point me to any
> reference we have (RFC ? ?), that would be lovely.
> As another example, when defining terms, i sometimes thought it would be appropriate
> to point to wikipedia. But given how the understanding of terms is changing over time,
> wikipedia definitions might be the worst references to use. Just think of all the
> technical terms we where fond of using (e.g.: blacklist) and that are now shunned/deprecated
> by us (not even sure what the right word for the process is ;-) - as one example category
> for this problem. If at all, it seems to me that references to wikipedia could
> really only go to an archived version of a wikipedia page that was used by the authors
> when writing the draft/RFC.
> Cheers
>    Toerless
> On Tue, Apr 25, 2023 at 11:50:24AM -0700, Alexis Rossi wrote:
>> Hi all,
>> I wanted to let the community know about something I’ve been working on. As you might know, one of my previous jobs was running the Wayback Machine, so when I started working with with this collection of RFCs one of my first thoughts was, “I wonder how many broken links are in these RFCs from the past few decades?” 
>> In general, the average lifespan of a URL before the content changes or disappears is on the order of 100 days. Fortunately for us, the links used in RFC references seem to be much more stable than that. For instance, so far I’ve only found one broken link in an RFC from the past 6 months [1].
>> Even though we favor these more stable URLs, some of them will eventually change or go 404 and having archival documents with link rot is something we can take steps to avoid in the future.
>> The first thing I wanted to do was just make sure we were archiving these outlinks somewhere. This won’t fix a broken link in the RFC, but at least the resource can be saved elsewhere for someone curious enough to go look (and potentially we could fix links in some version of the RFC in future).
>> The main services that are well qualified for this purpose are <> (run by the Internet Archive) and <> (run by Harvard Law School Library). I chose Archive-It, and when I approached them they offered us an account [2] with enough free data storage for our needs. Yay for non-profits supporting each other! 
>> So far I have used Archive-It to:
>> Archive <>, <>, <>, and <> (minus datatracker and the mail archive)
>> There are lots of references to these sites in RFCs, but I also wanted to preserve the contents for their own sake. I plan to revisit these sites once per year.
>> I am avoiding datatracker (except for outlinks from RFCs) because of concern about the extra traffic causing problems for the team that maintains the site.
>> I have not concentrated on archiving the mail archive yet, though I know some of it has been saved incidentally. 
>> Archive outlinks from RFCs
>> About once per quarter I’ll grab the outlinks from newly published RFCs and get them crawled. 
>> I am also going backwards through the entire series - I’ve started with the most recent RFCs (links are more likely to still be live) and am working my way back in time. 
>> There may be more room for improvements here, for example including archived links in RFCs from the start w here appropriate, or potentially defining a way for links to be self-healing in published RFCs. 
>> Please let me know if you have ideas or feedback on this.
>> Thanks,
>> Alexis
>> [1] RFC9311 published in September 2022, in Section 11 (Informative References) this link is 404: <>[2] <>
>> _______________________________________________
>> rfc-interest mailing list
> -- 
> ---
> _______________________________________________
> rfc-interest mailing list

Jay Daley
IETF Executive Director