Htmlized legacy RFCs are created by a script that uses heuristics to add
formatting to the canonical text document. One of the limitations of the
script is that it does not know when a section link is to another
document.
For RFCs published since we switched to XML v3 two years ago, the HTML i
I agree with this change, but with one caveat (already expressed in the PR)
that an AS should be aware that clients can now send scope, resource, and
authorization_details parameters together on a single request. It’s not up to
RAR to define how all of those fit together, but an AS implementing
I personally agree with this report, the new proposed wording is better.
OAuth 2.1 editors, please take note!
— Justin
> On Jun 22, 2021, at 8:01 PM, Benjamin Kaduk wrote:
>
> This looks correct to me; could the authors/WG please confirm?
>
> Thanks,
>
> Ben
>
> On Thu, Jun 17, 2021 at 12:
The following errata report has been submitted for RFC7519,
"JSON Web Token (JWT)".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6622
--
Type: Editorial
Reported by: Padmanarayanan SR
Sect
