130 likes | 146 Views
Understand LTAP protocol layering, interaction, transactions, and basic functions. Learn about archive objects, managing interactions, and service management for efficient archive operations. Get insights on infrastructure, user interactions, and data integrity.
E N D
LTAP presentation Peter Sylvester EdelWeb Peter.sylvester@edelweb.fr Peter Sylvester LTAP protocol presentation
LTAP layering We don’t handle everything! Peter Sylvester LTAP protocol presentation
Control User/Client Interaction Interaction Supporting infrastructure User/Client Archive service User/Client Interaction Interaction Notary service Supporting infrastructure Services Overview Peter Sylvester LTAP protocol presentation
Infrastructures • Basic infrastructure of trusted archive service • Interaction protocol • Archive objects • Data • Metadata • Digital signatures • Conservation attributes • Archive meta data • Complementary data • Evidence data • Supporting infrastructure of trusted archive service • Communication network • Security mechanisms • Time stamping • Data storage or document management system Peter Sylvester LTAP protocol presentation
Interactions • Message based technical and formal interpretation of archive services • Transaction based (asynchronous operation) • 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. 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 • Client in only need 1 function + status Peter Sylvester LTAP protocol presentation
Basic functions • Archive – insert data in the archive • Status – determine status of archived data • Transfer – export archive data and evidence data • Delete – delete archive data and evidence data • Verify – demonstrate data integrity and authenticity Peter Sylvester LTAP protocol presentation
LTAP service • Most importing: archiving • not an ebXML registry • Access, transfer are rare operations • At least during lifetime of objects, then transfer to historical archives • Client do not need to implement all functions Peter Sylvester LTAP protocol presentation
Management • Changes done via « transfer » • E.g. Changing of archive periods • Policies and configurations by reference • Minimization of parameters • Parameters to be configured a priori • Metadata from other layers • Entity identifiers and scope metadata, e.g. jurisdiction • Out of scope ‘front ends’ e.g. notarization • specialized front ends for authentication Peter Sylvester LTAP protocol presentation
Archive objects • Archive data • Raw data • Metadata • Security attributes (digital signatures) • Conservation attributes • Archive meta data • Complementary data • Evidence data Peter Sylvester LTAP protocol presentation
Archive data Peter Sylvester LTAP protocol presentation
Status • Document version 00 out • Metadata not completely clear • Collections/groups to be done • Adjusted with ERS • Some concerns about physical deletion • Data structures not yet fully defined Peter Sylvester LTAP protocol presentation
General Information • Authors • Aleksej Jerman Blazic, SETCCE • Peter Sylvester, EDELWEB • Carl Wallace, ORIONSEC Peter Sylvester LTAP protocol presentation