MIME-Version: 1.0
References: <20190705135606.F345BB8223A@rfc-editor.org>
In-Reply-To: <20190705135606.F345BB8223A@rfc-editor.org>
From: William Denniss <rfc8252@wdenniss.com>
Date: Fri, 5 Jul 2019 09:51:12 -0700
Message-ID: <CAD=M-Tn08T75F3ft2JDfpSqJ+smTu73WP1eM9-+bQ+GHh8jMCA@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc8252@wdenniss.com, rfc8252@ve7jtb.com, rdd@cert.org, kaduk@mit.edu, 
 Hannes.Tschofenig@gmx.net, rifaat.ietf@gmail.com, dziekan.jan@gmail.com, 
 oauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000069db04058cf1e733"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Qtk_axe3ndmN7PQYgFf_7tZyShM>
Subject: Re: [OAUTH-WG] [Editorial Errata Reported] RFC8252 (5776)
Precedence: list

--00000000000069db04058cf1e733
Content-Type: text/plain; charset="UTF-8"

This is an issue with the HTML auto generation, not the normative document.
I believe this errata should be rejected.

William

On Fri, 5 Jul 2019 at 06:56, RFC Errata System <rfc-editor@rfc-editor.org>
wrote:

> The following errata report has been submitted for RFC8252,
> "OAuth 2.0 for Native Apps".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5776
>
> --------------------------------------
> Type: Editorial
> Reported by: Jan Dziekan <dziekan.jan@gmail.com>
>
> Section: GLOBAL
>
> Original Text
> -------------
>
>
> Corrected Text
> --------------
>
>
> Notes
> -----
> RFC8252 references specific Sections of RFC6749, however urls are pointing
> to Sections in RFC8252.
> For example, in Section 6 there is a statement "code grant type per
> Section 4.1 of OAuth 2.0 [RFC6749]", where "Section 4.1" links to
> https://tools.ietf.org/html/rfc8252#section-4.1 instead of
> https://tools.ietf.org/html/rfc6749#section-4.1
> I have found such misplaced links in the following sections: 6, 8.2, 8.4,
> 8.5, 8.6, 8.12
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8252 (draft-ietf-oauth-native-apps-12)
> --------------------------------------
> Title               : OAuth 2.0 for Native Apps
> Publication Date    : October 2017
> Author(s)           : W. Denniss, J. Bradley
> Category            : BEST CURRENT PRACTICE
> Source              : Web Authorization Protocol
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>

--00000000000069db04058cf1e733
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This is an issue with the HTML auto generation, not t=
he normative document. I believe this errata should be rejected.</div><div>=
<br></div><div>William</div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Fri, 5 Jul 2019 at 06:56, RFC Errata System &lt;<a=
 href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The fol=
lowing errata report has been submitted for RFC8252,<br>
&quot;OAuth 2.0 for Native Apps&quot;.<br>
<br>
--------------------------------------<br>
You may review the report below and at:<br>
<a href=3D"https://www.rfc-editor.org/errata/eid5776" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.rfc-editor.org/errata/eid5776</a><br>
<br>
--------------------------------------<br>
Type: Editorial<br>
Reported by: Jan Dziekan &lt;<a href=3D"mailto:dziekan.jan@gmail.com" targe=
t=3D"_blank">dziekan.jan@gmail.com</a>&gt;<br>
<br>
Section: GLOBAL<br>
<br>
Original Text<br>
-------------<br>
<br>
<br>
Corrected Text<br>
--------------<br>
<br>
<br>
Notes<br>
-----<br>
RFC8252 references specific Sections of RFC6749, however urls are pointing =
to Sections in RFC8252.<br>
For example, in Section 6 there is a statement &quot;code grant type per Se=
ction 4.1 of OAuth 2.0 [RFC6749]&quot;, where &quot;Section 4.1&quot; links=
 to <a href=3D"https://tools.ietf.org/html/rfc8252#section-4.1" rel=3D"nore=
ferrer" target=3D"_blank">https://tools.ietf.org/html/rfc8252#section-4.1</=
a> instead of <a href=3D"https://tools.ietf.org/html/rfc6749#section-4.1" r=
el=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/rfc6749#sec=
tion-4.1</a><br>
I have found such misplaced links in the following sections: 6, 8.2, 8.4, 8=
.5, 8.6, 8.12<br>
<br>
Instructions:<br>
-------------<br>
This erratum is currently posted as &quot;Reported&quot;. If necessary, ple=
ase<br>
use &quot;Reply All&quot; to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party=C2=A0 <br>
can log in to change the status and edit the report, if necessary. <br>
<br>
--------------------------------------<br>
RFC8252 (draft-ietf-oauth-native-apps-12)<br>
--------------------------------------<br>
Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: OAuth 2.0 for=
 Native Apps<br>
Publication Date=C2=A0 =C2=A0 : October 2017<br>
Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: W. Denniss, J. Bradley<=
br>
Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : BEST CURRENT PRACTICE<b=
r>
Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Web Authorization =
Protocol<br>
Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Security<br>
Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF<br>
Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br>
</blockquote></div></div>

--00000000000069db04058cf1e733--