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

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
> 