Re: [jose] [Editorial Errata Reported] RFC7515 (5810)

Jim Schaad <> Wed, 14 August 2019 03:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 562EE12003F for <>; Tue, 13 Aug 2019 20:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vn4y6k6tDUC4 for <>; Tue, 13 Aug 2019 20:48:29 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CE13A12002F for <>; Tue, 13 Aug 2019 20:48:28 -0700 (PDT)
Received: from Jude ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 13 Aug 2019 20:48:18 -0700
From: Jim Schaad <>
To: 'RFC Errata System' <>,,,,,,
References: <>
In-Reply-To: <>
Date: Tue, 13 Aug 2019 20:48:14 -0700
Message-ID: <02c501d55253$1c2249b0$5466dd10$>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQENF8tTRIKNcl7mC+TvEgljDMynWaiKaxWw
Content-Language: en-us
X-Originating-IP: []
Archived-At: <>
Subject: Re: [jose] [Editorial Errata Reported] RFC7515 (5810)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Javascript Object Signing and Encryption <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 14 Aug 2019 03:48:32 -0000

This goes as a won't fix or delete because it is not a real errata.

The errata has been reported against the html-ized version of the RFC and not against the RFC proper.  How links work for the HTML-ized version is to link first to the reference and then you can go from there to the other document.

-----Original Message-----
From: RFC Errata System <> 
Sent: Tuesday, August 13, 2019 3:20 PM
Subject: [Editorial Errata Reported] RFC7515 (5810)

The following errata report has been submitted for RFC7515, "JSON Web Signature (JWS)".

You may review the report below and at:

Type: Editorial
Reported by: Avinash Kumar Singh <>

Section: 1

Original Text
 Cryptographic algorithms and identifiers for use with this
   specification are described in the separate JSON Web Algorithms (JWA)
   [JWA] specification and an IANA registry defined by that
   specification.  Related encryption capabilities are described in the
   separate JSON Web Encryption (JWE) [JWE] specification.

Corrected Text

The Hyperlink used for JWA and JWE is not working and pointing to the same RFC 7515.

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. 

RFC7515 (draft-ietf-jose-json-web-signature-41)
Title               : JSON Web Signature (JWS)
Publication Date    : May 2015
Author(s)           : M. Jones, J. Bradley, N. Sakimura
Category            : PROPOSED STANDARD
Source              : Javascript Object Signing and Encryption
Area                : Security
Stream              : IETF
Verifying Party     : IESG