Expand description
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:
- The coordinator authenticated each of them directly via a bilateral handshake (the coordinator holds a peer-issued TCT for each participant).
- 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 verifier::verify_session_bundle;pub use verifier::BundleOutcome;pub use verifier::VerifySessionBundleContext;
Modules§
- builder
SessionTrustBundlebuilder (RFC-AITP-0010 §4).- error
- Session Trust Bundle errors (RFC-AITP-0010 §7 /
BUNDLE_*codes tracked inagentidentitytrustprotocol/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).
Constants§
- RFC_
AITP_ 0010_ BUNDLE_ URI - Manifest
extensionskey under which a coordinator advertises the concrete HTTPS URL of its session-bundle endpoint (RFC-AITP-0010 §4.3.1; registered in the spec’sregistries/extension-keys.md).