IETF Logo Mail Archive

Re: [pkix] [Editorial Errata Reported] RFC6844 (5091)

"Phillip" <philliph@comodo.com> Fri, 18 August 2017 16:27 UTC

Return-Path: <philliph@comodo.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4151329FE for <pkix@ietfa.amsl.com>; Fri, 18 Aug 2017 09:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level:
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_SPF_PERMERROR=0.01] 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 5xmrncKCZ7Ta for <pkix@ietfa.amsl.com>; Fri, 18 Aug 2017 09:27:31 -0700 (PDT)
Received: from mmextmx2.mcr.colo.comodoca.net (mmextmx2.mcr.colo.comodoca.net [IPv6:2a02:1788:402:c00::c0a8:9cd6]) (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 3F6001329F3 for <pkix@ietf.org>; Fri, 18 Aug 2017 09:27:31 -0700 (PDT)
Received: (qmail 7726 invoked by uid 1004); 18 Aug 2017 16:27:28 -0000
Received: from clofcgmail2.cl.office.comodo.net (HELO clofcgmail2.cl.office.comodo.net) (10.104.70.204) by mmextmx2.mcr.colo.comodoca.net (qpsmtpd/0.84) with ESMTP; Fri, 18 Aug 2017 17:27:28 +0100
Received: (qmail 13007 invoked by uid 1012); 18 Aug 2017 16:27:27 -0000
Received: from pool-100-0-244-109.bstnma.fios.verizon.net (HELO VooDoo) (100.0.244.109) (smtp-auth username philliph, mechanism login) by clofcgmail2.cl.office.comodo.net (qpsmtpd/0.84/v0.84-169-ga857589) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Fri, 18 Aug 2017 12:27:27 -0400
From: Phillip <philliph@comodo.com>
To: 'Russ Housley' <housley@vigilsec.com>, 'Kathleen Moriarty' <Kathleen.Moriarty.ietf@gmail.com>, 'Eric Rescorla' <ekr@rtfm.com>
Cc: 'Phillip Hallam-Baker' <phillip.hallam-baker@comodo.com>, 'Rob Stradling' <rob.stradling@comodo.com>, 'IETF PKIX' <pkix@ietf.org>
References: <20170818150630.12CE1B814E2@rfc-editor.org> <EB29FEE8-AA80-48C7-A935-76CA419C21CB@vigilsec.com>
In-Reply-To: <EB29FEE8-AA80-48C7-A935-76CA419C21CB@vigilsec.com>
Date: Fri, 18 Aug 2017 12:27:26 -0400
Message-ID: <00d301d3183e$e1d15df0$a57419d0$@comodo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQGSOx0SL7MfQHNqOUPxFmmjd3PbhQG6RoP1ov40gYA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/2bxFXHu8O4thYtc8zBO_Ck6-evQ>
Subject: Re: [pkix] [Editorial Errata Reported] RFC6844 (5091)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2017 16:27:35 -0000

Please reject, Errata 5065 already updates this section, we should avoid
errata of errata.

https://www.rfc-editor.org/errata_search.php?rfc=6844&rec_status=15&presenta
tion=records

The second space does not worry me nearly as much as the issues to do with
CNAME handling.


-----Original Message-----
From: Russ Housley [mailto:housley@vigilsec.com] 
Sent: Friday, August 18, 2017 11:15 AM
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>; Eric Rescorla
<ekr@rtfm.com>
Cc: Phillip Hallam-Baker <phillip.hallam-baker@comodo.com>; Rob Stradling
<rob.stradling@comodo.com>; IETF PKIX <pkix@ietf.org>
Subject: Re: [pkix] [Editorial Errata Reported] RFC6844 (5091)

I do not think the extra space will confuse any implementers.  Also, since
the LAMPS WG is considering a charter item to update this document, a
resolution of "held for future update" seems right to me.

Russ


> On Aug 18, 2017, at 11:06 AM, RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC6844, "DNS 
> Certification Authority Authorization (CAA) Resource Record".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5091
> 
> --------------------------------------
> Type: Editorial
> Reported by: Mak Kolybabi <mak@kolybabi.com>
> 
> Section: 4
> 
> Original Text
> -------------
>   o  If CAA(X) is not empty, R(X) = CAA (X), otherwise
> 
> Corrected Text
> --------------
>   o  If CAA(X) is not empty, R(X) = CAA(X), otherwise
> 
> Notes
> -----
> Remove unnecessary space after second CAA, making appearances of CAA(X)
consistent throughout the section.
> 
> 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.
> 
> --------------------------------------
> RFC6844 (draft-ietf-pkix-caa-15)
> --------------------------------------
> Title               : DNS Certification Authority Authorization (CAA)
Resource Record
> Publication Date    : January 2013
> Author(s)           : P. Hallam-Baker, R. Stradling
> Category            : PROPOSED STANDARD
> Source              : Public-Key Infrastructure (X.509)
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix

v2.23.0 | Report a Bug | By Email