Mobile-ID · Long-term digital evidence preservation
Customers and partnersWorkflow demoContact
Trusted LTANS
Evaluate
MOBILE-ID · TRUSTED LTANS

LTAP Compatibility

Draft-08 adapter design: operation mapping, security, custody, errors and interoperability acceptance.

VI–EN terminology

Target adapter scope

LTAP draft-ietf-ltans-ltap-08 is an expired Internet-Draft. This adapter is a target design, not an accepted integration.
IETF Datatracker · draft-08 ↗

Command and query mapping

LTAPTarget REST interfaceContract
ARCHIVEPOST /v1/archivesArchive API
EXPORTPOST /v1/archives/{archiveId}/exportsExport / Transfer API
DELETEPOST /v1/archives/{archiveId}/dispositionsArchive API
VERIFYPOST /v1/archives/{archiveId}/verificationVerification API
STATUSGET /v1/archives/{archiveId}/statusArchive API
LISTIDSGET /v1/archivesArchive API

This maps business intent, not byte-for-byte request/response interchangeability. DELETE remains subject to retention, holds and approval.

Interoperability profile to agree

ElementHandling
Encoding and versionAgree wire structures, size limits and tests; this ZIP contains no operational LTAP wire schema.
Identity and authorizationMap clients to tenant, scopes and object rights; never trust a self-asserted tenant.
Asynchronous processingRetain LTAP transaction to archiveId/jobId mappings; reconcile original results after timeout.
ErrorsSeparate decoding, authorization, policy, byte, TSA and execution failures; HTTP status is not automatically an LTAP error code.
CustodyPreserve embedded/reference/hash-only semantics; never promise byte retrieval from digests alone.

Adapter PoC cases

Next steps

LTAP compatibility center
LTAP compatibility center · Target interface illustration.

Search LTANS documentation

Expanded illustration