[jose] [Editorial Errata Reported] RFC7515 (4554)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 04 December 2015 15:20 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20C521A7025 for <jose@ietfa.amsl.com>; Fri, 4 Dec 2015 07:20:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 al_q1nI6nPUw for <jose@ietfa.amsl.com>; Fri, 4 Dec 2015 07:20:14 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE6F1A87ED for <jose@ietf.org>; Fri, 4 Dec 2015 07:19:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F0B12180006; Fri, 4 Dec 2015 07:17:26 -0800 (PST)
To: mbj@microsoft.com, ve7jtb@ve7jtb.com, n-sakimura@nri.co.jp, stephen.farrell@cs.tcd.ie, Kathleen.Moriarty.ietf@gmail.com, odonoghue@isoc.org, ietf@augustcellars.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151204151726.F0B12180006@rfc-editor.org>
Date: Fri, 04 Dec 2015 07:17:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/Ceg9PUYzf_sQe9EhmSJBoIunapU>
X-Mailman-Approved-At: Fri, 04 Dec 2015 07:42:53 -0800
Cc: simon@bastli.ethz.ch, jose@ietf.org, rfc-editor@rfc-editor.org
Subject: [jose] [Editorial Errata Reported] RFC7515 (4554)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 04 Dec 2015 15:20:16 -0000
The following errata report has been submitted for RFC7515, "JSON Web Signature (JWS)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7515&eid=4554 -------------------------------------- Type: Editorial Reported by: Simon <simon@bastli.ethz.ch> Section: 2 Original Text ------------- Base64url Encoding Base64 encoding using the URL- and filename-safe character set defined in Section 5 of RFC 4648 [RFC4648], with all trailing \\'=\\' characters omitted (as permitted by Section 3.2) and without the inclusion of any line breaks, whitespace, or other additional characters. Note that the base64url encoding of the empty octet sequence is the empty string. (See Appendix C for notes on implementing base64url encoding without padding.) Corrected Text -------------- Base64url Encoding Base64 encoding using the URL- and filename-safe character set defined in Section 5 of RFC 4648 [RFC4648], with all trailing \\'=\\' characters omitted (as permitted by Section 3.2 of RFC 4648) and without the inclusion of any line breaks, whitespace, or other additional characters. Note that the base64url encoding of the empty octet sequence is the empty string. (See Appendix C for notes on implementing base64url encoding without padding.) Notes ----- in the html version https://tools.ietf.org/html/rfc7515 the link on \\"Section 3.2\\" goes to Section 3.2 of RFC7515 but it should go to Section 3.2 of RFC4648. Not sure how the automatic link generation is made (or is it manual?), so i would propose explicitly saying \\"Section 3.2 of RFC 4648\\". 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 (IESG) 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] [Editorial Errata Reported] RFC7515 (4554) RFC Errata System
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Jim Schaad
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… John Bradley
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Kathleen Moriarty
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… John Bradley
- [jose] [Errata Held for Document Update] RFC7515 … RFC Errata System
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Mike Jones
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Kathleen Moriarty
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… John Bradley
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Jim Schaad
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Kathleen Moriarty
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Kathleen Moriarty
- Re: [jose] [Editorial Errata Reported] RFC7515 (4… Megan Ferguson