1 / 12

The (revised) LTAP Protocol

The (revised) LTAP Protocol. LTA, LTAP and AO Aleksej Jerman Blazic. Preservation. Archiving is a process (!) May be successor of terminated process (e.g. workflow) or simply demonstrator of events (e.g. within a workflow) Has a starting point and termination point Perpetual maintenance

jacqui
Download Presentation

The (revised) LTAP Protocol

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. The (revised) LTAP Protocol LTA, LTAP and AO Aleksej Jerman Blazic 65th IETF Meeting, Dallas

  2. Preservation • Archiving is a process (!) • May be successor of terminated process (e.g. workflow) or simply demonstrator of events (e.g. within a workflow) • Has a starting point and termination point • Perpetual maintenance • Availability – access • Readability – interpretation • Authenticity – existence • Stability – integrity

  3. The global picture

  4. Archive Object

  5. Long term archive protocol • Technical vs. formal interaction • Levels – to be clarified • LTA – a general service • LTA – an ERS service • A position of LTA in data lifecycles • Redundancy and data moving – single repository with bindings • Workflow • Archive • Etc.

  6. The general picture • Asynchronous model • One request • Two category response • ACK/NACK • ACK/NACK + Process outcome • Use of lower transport layers including authentication/security means • Messages • Request information • Payload • Security assertions

  7. Asynchronous model

  8. Definitions • Clarification done • Structure of objects (still needs some work on groups) • Data • Metadata • Binding info. • Lifecycle of objects defined • Inside one transaction • As a result of export information

  9. Services and configuration • Principles of configurations and service parameters • client selects a service according a contract/archive policy • Service/archive policy • Global – general operation characteristics (e.g. redundancy, ERS type, etc.) • Specific – archive process characteristics (e.g. grouping, retention, etc.) • service has all necessary parameters • service management • out of scope or • some configuration options available

  10. Services and configuration • LTA service types • Archive • Status • Verify • Export/Modify - TBC • Delete • Issue • Configuration option – change process parameters, e.g. retention • Change parameters • Change archive policy

  11. To be done • Details of specifications in xml and asn1 • Integration with ERS??? • Lower layer bindings – when lower layer bindings are removed, the LTAP should work • Service configuration • Service types • Data group clarification (probably removal) • Splits processing (?) • Done at the requestor level, i.e. all preparations done before and a metadata object added to each portion. Portions are handled by a front end – somewhat comparable to an entity that encrypts the data before archiving them • Done by “splitting” device? • Splitting done instead time stamping? How does that affect the ERS? • Other?

  12. Questions P. Sylvester (peter.sylvester@edelweb.fr) C. Wallace (cwallace@orionsec.com) A. Jerman Blazic (aljosa@setcce.org)

More Related