_index._agents, the primary-owner record model and the well-known / cap / cap-sha256 parameters used here.well-known SvcParamKey used in the agent records here. Values are well-known suffixes, never paths; the client appends /.well-known/ and the suffix to the service origin._catalog._agents example predates the draft's _index._agents. The draft is the reference where they differ.One viewer, three organisations, one agent registry. An illustrative, simulated scenario built on the DNS-AID proposal. Thanks for watching.
More on AI4ME: personalised media explainer video · project website
Next or Restart to start again · Back to go back a step · T for the optional failure branch
A viewer in Manchester wants tonight's forecast in Welsh with large captions. Their TV can't draw the 3D map. Watch the BBC's orchestrator agent find, verify and negotiate with agents at the BBC, BT and Cloudflare, using only the DNS, to put that picture on screen.
Agent discovery is a key industry requirement. Before agents from different organisations can work together they must be able to find each other, learn what each can do, and verify what they are told. This demo shows how the approach we are developing within IETF DAWN addresses that need.
31 short steps with narration. Each shows the DNS exchange in the draft's record format, a plain-English explanation and a jargon buster. About eight minutes.
New to AI4ME? Watch the personalised media explainer · AI4ME project site
Illustrative AI4ME scenario. The DNS answers, the metrics, the three organisations' agent endpoints and the migration outcomes are all simulated. Record formats follow draft-mozleywilliams-dnsop-dnsaid-02; signatures and digests are shortened.
Keys: → / Page Down next · ← / Page Up back · D show the DNS record · Esc close it · T optional failure branch