IETF Logo Mail Archive

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

Benjamin Kaduk <kaduk@mit.edu> Tue, 20 October 2020 16:31 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0544E3A0ADF for <oauth@ietfa.amsl.com>; Tue, 20 Oct 2020 09:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, 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 43wToi4I57ZU for <oauth@ietfa.amsl.com>; Tue, 20 Oct 2020 09:31:53 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7610C3A0AC5 for <oauth@ietf.org>; Tue, 20 Oct 2020 09:31:53 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 09KGVjPQ017589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 20 Oct 2020 12:31:50 -0400
Date: Tue, 20 Oct 2020 09:31:45 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: David Brossard <dbrossard@salesforce.com>
Cc: David Brossard <david.brossard@gmail.com>, mbj@microsoft.com, phil.hunt@yahoo.com, oauth@ietf.org, tonynad@microsoft.com, rfc-editor@rfc-editor.org
Message-ID: <20201020163145.GK39170@kduck.mit.edu>
References: <20201020162145.1A4FCF40719@rfc-editor.org> <20201020162416.GI39170@kduck.mit.edu> <CAKSYhSRXX8sHqYXi_PQ9wumkUdu+os6edSZNJ12oKOt6ZUwTeQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAKSYhSRXX8sHqYXi_PQ9wumkUdu+os6edSZNJ12oKOt6ZUwTeQ@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Y_2viaNGqu9A5z_BtLEV4WHJ3_0>
Subject: Re: [OAUTH-WG] [Errata Rejected] RFC8176 (6314)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 16:31:55 -0000

[adding back rfc-editor@rfc-editor.org]

Hi David,

I am quite far removed from the actual operation of the script and the
rfc-editor.org website, so I don't know the answer to your question.  That
said, my understanding is that it's set up with automation that assumes the
script is idempotent, and can regenerate various bits from scratch in
certain cases, so a manual edit might not be very reliable.

-Ben

On Tue, Oct 20, 2020 at 09:26:21AM -0700, David Brossard wrote:
> Thanks Ben (and apologies about the double submission).
> 
> In this case, given the reference is not an RFC, that would explain why the
> script failed. Can we do a manual fix after the script has run to update
> the RFC?
> 
> On Tue, Oct 20, 2020 at 9:24 AM Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> > On Tue, Oct 20, 2020 at 09:21:45AM -0700, RFC Errata System wrote:
> > >  --VERIFIER NOTES--
> > > 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.
> >
> > -Ben
> >
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
> >
> 
> 
> -- 
> *David Brossard*
> Sr. Director of Product Management
> Identity, Authentication, Federation, and Single Sign-On | Salesforce
> c: +1 502-922-6538 (US) | +1 236-333-6379 (Canada)
> Learn more about identity here
> <https://trailhead.salesforce.com/content/learn/modules/identity_basics/identity_basics_product>
> |
> Identity for Developers
> <https://developer.salesforce.com/developer-centers/identity/>

v2.23.0 | Report a Bug | By Email