MOBILE-ID · TRUSTED LTANS
Standards architecture
Connect evidence models to standards, validation material and deployment boundaries.
From standards to responsibility
| Layer | Basis | Boundary |
|---|---|---|
| Requirements | RFC 4810 | Informational, not a certification |
| Evidence | RFC 4998 / 6283 | Model-specific syntax and processing |
| Trust | RFC 3161 / 5280 / 6960 | Timestamping and certificate validation |
| LTAP | draft-ietf-ltans-ltap-08 | Expired Internet-Draft; adapter design |
| Product API | 3.0.0-draft | Mobile-ID design, not an IETF standard |
From reference mapping to acceptance evidence
| Scope | Required evidence | Package limit |
|---|---|---|
| RFC 4998 / 6283 | Valid encoded artifacts, decoder and syntax-specific validation. | Sample JSON does not establish ERS/XMLERS. |
| RFC 3161 / 5816 | Token, imprint, TSA certificate and negative cases. | No accepted TSA backend in the ZIP. |
| RFC 5280 / 6960 | Trust inputs, time-bound status material and distinct UNKNOWN outcomes. | HTTP success does not establish certificate status. |
| RFC 9169 | Record ASN.1 module/tool versions and check encoding. | Informational; unchanged wire bits, no product certification. |