1 / 4

Formats for long term signatures

Formats for long term signatures. Original documents RFC 3126 ETSI TS 101 733 European Electronic Signature Standardisation Initiative (EESSI) Why update TS101 733 updated by ETSI Based on review by EC evaluation of EESSI CMS updated RFC 3369 RFC 3852.

leane
Download Presentation

Formats for long term signatures

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. Formats for long term signatures Original documents RFC 3126 ETSI TS 101 733 European Electronic Signature Standardisation Initiative (EESSI) Why update TS101 733 updated by ETSI Based on review by EC evaluation of EESSI CMS updated RFC 3369 RFC 3852

  2. EU EESSI Review Comments • Allow implementers more flexibility to choose options which best fit market requirements • Separate the Signature Format from the signature policy • Simplify the document • Document structure and editorial changes

  3. Main Technical Changes • Signature policy attribute made optional for Basic Electronic Signature (BES) • BES = CMS + signing certificate attribute (i.e. hash+id of cert). • Backward compatibility with older versions (101 733 and RFC 3126) provided by Explicit Policy-based Electronic Signature (EPES) • EPES = BES+ signature-policy-identifier attribute • On generation conformance to either BES or EPES is required • Two new optional attributes for attribute cert refs • id-aa-ets-attrCertificateRefs • id-aa-ets-attrRefsRevocationRefs

  4. What next • Comments welcome on Internet draft ross@secstan.com • Proposal: • Replace RFC 3126 with new RFC XXX based on the Internet draft presented to this meeting.

More Related