[Trans] draft-ietf-trans-rfc6962-bis

[Russ Housley <[e-mail]>]

Hi.

A long time ago, I wrote an open source pyasn1 module for RFC 6962.  I just looked at the bis document to see what would need to change.  It turns out there there is a fair amount.

I was wondering if you would be willing to as an ASN.1 module as an appendix.  Right now, an implementer needs to do a fair amount of work to find all of the OID values and some of them do not have names.  For example:

     -  "eContentType" MUST be the OID 1.3.101.78.

By having an ASN.1 module, this OID will be easily recognized as a content type, and the syntax of the type:

   IMPORTS

  TBSCertificate
  FROM PKIX1Explicit-2009 -- RFC 5912
      { iso(1) identified-organization(3) dod(6) internet(1)
        security(5) mechanisms(5) pkix(7) id-mod(0)
        id-mod-pkix1-explicit-02(51) }

   CONTENT-TYPE
   FROM CryptographicMessageSyntax-2010  -- RFC 6268
       { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
          pkcs-9(9) smime(16) modules(0) id-mod-cms-2009(58) } ;

  ct-precertificateContent CONTENT-TYPE ::=
     { TYPE TBSCertificate IDENTIFIED BY
       id-ct-precertificateContent }

  id-ct-precertificateContent OBJECT IDENTIFIER ::= { 1 3 101 78 }


There are parallel benefits for the extension definitions.

I am willing to review the module and ensure that it compiles properly.

Russ