Re: [OAUTH-WG] [Errata Rejected] RFC8176 (6314)

Benjamin Kaduk <> Tue, 20 October 2020 16:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2F1303A1186 for <>; Tue, 20 Oct 2020 09:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id oUCWZPnrGFCV for <>; Tue, 20 Oct 2020 09:24:25 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E051D3A1183 for <>; Tue, 20 Oct 2020 09:24:24 -0700 (PDT)
Received: from ([]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by (8.14.7/8.12.4) with ESMTP id 09KGOHfl014560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 20 Oct 2020 12:24:21 -0400
Date: Tue, 20 Oct 2020 09:24:16 -0700
From: Benjamin Kaduk <>
Message-ID: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
Archived-At: <>
Subject: Re: [OAUTH-WG] [Errata Rejected] RFC8176 (6314)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Oct 2020 16:24:26 -0000

On Tue, Oct 20, 2020 at 09:21:45AM -0700, RFC Errata System wrote:
> Errata reports are for reporting issues with the authoritative RFC version(s) as published by the RFC Editor.  RFC 8176 predates the usage of the "v3 XML" format, so the plain text version is the authoritative one, and thus questions of HTML links are irrelevant for it.

For what it's worth, this "bad HTML link" situation occurs with some
regularity -- the "html" versions of non-v3-XML RFCs are created by running
a script over the text version.  The script uses heuristics to convert
certain types of text into links, and "Section <N>" gets expanded to this
document unless followed by "of RFC <Y>".  I believe this script is
open-source and patches would be welcome, though I don't know the location
of the source-code repository in question off the top of my head.