Crate aitp_session_bundle 

Session Trust Bundle (RFC-AITP-0010).

In a multi-agent session of N participants, requiring O(N²) bilateral Mutual Handshakes is unscalable. The Session Trust Bundle is a signed artifact a coordinator constructs from N coordinator↔participant Mutual Handshakes (each producing a peer-issued TCT) and distributes to all participants, so that every agent-to-agent pair within the session has a verifiable trust artifact without a full mesh of handshakes.

Trust model

A bundle provides coordinator-attested membership, not peer-to-peer identity binding. If A and B both appear in the same bundle, they know:

1. The coordinator authenticated each of them directly via a bilateral handshake (the coordinator holds a peer-issued TCT for each participant).
2. The coordinator signed both of those TCTs into the same bundle.

Pairs that need direct peer-to-peer identity binding (rather than coordinator-attested membership) MUST run a separate bilateral Mutual Handshake.

Re-exports

pub use builder::SessionBundleBuilder;

pub use builder::DEFAULT_BUNDLE_VERSION;

pub use error::SessionBundleError;

pub use types::ParticipantEntry;

pub use types::SessionBundleEnvelope;

pub use types::SessionTrustBundle;

pub use types::SESSION_BUNDLE_MEMBERS;

pub use verifier::verify_session_bundle;

pub use verifier::BundleOutcome;

pub use verifier::CoordinatorKeySource;

pub use verifier::VerifySessionBundleContext;

pub use wire::parse_session_bundle_envelope;

pub use wire::parse_session_bundle_wire;

Modules

builder

SessionTrustBundle builder (RFC-AITP-0010 §4).

error

Session Trust Bundle errors (RFC-AITP-0010 §7 / BUNDLE_* codes tracked in agentidentitytrustprotocol/plans/v0.2-conformance-followups.md).

types

Wire types for Session Trust Bundle (RFC-AITP-0010 §3).

verifier

Session Trust Bundle verification (RFC-AITP-0010 §5-§6).

wire

Wire-form parsing for the Session Trust Bundle transport envelope (RFC-AITP-0010 §3, §5).

Constants

RFC_AITP_0010_BUNDLE_URI

Manifest extensions key under which a coordinator advertises the concrete HTTPS URL of its session-bundle endpoint (RFC-AITP-0010 §4.3.1; registered in the spec’s registries/extension-keys.md).

Functions

advertise_bundle_uri

Advertise a coordinator’s session-bundle endpoint in the Manifest it is about to sign (RFC-AITP-0010 §4.3.1): sets extensions["rfc-aitp-0010.bundle_uri"] to bundle_uri, the concrete URL the coordinator exposes (e.g. https://coord.example/aitp/session/bundle). Because the key lives in the Manifest’s extensions, the Manifest signature covers it.

bundle_uri_from_manifest

Read the advertised session-bundle endpoint from a coordinator’s (verified) Manifest. None when the key is absent, not a string, not a URL, or neither HTTPS nor http://localhost / http://127.0.0.1.