1 / 18

OpenEvidence and ESS

OpenEvidence and ESS. Peter Sylvester, EdelWeb IETF - N° 57, Wien 2003-07-15 S/MIME working group. OpenEvidence project. EU IST 5th framework Accompanying measures special action open source duration april 2002 - Jan 2004. OpenEvidence Partners. EdelWeb - Groupe ON-X - France

abrun
Download Presentation

OpenEvidence and ESS

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. OpenEvidence and ESS Peter Sylvester, EdelWeb IETF - N° 57, Wien 2003-07-15 S/MIME working group

  2. OpenEvidence project • EU IST 5th framework • Accompanying measures • special action open source • duration april 2002 - Jan 2004

  3. OpenEvidence Partners • EdelWeb - Groupe ON-X - France • techno provider and coordination • Cybernetica - Estonia • techno provider • C & A - Italy • techno provider • EADS Telecom • user and testbed

  4. OpenEvidence Context • Emerging legal environments for • Recognition of electronic signatures • Long-term validity of electronic documents • Model : Third parties services for evidence creation and validation • Techniques • Time stamping, notarization, archiving, signature validation, • Problems • Proprietary solutions, competition, secret agendas, .. • Thus, slow standardization (many years) • Even: competing technologies

  5. State of the art • We can produce open source and have tools for it • We have identified workable solutions • There are technologies for our purposes • We can base on existing work

  6. OpenEvidence Techno • Complementary technologies • RFC 3029, RFC 3161 • Hash Linking Schemes for timestamping • Tests in application contexts • Demonstration time stamping • archive service

  7. More secure email • More tracability for users • receipts (among two consenting partners) • signed (protection against others) • For service provider and organisations • track mail transactions • keep mail archives for critical applications

  8. C & A Italian Law - example • Due to the Italian old law (D.P.R. 513/1997 , D.P.R. 445/2000 ) and the latest e-government law (“Allegato 3 for e-gov”) the transmission of a document via normal mail is equivalent to an electronic transmission if a signed return receipt will be created during delivery. • “Allegato 3” also specifies the technical requirements for the Italian Public Administration registry and mail interoperability mandatory after January 1st 2004. • All the Public Administration will be connected in a LAN called R.U.P.A. (Rete Unitaria della Pubblica Amministrazione) with an internal PKI and an LDAP directory containing the list of the servers mail addresses and their certificates. •  need to use Timestamps, certificate validation and a secure long term archiving system (OpenEvidence).

  9. Public Administration Public Administration C & A Actual situation Mail Server Mail Server

  10. Mail Server Mail Server XML XML Public Administration Public Administration Registry Registry C & A New situation

  11. ESS signed receipts • Three events • message creation • receipt creation • receipt « consumption »

  12. ESS message creation • Create timestamp/archive DVC (3029) • recipients as « dataLocators » • creates initial trace event • included as signed attribute • fair treatment to user • needed by recipient ’s service • request signed receipt

  13. Receipt creation • DVC validation (vsd service) • creates second trace event • produces validation DVC • create signed receipt • include DVC as signed attribute • send back to origin

  14. Receipt consumption • Validation of second DVC • creates third trace event • User and service have all DVCs • Service • consolidates DVCs • creates statistics, etc.

  15. Initial receipt • Time stamp • minimal • archive request • responds to many requirements • all outgoing mail need to be tracable • some procedure require it

  16. Critique • Separation of transport and transaction certification, example: • certified mail by postal services • did not succeed in the past • Internet email is « the » transport • postal service are « trusted » providers for attestations • No new technology

  17. Implementation Issues • What toolkits ? • Not many for ESS • ESS specification • obsolete ASN.1 • compilers difficult to use

  18. Questions • Answers: https://www.openevidence.org

More Related