Python API reference (unreleased)

IPv4 authorization scope (IANA AFI 1).

IPv6 authorization scope (IANA AFI 2).

Nonzero unsigned 32-bit customer ASN.

Nonempty unique provider ASNs; {0} alone means no authorized providers.

Explicit authorization scope; None asserts the same authorization for both families.

Nonzero ASN of the local receiving AS.

Nonzero ASN of the neighbor supplying the path.

Neighbor role as seen by the local receiving AS.

Reconstructed external AS path to evaluate.

Explicit receiving AS, neighbor and relationship context.

Optional caller correlation string preserved in the corresponding batch item.

Family to evaluate; None requires identical usable authorization views for both.

Customer ASN queried in the available ASPA view.

Whether an attestation exists; False is permitted only in a usable data view.

Effective provider ASN to immutable original supports; nonzero providers suppress AS0.

Evaluated family, or None for an explicitly verified identical view in both families.

Optional inclusive original support start, as an aware UTC datetime.

Optional exclusive original support end; loading may impose an earlier source deadline.

Optional producer label; it is not a configured source identity or trust decision.

Original customer-provider assertion, including its authorization scope.

Normal outcome of the fixed ASPA path algorithm.

Original reconstructed path supplied by the caller.

Receiving context used by the algorithm.

ASN sequence after the algorithm removes consecutive prepends.

Stable reasons supporting this outcome.

Fixed data version used for this result.

UTC time actually used for this path evaluation.

Online current-time or explicitly fixed offline evaluation.

Exact fixed ASPA verification specification identifier.

Optional bounded ramp and authorization explanation.

Evaluated family, or None for an explicitly verified common view.

The fixed ASPA algorithm accepts the path in the supplied context.

The fixed ASPA algorithm rejects the path in the supplied context.

Available data lacks the attestation needed for a conclusive path result.

Reconstructed external path segments, neighbor first and origin last.

The source or protocol explicitly does not supply this payload.

No complete successful update has supplied this payload yet.

A complete usable view contains effective records.

A complete usable view authoritatively contains no effective records.

Previously synchronized data can no longer supply a valid view.

Availability was explicitly revoked, for example by a fatal protocol error.

Zero-based position in the caller input sequence.

Caller correlation string, or None when absent or itself invalid.

Evaluated result, including normal invalid/unknown outcomes; None on execution error.

Safe per-item input or availability error; exactly one of result and error is present.

One fixed data version used for the entire batch.

Ordered per-input results or safe errors.

Whether every input was processed; this does not mean every route was valid.

Number of evaluated items, including normal invalid/unknown outcomes.

Number of per-item execution or input failures.

Conservative BMP assessment, distinct from a standard ASPA status.

Original reconstructed path supplied for analysis.

Known observation facts; missing facts are not silently inferred.

Names of facts absent or unsuitable for a conclusive assessment.

Standard ASPA results for the explicitly checked receiving scenarios.

Fixed data version used for the scenario analysis.

UTC time used for the analysis.

Online current-time or explicitly fixed offline evaluation.

Evaluated family, or None for an explicitly verified common view.

Every applicable checked scenario is invalid with sufficient observation context.

All checked scenarios are valid; this is not a standard ASPA valid result.

Missing context or inconclusive scenarios prevent a definite assessment.

Known pre_policy or post_policy observation stage; None means unknown.

Whether the host reconstructed the external path, including AS4 information.

Known neighbor_to_origin ordering; unknown or other values prevent certainty.

Local receiving ASN, if known from the observation context.

ASN of the supplying neighbor, if known.

Known neighbor role; None requests analysis across applicable scenarios.

Configuration owner identifier used in compare-and-swap checks.

Configuration owner lifetime; not necessarily the observing snapshot epoch.

Positive configuration sequence within this owner and epoch.

No connection attempt is currently running.

A connection attempt or handshake is in progress.

The transport is connected; payload readiness is a separate property.

Synchronization failed and may retry; old data keeps its original lifetime.

The source worker has stopped; this does not extend or revoke data lifetime.

Stable identifier for the parsing or completeness observation.

Human-readable observation text, not a stable matching interface.

Optional producer field path associated with the observation.

Online lifetime checks or fixed offline evaluation.

Aware offline reference time, normalized to UTC; must be None online.

Check the current online lifetime on every operation.

Evaluate at the explicit reference time, without claiming current validity.

The receiving AS sees the neighbor as its customer.

The receiving AS sees the neighbor as its peer.

The receiving AS sees the neighbor as its provider.

The neighbor is a route server; the fixed algorithm permits its ASN omission.

The neighbor is a route-server client as seen by the local route server.

Route network or strict CIDR text; evaluated and checked per batch item.

Claimed origin ASN, or None when no origin is available.

Optional caller correlation string preserved in the corresponding batch item.

Normal RFC 6811 validation outcome on available data.

Canonical route network that was evaluated.

Evaluated origin ASN, or None for a missing origin.

Stable reasons supporting this outcome.

Fixed data version used for this result.

UTC time actually used for the route evaluation.

Online current-time or explicitly fixed offline evaluation.

Optional bounded explanation; None when explanation was not requested.

At least one covering VRP authorizes both the origin ASN and prefix length.

VRPs cover the route, but none authorizes both origin and length.

The available VRP view contains no covering assertion.

Copied immutable JSON-compatible producer metadata; it is not verified trust evidence.

BGP segment category; validation keeps unsupported categories explicit.

Nonempty ordered tuple of unsigned nonzero ASNs as supplied by the host.

An ordered AS_SEQUENCE segment.

An unordered AS_SET segment, retained for explicit validation rejection.

A confederation sequence requiring external reconstruction.

A confederation set requiring external reconstruction.

Validated prefix and origin assertions used for ROV.

Customer-provider authorizations with explicit address-family scope.

Keys retained for RTR, export and persistence; no dedicated query API.

Configured source that supplies this original support.

Exclusive effective UTC end, bounded by original record and source deadlines.

Original producer or successful RTR update time, when known.

Optional original producer label, distinct from source_id.

Inclusive original support start, when supplied; None adds no lower bound.

Publisher identifier; generation values from different publishers are incomparable.

Publisher lifetime identifier, changed when an online publisher restarts.

Positive snapshot sequence within this store_id and epoch.

Configured source identifier, distinct from producer labels.

Nonsecret digest of endpoint, interpretation and trust identity used for restoration.

Source category, such as rtr or json; not the producer format.

Format of the last complete dataset; None before a successful commit.

Availability of each payload family, independent of transport connection.

Current transport or worker state; retrying data may remain usable.

Stable reason for the latest reported source state, when available.

UTC time of the last accepted complete synchronization, when known.

Exclusive source deadline; reconnects and restoration do not extend it.

Original dataset generation time, when supplied or established by RTR EOD.

Negotiated RTR version of the complete dataset, or None for other inputs.

RTR cache session identifier, when a complete session is available.

RTR serial of the complete dataset; interpreted only within its session.

Most recent safe error information, when available.

Both AFI capabilities; explicit values determine aggregate ASPA availability.

One deduplicated effective prefix assertion.

All currently effective original supports for this assertion.

Optional inclusive original support start, as an aware UTC datetime.

Optional exclusive original support end; loading may impose an earlier source deadline.

Optional producer label; it is not a configured source identity or trust decision.

Original prefix assertion carried by this independently timed support.

Whether a new configuration and snapshot were atomically committed.

Configuration owner revision that defines this view.

Snapshot committed with this configuration; readiness and persistence may follow later.

Sorted identifiers newly present in the configuration.

Sorted identifiers removed from the configuration.

Sorted retained identifiers whose source identity or injected binding was replaced.

Publisher identifier for this event stream.

Event-stream lifetime; restarting a publisher invalidates older cursors.

Positive sequence within this publisher and epoch, including status-only events.

UTC time at which immutable metric values were sampled.

Publisher or explicit collector identifier for these process-local metrics.

Metric lifetime; counters do not continue across publisher restarts.

Cumulative integer event counts using fixed metric names and bounded labels.

Sampled resource and state quantities; units depend on the documented metric name.

Durations in seconds; each metric defines cumulative or latest-attempt semantics.

Position of this transition in the bounded publisher event stream.

Snapshot immediately before this transition or coalesced interval.

Snapshot published by this transition or at the coalesced interval end.

Configuration revision attached to before_id.

Configuration revision attached to after_id.

Stable publication cause, such as synchronized or configuration_changed.

VRP values affected by payload or support changes, subject to event limits.

ASPA customer ASNs affected by authorization or support changes.

Changed source metadata keyed by source ID; None denotes removal.

Conservative route scope: every route contained by these prefixes may need revalidation.

Conservative ASPA customer scope requiring path revalidation.

Payload families affected, including when a bounded detailed diff is unavailable.

Whether consumers must revalidate all relevant routes for affected_kinds.

Whether this event spans multiple actual commits; no intermediate IDs are invented.

Position of this observation in the publisher event stream.

Data snapshot current when this status observation was emitted.

Changed source connection or diagnostic state; may be empty for persistence events.

Last acknowledged durable snapshot identity, or None before any successful commit.

Configuration revision in the last acknowledged durable snapshot.

Current safe persistence failure, if any; valid memory state remains independent.

UTC time at which this report was sampled.

Resource lifecycle state; closing persists until all managed work has exited.

Fixed snapshot publication identity associated with this value.

Configuration owner revision that defines this view.

Observed payload availability; online queries still perform their own lifetime checks.

Exclusive next-recomputation boundary per payload, not an extension of source lifetime.

Selected trust group per payload; aggregate ASPA is None if family groups differ.

Current safe source observations, including changes after the last snapshot commit.

Limits currently committed by the owning client.

Exact fixed protocol and validation specification identifiers.

Whether the owning client satisfies its configured required payloads.

Observed availability independently for IPv4 and IPv6.

Exclusive next-recomputation boundary for each ASPA family, or None if unavailable.

Selected trust group per ASPA family, or None when no group is usable.

Last acknowledged durable snapshot identity, or None before any successful commit.

Configuration revision in the last acknowledged durable snapshot.

Disk snapshot used during restoration, or None if no complete state was recovered.

Current safe persistence failure, if any; valid memory state remains independent.

Whether a configuration candidate is being prepared; it may not yet be committed.

Removed or replaced source IDs whose owned cleanup has not finished.

Whether cleanup exceeded its reporting threshold while work remains managed.

Seconds elapsed in the currently observed cleanup.

Bounded descriptions of owned resources still awaiting cleanup.

Fixed publisher identity and generation; holding this object does not preserve lifetime.

Configuration owner revision that defines this view.

UTC publication time, separate from original generation and support deadlines.

Online or explicitly fixed offline evaluation context.

Source metadata captured atomically with this snapshot; later status changes are separate.

Selected trust group per payload; aggregate ASPA is None if family groups differ.

Payload availability in this fixed view; empty and unavailable remain distinct.

Exclusive next-recomputation boundary per payload, not an extension of source lifetime.

Independent availability for IPv4 and IPv6 authorization scopes.

Exclusive next-recomputation boundary for each ASPA family, or None if unavailable.

Selected trust group per ASPA family, or None when no group is usable.

Original publisher snapshot identity retained by an observer or import, when available.

Exact fixed protocol and validation specification identifiers.

Applied policy identity; none explicitly denotes no local policy in this release.

Payload category compared using the original source records.

Payloads asserted only by the left source, retaining original support intervals.

Payloads asserted only by the right source, retaining original support intervals.

Shared payloads retaining both sources supports, including differing deadlines.

Fixed snapshot whose original source states were compared.

Left source identity, capability and time metadata.

Right source identity, capability and time metadata.

Complete bounded differences keyed by payload kind; no silent truncation.

Original common or one-sided payload; ASPA uses one customer-provider edge with AFI.

Original bounded supports from the left source; empty when present only on the right.

Original bounded supports from the right source; empty when present only on the left.

Default stable error category used unless the constructor supplies an explicit code.

Stable error code.

Source affected by the operation, if known.

Whether retrying may succeed.

Minimum retry delay in seconds, if known.

Immutable safe fields explaining the failure.

Default stable error category used unless the constructor supplies an explicit code.

Stable error code.

Source affected by the operation, if known.

Whether retrying may succeed.

Minimum retry delay in seconds, if known.

Immutable safe fields explaining the failure.

Default stable error category used unless the constructor supplies an explicit code.

Stable error code.

Source affected by the operation, if known.

Whether retrying may succeed.

Minimum retry delay in seconds, if known.

Immutable safe fields explaining the failure.

Default stable error category used unless the constructor supplies an explicit code.