Re: [jose] [Editorial Errata Reported] RFC7515 (4554)
"Jim Schaad" <ietf@augustcellars.com> Tue, 08 December 2015 18:08 UTC
Return-Path: <ietf@augustcellars.com>
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 CB3711A1A3C for <jose@ietfa.amsl.com>; Tue, 8 Dec 2015 10:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 coMkyNs-o-K6 for <jose@ietfa.amsl.com>; Tue, 8 Dec 2015 10:08:56 -0800 (PST)
Received: from smtp3.pacifier.net (smtp3.pacifier.net [64.255.237.177]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6931A1A3B for <jose@ietf.org>; Tue, 8 Dec 2015 10:08:56 -0800 (PST)
Received: from hebrews (c-24-21-96-37.hsd1.or.comcast.net [24.21.96.37]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp3.pacifier.net (Postfix) with ESMTPSA id 7935338F2A; Tue, 8 Dec 2015 10:08:55 -0800 (PST)
From: Jim Schaad <ietf@augustcellars.com>
To: 'Kathleen Moriarty' <kathleen.moriarty.ietf@gmail.com>, 'John Bradley' <ve7jtb@ve7jtb.com>
References: <20151204151726.F0B12180006@rfc-editor.org> <018b01d1316f$ea11c8e0$be355aa0$@augustcellars.com> <EC8849D9-1802-4406-8F30-E5DAD541593E@ve7jtb.com> <5912D7C1-CC80-48ED-8B87-60E1D88391B8@gmail.com>
In-Reply-To: <5912D7C1-CC80-48ED-8B87-60E1D88391B8@gmail.com>
Date: Tue, 08 Dec 2015 10:06:09 -0800
Message-ID: <029701d131e3$1e6b70f0$5b4252d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Content-Language: en-us
Thread-Index: AQHynYOcpZbQ5OFtnP/nXMJjZHRETAJv6HwJAXqLoR0DLNakPZ5F0NMQ
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/gpn18ay60LlUQXtp16y_vUrXOb8>
Cc: simon@bastli.ethz.ch, 'Karen Odonoghue' <odonoghue@isoc.org>, 'RFC Errata System' <rfc-editor@rfc-editor.org>, 'Michael Jones' <mbj@microsoft.com>, jose@ietf.org, 'Nat Sakimura' <n-sakimura@nri.co.jp>, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>
Subject: Re: [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: Tue, 08 Dec 2015 18:08:59 -0000
That works for me > -----Original Message----- > From: Kathleen Moriarty [mailto:kathleen.moriarty.ietf@gmail.com] > Sent: Tuesday, December 08, 2015 5:59 AM > To: John Bradley <ve7jtb@ve7jtb.com> > Cc: Jim Schaad <ietf@augustcellars.com>; RFC Errata System <rfc-editor@rfc- > editor.org>; Michael Jones <mbj@microsoft.com>; Nat Sakimura <n- > sakimura@nri.co.jp>; Stephen Farrell <stephen.farrell@cs.tcd.ie>; Karen > Odonoghue <odonoghue@isoc.org>; simon@bastli.ethz.ch; jose@ietf.org > Subject: Re: [Editorial Errata Reported] RFC7515 (4554) > > Thanks for your advice on this. > > How about I mark it as 'editorial' and hold for document update, then add a note > that says the normative section is correct and this is just an HTML markup from > txt issue? > > Thanks, > Kathleen > > Sent from my iPhone > > > On Dec 8, 2015, at 8:47 AM, John Bradley <ve7jtb@ve7jtb.com> wrote: > > > > I agree, Rfcmarkup strikes again:) > > > > The canonical version is txt and that is correct. > > > > The link is probably correct in the XML version. > > One day we will publish RFC from the XML and can get rid of these stupid > HTML markup from TXT issues. > > > > Worth keeping a note of if we do do an errata and can publish in XML. > > > > Until that time nothing to do for it. > > > > John B. > > > >> On Dec 8, 2015, at 1:21 AM, Jim Schaad <ietf@augustcellars.com> wrote: > >> > >> > >> My inclination is to say that this is not a valid Errata. The > >> complaint is really against the tools and not the document as the > >> complaint is dealing with the line, which is not part of the RFC, > >> rather than with either technical or editorial content of the document. > >> > >> I believe that the original text is sufficiently clear as to which > >> section is being referred to for a human. But it would not be clear > >> to a tool. The suggested change may or may not fix that for the tool > >> and a better approach is probably to start using the xml source for > >> the generation of the html page rather than to fix up the text version. > >> > >> Jim > >> > >> > >>> -----Original Message----- > >>> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] > >>> Sent: Friday, December 04, 2015 7:17 AM > >>> 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 > >>> Cc: simon@bastli.ethz.ch; jose@ietf.org; rfc-editor@rfc-editor.org > >>> Subject: [Editorial Errata Reported] RFC7515 (4554) > >>> > >>> 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