Re: [pkix] [Technical Errata Reported] RFC5913 (5890)

Benjamin Kaduk <kaduk@mit.edu> Tue, 05 November 2019 18:54 UTC

Return-Path: <kaduk@mit.edu>
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 3649A120985 for <pkix@ietfa.amsl.com>; Tue, 5 Nov 2019 10:54:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 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, URIBL_BLOCKED=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 5i4w_3cCvhjW for <pkix@ietfa.amsl.com>; Tue, 5 Nov 2019 10:54:45 -0800 (PST)
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 CFEB212094A for <pkix@ietf.org>; Tue, 5 Nov 2019 10:54:44 -0800 (PST)
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 xA5IsbkN026508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 5 Nov 2019 13:54:40 -0500
Date: Tue, 5 Nov 2019 10:54:37 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Sean Turner <sean@sn3rd.com>
Cc: Santosh Chokhani <santosh.chokhani@gmail.com>, Roman Danyliw <rdd@cert.org>, pkix@ietf.org
Message-ID: <20191105185437.GF61969@kduck.mit.edu>
References: <20191031231219.933BFF406D7@rfc-editor.org> <020601d590ab$928d5180$b7a7f480$@gmail.com> <7FE54201-5DA3-4A01-AA64-913AA3C7F7DB@sn3rd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7FE54201-5DA3-4A01-AA64-913AA3C7F7DB@sn3rd.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/BBrXzIPaRS8y5WGKfDLy2fAqVkg>
Subject: Re: [pkix] [Technical Errata Reported] RFC5913 (5890)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 05 Nov 2019 18:54:51 -0000

Thanks for checking; I went with Editorial/Verified since I found Jim's
argument compelling (but we can ask the RFC Editor to change it if we feel
otherwise).

-Ben

On Tue, Nov 05, 2019 at 01:37:34PM -0500, Sean Turner wrote:
> +1
> 
> > On Nov 1, 2019, at 07:57, Santosh Chokhani <santosh.chokhani@gmail.com> wrote:
> > 
> > I as coauthor of the document is ok with the change.
> > 
> > -----Original Message-----
> > From: pkix [mailto:pkix-bounces@ietf.org] On Behalf Of RFC Errata System
> > Sent: Thursday, October 31, 2019 7:12 PM
> > To: turners@ieca.com; SChokhani@cygnacom.com; rdd@cert.org; kaduk@mit.edu;
> > kent@bbn.com; stefan@aaa-sec.com
> > Cc: pkix@ietf.org; rfc-editor@rfc-editor.org
> > Subject: [pkix] [Technical Errata Reported] RFC5913 (5890)
> > 
> > The following errata report has been submitted for RFC5913, "Clearance
> > Attribute and Authority Clearance Constraints Certificate Extension".
> > 
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid5890
> > 
> > --------------------------------------
> > Type: Technical
> > Reported by: Russ Housley <housley@vigilsec.com>
> > 
> > Section: Section 3
> > 
> > Original Text
> > -------------
> >     id-pe-authorityClearanceConstraints OBJECT IDENTIFIER ::= {
> >       iso(1) identified-organization(3) dod(6) internet(1) security(5)
> >       mechanisms(5) pkix(7) pe(1) 21 }
> > 
> > Corrected Text
> > --------------
> >   id-pe-clearanceConstraints OBJECT IDENTIFIER ::=
> >     { iso(1) identified-organization(3) dod(6) internet(1) security(5)
> >       mechanisms(5) pkix(7) pe(1) 21 }
> > 
> > Notes
> > -----
> > Section 3 and Appendix A use different names for the object identifier.
> > They should match.  I propose changing Section 3 to match Appendix A.
> > 
> > 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. 
> > 
> > --------------------------------------
> > RFC5913 (draft-ietf-pkix-authorityclearanceconstraints-03)
> > --------------------------------------
> > Title               : Clearance Attribute and Authority Clearance
> > Constraints Certificate Extension
> > Publication Date    : June 2010
> > Author(s)           : S. Turner, S. Chokhani
> > 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
> > 
> > _______________________________________________
> > pkix mailing list
> > pkix@ietf.org
> > https://www.ietf.org/mailman/listinfo/pkix
>