IETF 63 LTANS, Paris. Peter Sylvester. LTAP protoco

1
LTAP presentation

• Peter Sylvester
• EdelWeb
• Peter.sylvester_at_edelweb.fr

2
LTAP layering

• We dont handle everything!

3
Services Overview
4
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

5
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.

6
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

7
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

8
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

9
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

10
Archive objects

• Archive data
• Raw data
• Metadata
• Security attributes (digital signatures)
• Conservation attributes
• Archive meta data
• Complementary data
• Evidence data

11
Archive data
12
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

13
General Information

• Authors
• Aleksej Jerman Blazic, SETCCE
• Peter Sylvester, EDELWEB
• Carl Wallace, ORIONSEC