Expand description
RFC3161 timestamp facts, independent of application timelines and trust.
Structs§
- Accuracy
- Accuracy components as read, with zero for an omitted component.
- Accuracy
Reading - Readable scalar fields and conformance faults, without token acceptance.
- Authority
Error - Execution refusal, never a negative TSA identity or usage answer.
- Authority
Facts - Independent usage/name facts; neither proves certificate trust or signature.
- Check
Context - Explicit caller selection/time facts; this does not select a trusted path.
- Checked
Timestamp - Common check facts including original ESS validation-set restrictions.
- Component
Reading - Original wire spelling and the common INTEGER decoder’s minimal suffix.
- Deviation
Error - The unrepresentable component remains present, with its original location.
- Evidence
- Independently retained cryptographic/time evidence, not a trust verdict. The caller must establish TSA path/status, enforce signed ESS restrictions and apply algorithm/policy permissions before granting product acceptance.
- Integer
Field - Original integer spelling and the common decoder’s minimal numeric view.
- Message
Imprint - Borrowed algorithm/hash fields and independently accounted diagnostics. Reading is independent of algorithm support, output width and token trust.
- Profile
Failure - Exact caller-owned cause and the source from which its coordinates came. The common core does not rewrite an opaque error or invent its location.
- Profile
Input - Original already decoded fields, scoped to one profile invocation. These are structural facts, not successful mathematics, authority or trust. Outer and carried sources can have different coordinate systems even when they share an execution account. Scans, copies and parameter queries must admit their work through the corresponding reader’s current execution.
- Request
- A syntactically conforming original
TimeStampReq. - Request
Field Error - A failure retains the operand whose original source locates the cause.
- Request
Fields - Optional requested-field facts; omitted request fields mean unchecked.
- Request
Window - Caller-supplied moving window for a uniquely outstanding complete imprint.
- Requested
- Original parsed request and its producing reader, not reconstructed tuples.
- Retained
Facts - A conforming token’s declared generation/imprint projection.
- Retained
Imprint - Independently retained written hash algorithm and logical digest bytes. Parameter absence stays distinct from a written NULL; no re-encoding or generic normalization substitutes for the selected provider’s semantics.
- Token
- Timestamp envelope; reading does not establish signature, trust or chronology.
- Token
Extension - One original extension, with logical OCTET STRING content still borrowed.
- Token
Extensions - Recovered first readings plus independently owned source-located faults. These are inspection facts, not extension recognition or token acceptance.
- Token
Info - Required timestamp facts and optional values, independently of acceptance. Original bytes are borrowed; diagnostics/catalogues own their accounted capacity.
- TsaReading
- Present TSA wrapper and its readable name, or explicitly unreadable contents. An unreadable present wrapper is distinct from an absent optional field.
Enums§
- Authority
Source - Source in whose original coordinates a refusal is located.
- Bound
Uncertainty - Why the timestamp facts cannot establish a temporal endpoint.
- Check
Error - Execution refusal, never a semantic partial success.
- Component
- The optional component selected by the RFC3161 Accuracy schema.
- Deviation
Reason - Why the original component cannot be represented by a nonnegative u64.
- Evidence
Copy Error - Independent-copy refusal retains the coordinate context of its cause.
- Hash
Algorithm Reading - A written identifier versus uniquely bounded malformed algorithm syntax.
- Imprint
Agreement - Imprint agreement alone does not establish token signature or authority trust.
- Imprint
Error - Failed execution stays distinct from semantic mismatch and unsupported input.
- Imprint
Operand - Identifies which original source supplied an operand or located failure.
- Info
Check Error - Scoped execution refusal retaining the actual source/operand and cause.
- Info
Error - Failure inside the explicitly identified carried-content source.
- Mapped
Check Error - A check in a logical CMS envelope retains its own source context separately
from the inner
TSTInfomap. CMS errors must not useTSTInfocoordinates. - Mapped
Profile Check Error - A profile check in a logical envelope retains both independent source maps.
- Profile
Check Error - Extended profile execution refusal. Existing public common error enums are unchanged, including their exhaustive matching surface.
- Profile
Source - The coordinate domain of a profile’s original refusal.
- Recognition
Error - Recognition cannot erase an execution refusal or an opaque callback cause.
- Request
Agreement - Complete imprint agreement, independently of other request checks.
- Request
Imprint Error - Request comparison failure retains source role and actual source span.
- Requested
Content Error - Combined execution preserves request versus covered-content failure classes.
- Signature
Error - Execution failures remain separate from arithmetic and conformance answers.
- Timeliness
- How the supplied facts establish, fail or leave freshness unresolved.
- Token
Signature - Arithmetic/content facts, without ESS, certificate trust or timestamp proof.
- TsaIdentity
- Optional TSA subject-name agreement, without a trust assertion.
- TsaUsage
- RFC3161 §2.3 requires exclusive critical timestamping EKU.
Functions§
- earliest
- Lower endpoint of the authority’s generation-time accuracy interval. This says nothing about when the imprinted document was signed.
- latest
- Upper endpoint, retaining subnanosecond rounding and supplied leap facts. This is a factual interval calculation, not signature or trust validation.
- timeliness
- Evaluates explicit time facts; it does not establish signature or trust.