AICENT-002
RTTP
Tag under the Aicent Stack blog.
Four public questions we posed to the W3C AI Agent Protocol Community Group — preimage defense, address assurance, trust leases, granularity — and our…
The Model Context Protocol's 2026-07-28 revision removes protocol-level sessions, the initialize handshake and the Mcp-Session-Id header…
While the formal A2A Agent Registry spec remains unratified, five implementations ship with incompatible APIs, the official MCP Registry validates own…
SHA-256 outputs 32 bytes; we keep the first 16 as the address. The truncation is not a shortcut — it is a priced security decision. This piece lays th…
The address is a function of the authority string, so "two spellings of one address" is a correctness defect, not a style question. The mainstream URI…
We registered two schemes at IANA, yet the I-D is one merged document — why one document, not two? Because the addressing model exists only once, and…
The merged document's acknowledgements concede that the client-behaviour requirements are the part most likely to be misimplemented — so it uses three…
The merged document opens with an unusual confession — "This document is not an Internet Standard." An inevitable question follows: why self-demote to…
The September W3C report pushed the identity layer all the way to a reference implementation — yet in the report's own requirements list, the addressi…
The trust anchor of agent mutual-recognition can live in three places — a registry's server, a platform-hosted identity document, or a derived key…
The agent era forced authentication to reinvent itself — derivation instead of issuance, leases instead of permanence, one draft and two schemes.
Resonant Time Transfer Protocol, fixed in 2026 after four rival expansions. The name presses itself onto four words readers already know — RTP, HTTP…
Sixteen numbered pillars plus one unnumbered engine — and only two of them are walking the IANA and IETF path right now. This piece explains the lands…