Service requirements
RFC 4810 describes long-term archive requirements as an Informational document.
MOBILE-ID · TRUSTED LTANS
Standards & Interoperability
From archival requirements to evidence records, timestamping and PKI validation.
Three technical reference layers
Evidence structures
ERS and XMLERS have distinct syntax and processing rules.
Trust infrastructure
TSA, certificates, revocation data and verification context support the evidence history.
Choose a reference by task
RFC 4810 — LTANS Requirements
Map RFC 4810 to evidence structures, interfaces and matching test criteria.
Review record and scope →RFC 4998 — ASN.1 ERS
Map RFC 4998 to evidence structures, interfaces and matching test criteria.
Review record and scope →RFC 6283 — XMLERS
Map RFC 6283 to evidence structures, interfaces and matching test criteria.
Review record and scope →RFC 3161 / RFC 5816 — Timestamping
Map RFC 3161 to evidence structures, interfaces and matching test criteria.
Review record and scope →Full reference catalog and applicability
| RFC | Document | Category |
|---|---|---|
| 4810 | Long-Term Archive Service Requirements | INFORMATIONAL |
| 4998 | Evidence Record Syntax (ERS) | STANDARDS TRACK |
| 6283 | Extensible Markup Language Evidence Record Syntax (XMLERS) | STANDARDS TRACK |
| 3161 | Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) | STANDARDS TRACK |
| 5816 | ESSCertIDv2 Update for RFC 3161 | STANDARDS TRACK |
| 5280 | Internet X.509 Public Key Infrastructure Certificate and CRL Profile | STANDARDS TRACK |
| 6960 | X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP | STANDARDS TRACK |
| 5652 | Cryptographic Message Syntax (CMS) | STANDARDS TRACK |
| 5035 | Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility | STANDARDS TRACK |
| 5698 | Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC) | STANDARDS TRACK |
Capability mappings are reference designs, not backend interoperability results. RFC 9169 updates ERS ASN.1 modules; deployment must identify tooling revisions.
RFC 9169 ↗LTAP
draft-ietf-ltans-ltap-08 is an expired Internet-Draft. The adapter is a target design, not a certification or current standard claim.
LTAP CompatibilityRFC 9169 · ASN.1 module scope
RFC 9169 is Informational and supplies alternative ERS/SCVP ASN.1 modules. It does not change wire bits or certify product interoperability. Record module/decoder choices in the deployment profile.
RFC Editor · RFC 9169 ↗From requirement to acceptance case
| Reference | Capability / output | Test and status |
|---|---|---|
| RFC 4810 · service requirements | Scoped submission, management, retrieval, policy and evidence. | Design mapping; backend acceptance not verified. |
| RFC 4998 / RFC 6283 | ERS/XMLERS package, data binding, tokens and history. | Decode, altered bytes, wrong token and missing history; no accepted cryptographic package available. |
| RFC 3161 / RFC 5816 | TSA token, imprint, policy and certificate path. | Valid/invalid imprint and source cases; needs TSA environment. |
| RFC 5280 / RFC 6960 | Trust anchors, path and contextual status. | GOOD/REVOKED/UNKNOWN and policy-specific missing material; real PKI not tested. |
| RFC 9169 | Alternative ASN.1 modules and decoder version. | Record module/tool in profile; no automatic wire-format change. |
| LTAP draft-08 | Target adapter; expired Internet-Draft. | Agree version, mapping and interoperability cases; adapter not accepted. |
| REST 3.0.0-draft / event 2.0 | Product-specific contracts; contextual JSON/examples. | Schema/negative tests in QA; no replacement for ERS verification. |