Summary

  • A 26 October individual Internet-Draft proposes that an AI-agent selector first establish what a requester may see and which targets satisfy hard requirements, then rank the survivors by semantic fit.
  • An unknown mandatory requirement produces unsupported_constraint; an unsupported preference can be set aside, but the decision must disclose it in ignored_preferences.

The most eloquent agent in the room may never make the shortlist. In “Semantic Routing for AI Agent Communication,” Yong Cui, Yihan Chao and Chenguang Du give the matchmaking desk a bouncer: check who is asking, what they are allowed to see, and which candidates meet the non-negotiable conditions. Only then does semantic similarity get a vote.

Their proposed Semantic Routing Function receives a task, execution context, required capabilities, constraints and preferences. It looks at locally visible target profiles and policy, and returns one target or an error. “Routing” here happens at the application layer. No IP packet changes course because this document says so.

The draft's decision sequence is unusually explicit. First comes requester security context and an authorized view of targets. The function validates the request, keeps active and policy-eligible candidates, enforces mandatory capabilities and constraints, then scores semantic fit and optional preferences. A brilliant semantic score cannot resurrect a candidate that failed a hard rule. If the selector cannot understand a required constraint, its proposed answer is unsupported_constraint, not a hopeful guess. If it ignores an optional preference, it records that fact.

There is a small trap in the input fields. A data_location or language value in context describes a task; it does not become a hard placement rule unless the requester also expresses it as a routing constraint. The draft's example of a confidential Chinese-language report and Chinese data residency is a worked example, not a reported incident. For a requester, the difference between “here is the context” and “you must stay here” is the whole contract.

The authors also give decisions an expiry. Fallback keeps the original hard constraints, and the receiving target or gateway checks current authorization again when invoked. Selection, in their design, does not reserve capacity or grant permission to run the task. A pretty match card is still just a match card.

The Datatracker record lists this as an individual draft submitted on 26 October, with no working-group adoption shown. The newly approved DAWN charter covers initial public agent discovery and leaves semantic matchmaking and ranking outside its first mandate. Discovery may supply names; this proposal asks who may choose among them.