Struct FreshnessPolicy 

pub struct FreshnessPolicy {
    pub skew: TimeDelta,
    pub max_age: Option<TimeDelta>,
    pub require_issued_at: bool,
}

How a consumer bounds a document in time before acting on it.

Every field is explicit; there is no “unset means whatever the library felt like” case. See the module documentation for the reasoning and for which constructor to reach for.

Fields

skew: TimeDelta

Tolerance applied when comparing the document’s timestamps against the consumer’s own clock, per the allowance in SPEC §4.2. Applied to the future-dating check and to max_age.

Not applied to expiresAt, which validate_basic evaluates against the raw now: that comparison is documented as taking an already-adjusted instant from the caller, and moving it here would change the meaning of every existing call site.

max_age: Option<TimeDelta>

The oldest issuedAt this consumer will accept, measured back from now. None means unbounded — the pre-existing behaviour, and the only setting under which a document carrying neither timestamp can be accepted.

require_issued_at: bool

Reject a document that carries no issuedAt at all, with malformedRequest.

A document with no issuedAt and no expiresAt cannot be placed in any window, which SPEC §7.2 forbids executing a consequential task on. Setting this makes that refusal happen at the framework layer with a code the producer can act on, rather than at the replay guard with one that says nothing about what to fix.

Implementations

impl FreshnessPolicy

pub fn consequential() -> FreshnessPolicy

The posture SPEC §7.2 (Bounding the record) describes for a consequential Trust Task: issuedAt REQUIRED and a bounded acceptance window (DEFAULT_MAX_AGE), so that every accepted document sits inside a window the ReplayGuard can retain a record for.

pub fn with_max_age(self, max_age: TimeDelta) -> FreshnessPolicy

Builder: set the acceptance window.

pub fn with_skew(self, skew: TimeDelta) -> FreshnessPolicy

Builder: set the clock-skew tolerance.

pub fn requiring_issued_at(self) -> FreshnessPolicy

Builder: require an in-band issuedAt.

pub fn record_expiry<P>( &self, doc: &TrustTask<P>, now: DateTime<Utc>, ) -> Option<DateTime<Utc>>

The instant at which a record for doc may be dropped — the end of this consumer’s willingness to execute it, which SPEC §7.2 makes the same instant as the end of the replay record’s required retention.

expiresAt fixes it where present. Otherwise it is issuedAt + max_age. None means this policy places no bound on the document, in which case a consumer MUST NOT execute a consequential task on it: it has no window in which to retain the record.

Trait Implementations

impl Clone for FreshnessPolicy

fn clone(&self) -> FreshnessPolicy

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for FreshnessPolicy

impl Debug for FreshnessPolicy

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Default for FreshnessPolicy

fn default() -> FreshnessPolicy

The minimum every consumer should apply: reject a future-dated document and reject one whose stated validity interval is empty. Both are producer bugs or forgeries — no conforming producer emits either — so enforcing them costs a correct deployment nothing.

It deliberately sets no max_age. An acceptance window is a deployment decision (it depends on how long the transport may hold a message), and a library that guessed one would start silently rejecting documents that had been arriving for years.

impl Eq for FreshnessPolicy

impl PartialEq for FreshnessPolicy

fn eq(&self, other: &FreshnessPolicy) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for FreshnessPolicy