1 / 9

LTAP status

Peter.sylvester@edelweb.fr. LTAP status. LTAP reminder. Very thin layer Usable for many use cases Record keeping long term archive. Services. Basic service (treated) Interaction between client and ONE server Few and simple operations Simple use/profile of protocol

baby
Download Presentation

LTAP status

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. Peter.sylvester@edelweb.fr LTAP status Peter Sylvester LTAP protocol presentation

  2. Peter Sylvester LTAP protocol presentation LTAP reminder Very thin layer Usable for many use cases Record keeping long term archive

  3. Peter Sylvester LTAP protocol presentation Services • Basic service (treated) • Interaction between client and ONE server • Few and simple operations • Simple use/profile of protocol • Example: One target, one message, etc • Extended service (not treated in this doc) • For front ends and brokers (Encryption, splitting, proxies, …) • Can use the same protocol or overload • May add operations • Example CompleteTRANSFER from one archive to another

  4. Peter Sylvester LTAP protocol presentation Transactions Transaction based (asynchronous operation) borrowed from ebXML Request Acknowledge (technical) Response (business) Support for services archive/status/verify/export/delete defined by service Underlying authorization and transport services SAML, SOAP, SSL, etc. Transaction model almost stable Artifacts are probably not necessary, identification via hash and long term URI seems sufficient. French National Archive has defined OAIS like operations and services that map down the LTAP (without saying so)

  5. Peter Sylvester LTAP protocol presentation Transactions Asynchronous by need Need to « wait » until evidence available Implemented using polling via status function Request, acknowledge, final result Some clients may only need 1 function + status Ex. Just archive

  6. Peter Sylvester LTAP protocol presentation Basic functions Archive – insert data in the archive Status – determine status of archived data Export – export archive data and evidence data Delete – delete archive data and evidence data Verify – demonstrate data integrity and authenticity Question: Can Verify mapped to something in WEBDAV?

  7. Peter Sylvester LTAP protocol presentation Status Document version 01 out, still incomplete, next version is already advanced. Small tool to allow automatic creation of asn1 and xsd modules was developped in the meantime. Data structures not yet fully included from existing implementation

  8. Peter Sylvester LTAP protocol presentation To be done • Result of Verify function? • Just a date? • An ERS? • How to add/handle metainformation? • Just « archive » them using existing long term reference.

  9. Peter Sylvester LTAP protocol presentation General Information Authors Aleksej Jerman Blazic, SETCCE Peter Sylvester, EDELWEB Carl Wallace, ORIONSEC

More Related