IETF Logo Mail Archive

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

Benjamin Kaduk <kaduk@mit.edu> Thu, 15 August 2019 04:09 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D8E12001A for <jose@ietfa.amsl.com>; Wed, 14 Aug 2019 21:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 A20tmCLOBjlI for <jose@ietfa.amsl.com>; Wed, 14 Aug 2019 21:09:16 -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 D50AC120018 for <jose@ietf.org>; Wed, 14 Aug 2019 21:09:15 -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 x7F48vf1029518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Aug 2019 00:09:00 -0400
Date: Wed, 14 Aug 2019 23:08:57 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Jim Schaad <ietf@augustcellars.com>
Cc: 'RFC Errata System' <rfc-editor@rfc-editor.org>, mbj@microsoft.com, ve7jtb@ve7jtb.com, n-sakimura@nri.co.jp, rdd@cert.org, odonoghue@isoc.org, jose@ietf.org, avinash44491@gmail.com
Message-ID: <20190815040857.GL88236@kduck.mit.edu>
References: <20190813221952.2D65BB813FF@rfc-editor.org> <02c501d55253$1c2249b0$5466dd10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <02c501d55253$1c2249b0$5466dd10$@augustcellars.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/CYJPoGeAtMe4OeeDTLeFth_Lsyc>
Subject: Re: [jose] [Editorial Errata Reported] RFC7515 (5810)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 04:09:20 -0000

My recollection is that the RFC Editor will usually delete these, yes.

-Ben

On Tue, Aug 13, 2019 at 08:48:14PM -0700, Jim Schaad wrote:
> 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 <rfc-editor@rfc-editor.org> 
> Sent: Tuesday, August 13, 2019 3:20 PM
> To: mbj@microsoft.com; ve7jtb@ve7jtb.com; n-sakimura@nri.co.jp; rdd@cert.org; kaduk@mit.edu; odonoghue@isoc.org; ietf@augustcellars.com
> Cc: avinash44491@gmail.com; jose@ietf.org; rfc-editor@rfc-editor.org
> 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:
> https://www.rfc-editor.org/errata/eid5810
> 
> --------------------------------------
> Type: Editorial
> Reported by: Avinash Kumar Singh <avinash44491@gmail.com>
> 
> 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
> --------------
> 
> 
> Notes
> -----
> The Hyperlink used for JWA and JWE is not working and pointing to the same RFC 7515.
> 
> 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. 
> 
> --------------------------------------
> 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
> 
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose

v2.23.0 | Report a Bug | By Email