pub struct Request<'a> { /* private fields */ }Expand description
A syntactically conforming original TimeStampReq.
Algorithm support/width, extension recognition, replay history and trust are separate decisions. Unlike token inspection, request syntax faults are refused, not silently repaired or passed to the selected provider.
Implementations§
Source§impl<'a> Request<'a>
impl<'a> Request<'a>
Sourcepub fn read(parent: &Reader<'a>, element: &Element<'a>) -> Result<Self>
pub fn read(parent: &Reader<'a>, element: &Element<'a>) -> Result<Self>
Reads the original SEQUENCE with inherited depth/current execution. BER is allowed by the producing reader; the caller selects encoding. RFC3161 §2.4.1 defines version 1 and the ordered optional fields. https://www.rfc-editor.org/rfc/rfc3161.html#section-2.4.1
Sourcepub fn imprint(&self) -> &MessageImprint<'a>
pub fn imprint(&self) -> &MessageImprint<'a>
Full original requested imprint, including original parameter provenance.
Sourcepub fn nonce(&self) -> Option<Integer<'a>>
pub fn nonce(&self) -> Option<Integer<'a>>
Original minimal INTEGER view; no nonce bytes are fabricated.
Sourcepub fn extensions(&self) -> Option<&Extensions<'a>>
pub fn extensions(&self) -> Option<&Extensions<'a>>
All request extensions require server recognition, not only critical ones.
Sourcepub fn same_session(&self, parent: &Reader<'_>) -> bool
pub fn same_session(&self, parent: &Reader<'_>) -> bool
Original session identity, independent of shared account identity.
Source§impl<'a> Request<'a>
impl<'a> Request<'a>
Sourcepub fn unrecognized_extensions<E>(
&self,
parent: &Reader<'_>,
recognizes: impl FnMut(&Extension<'a>, &Execution<'_>) -> Result<bool, E>,
) -> Result<OwnedVec<Oid<'a>>, RecognitionError<E>>
pub fn unrecognized_extensions<E>( &self, parent: &Reader<'_>, recognizes: impl FnMut(&Extension<'a>, &Execution<'_>) -> Result<bool, E>, ) -> Result<OwnedVec<Oid<'a>>, RecognitionError<E>>
Reports every requested extension the supplied handler does not recognize.
RFC3161 §2.4.1 requires server recognition regardless of criticality. This is not a certificate-understands or token-critical-only query. The common fallible catalogue iterator admits each metadata access; the handler must independently admit its data-dependent decoding work. No empty/partial successful list is returned after processing or handler refusal. Recognition itself does not grant policy/algorithm permission. https://www.rfc-editor.org/rfc/rfc3161#section-2.4.1