AI4ME
AI for personalised media
Wording
Agent discovery across organisations · one viewer, one forecast

How agents deliver personalised media

The big deal
BBC compute agents bbc.co.uk
BT network agents bt.com
Cloudflare CDN agents cloudflare.com
DNS resolver Cloudflare 1.1.1.1
Guided demo

Configure

Background information

Detail and DNS exchange

Point at

The viewer

Manchester
BSL
AD
Waiting for the pipeline to be placed…

Where the pieces are

Idle
BBCBTCloudflareDNStalkingchosenwithdrawn

Agent discovery, step by step

click a step for detail
DNS-AID discovery→Directory (illustrative)→Selection (live metrics)→Negotiation (A2A)
    What the orchestrator agent can prove afterwards
    • Nothing yet. Run discovery.
    Play the discovery
    Then change the world and watch it adapt
     
    Pick a device, then run discovery.
    Show the plumbing (what actually went over the wire)

    Resolver log (Cloudflare 1.1.1.1)

    ; nothing resolved yet

    The three zones (live)

    Jargon buster

    References (status as of 21 Oct 2026)

    • draft-mozleywilliams-dnsop-dnsaid-02 (27 May 2026): individual Internet-Draft, not yet adopted. Source of _index._agents, the primary-owner record model and the well-known / cap / cap-sha256 parameters used here.
    • IETF DAWN: proposed working group; charter in external review. Chairs Adrian Farrel and Wes Hardaker. Refresh before presenting.
    • RFC 9460 (SVCB), RFC 6698 / 7671 (DANE TLSA), RFC 4035 §4.3 (resolver trust and the AD bit), RFC 2308 (negative caching), RFC 8615 (well-known URIs): established mechanisms reused unchanged.
    • The Infoblox “Why the world needs DNS-AID” article is motivation only; its _catalog._agents example predates the draft's _index._agents. The draft is the reference where they differ.
    • Directory API, MVD/MDI fields, metrics, latency figures and migration outcomes are illustrative, from the AI4ME NIPA material, and are not specified by DNS-AID.