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

John Bradley <ve7jtb@ve7jtb.com> Tue, 08 December 2015 13:47 UTC

Return-Path: <ve7jtb@ve7jtb.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 3A4851B2E0C for <jose@ietfa.amsl.com>; Tue, 8 Dec 2015 05:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] 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 d-mQNg1RXvWu for <jose@ietfa.amsl.com>; Tue, 8 Dec 2015 05:47:42 -0800 (PST)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 131FB1B2E08 for <jose@ietf.org>; Tue, 8 Dec 2015 05:47:42 -0800 (PST)
Received: by qgcc31 with SMTP id c31so15777641qgc.3 for <jose@ietf.org>; Tue, 08 Dec 2015 05:47:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=awPkAxReHwfIjaM+Gx+mhScDWonFhvLj7tfD5G+wOa0=; b=A87W2cYYv4um39YUb811FQfTrxvOEgkCAMF9hje2kNhoChKFWg/DJhA4eRxV2iI+y8 S4hSWjI1b45l48cK3eZ6ubaycX/YmwycDTCIezsd24+/iEM0JNvc+ythlZ3lsdd1Tst+ 2ubo9HuxGPGeq3p9umQioePBWoAoszqz0uXOOIRRAMk62UNLTLx0atwBOIb9hVLC+v2T BsuCTc4HaDBcDfUFMRt+hUZMynVRn2mCTZsdqnaciiuAb7G7bOIOc4LyWDORj+kOcrM6 7oK5UpfsjXn1EWN/ulfPRDjVE8SC81IUTyHvRsarhb96teV4zJEOtNi/iFIGewSahFp2 U1aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=awPkAxReHwfIjaM+Gx+mhScDWonFhvLj7tfD5G+wOa0=; b=G9TO0wDXbZaF27TmyAERBP9hqJbGHog9rNvSPZUFByp5mZ/ARJASCdZwdvJBIQdc/R gKIyU2XydCP5cZfL5b6Ta2GVr7g+WAlvVbOSyt0qdi3n4fDaDGGCmfFHM9C4uP2xbRnd NkkcTeFELZmoAnA3l0G2vSMc1uuA/ZT3pkoL45g3Ew8tmzZqTiDuHIQAYsIuYkvq6LwE cRVhA7Rja1aZlycmpoTPtTpjuwqCAYCU6v9J9iFV8cLHBQ9uTNXTq3ImnEDNKmSf2rJQ ahRbEIWuAW+UHrJSuwHPcmD68Uk7QcR0QCfk8rnEdMMNgXpDLZidxJX/hNkm4GwLQQn7 NDqA==
X-Gm-Message-State: ALoCoQlmohM6RA6Ozyh/6FNAdjk44siCi5XKZs1Qv75Yfl/0YaxW6Ch7UmSDSMJRHezzRTfodgK2zxy6L0yMWujatnxG5RvF5A==
X-Received: by 10.140.221.145 with SMTP id r139mr4865418qhb.94.1449582461114; Tue, 08 Dec 2015 05:47:41 -0800 (PST)
Received: from [192.168.1.216] ([191.115.1.95]) by smtp.gmail.com with ESMTPSA id h206sm1502672qhc.43.2015.12.08.05.47.33 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 08 Dec 2015 05:47:39 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <018b01d1316f$ea11c8e0$be355aa0$@augustcellars.com>
Date: Tue, 08 Dec 2015 10:47:25 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC8849D9-1802-4406-8F30-E5DAD541593E@ve7jtb.com>
References: <20151204151726.F0B12180006@rfc-editor.org> <018b01d1316f$ea11c8e0$be355aa0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/z2BgWUBuYr-px6zQRe-DPPQYemM>
Cc: simon@bastli.ethz.ch, Karen Odonoghue <odonoghue@isoc.org>, RFC Errata System <rfc-editor@rfc-editor.org>, Michael Jones <mbj@microsoft.com>, Kathleen.Moriarty.ietf@gmail.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 13:47:44 -0000

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
>