1 / 5

ASN.1 Profile Revision: Authors' Opinion & Future Plans

Draft 02 with changes including DC attribute, ASN.1 fixes, and editorial issues. Collaboration with ETSI for certificate interoperability. Feedback and timeline discussed for future RFC submission.

masato
Télécharger la présentation

ASN.1 Profile Revision: Authors' Opinion & Future Plans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Son of RFC 3039Qualified Certificates Profile Stefan Santesson, Microsoft Tim Polk, NIST Magnus Nystrom, RSA

  2. Status • Authors opinion is that this document is done • Draft 02 recently posted • Added DC attribute in subject field • Fixed ASN.1 problems • Remaining Editorial Issues • ASN.1 1993 - “To be or not to be” • Some minor reference updates

  3. Comments on the list • Comments from Denis Pinkas • Document title should be changed and the term Qualified Certificates removed from the document • Key usage extension recommendations – Freeze this work until X.509 is done with its defect resolution. • A new RFC should not obsolete 3039 • Authors comments • No changes of titles and terms • Son of 3039 does not depend on X.509 key usage resolution – done issue • Son of 3039 must obsolete RFC 3039

  4. ETSI Collaboration • ETSI currently defines new certificate interoperability profile TS 102 280 • TS 102 280 process has generated feedback on son of RFC 3039 – posted on the list • Current time table depends on son of RFC 3039 being done and having an assigned RFC number before end of February

  5. Future path • WG last call after this meeting • Editorial fixes of ASN.1 handled after last call together with any last call issues

More Related