Re: [Technical Errata Reported] RFC5913 (5890)

This is an error in the text and not in the ASN.1 module, if it was in the
module I would agree.

-----Original Message-----
From: Benjamin Kaduk <[email protected]> 
Sent: Saturday, November 2, 2019 7:05 PM
To: Jim Schaad <[email protected]>
Cc: 'RFC Errata System' <[email protected]>; [email protected];
[email protected]; [email protected]; [email protected]; [email protected];
[email protected]
Subject: Re: [pkix] [Technical Errata Reported] RFC5913 (5890)

I've kept the "Technical" for similar ones in the past.
The ASN.1 is part of the protocol being specified, and if the ASN.1 as
written cannot be used, that feels like a technical flaw in the
specification.

-Ben

On Fri, Nov 01, 2019 at 02:43:34PM -0700, Jim Schaad wrote:
> Reasonable but editorial.
> 
> -----Original Message-----
> From: pkix <[email protected]> On Behalf Of RFC Errata System
> Sent: Thursday, October 31, 2019 4:12 PM
> To: [email protected]; [email protected]; [email protected]; 
> [email protected]; [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> 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 <[email protected]>
> 
> 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/pkix
> 

_______________________________________________
pkix mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pkix