AI URI Scheme – Internet-Draft (ietf.org)

I build coding agents for a living, and I'm struggling to map this onto the set of things I do at work.

In general, interoperability and user choice are really important for us to get right as the community of people building AI platforms...

Have others reading this document been able to map it onto their work?

As a specific example:

> ai://bank/service/payments?amount=10&currency=USD

I'm not sure what this is representing here. Is it a way to encode a clickable link to chat with `bank` about `service/payments` with a few additional args attached?

100 points to anyone who can explain this

There is a newer version here https://datatracker.ietf.org/doc/draft-sogomonian-aiip-archi...

I don't understand what problem this is trying to solve though.

Is this a new protocol for us to put our remote MCP and remote resources behind?

> enabling autonomous systems and robots to connect

I was not expecting such ambiguous and inaccurate wording from IETF. Why "ai" and not, how it was traditionally called on the web, "robots"?

And of course this does not make any sense since vast majority of HTTP traffic is already autonomous.

Impressive, not just a new URI scheme, but also a brand-new Internet protocol, all in one concise paper.

Does the IETF have a red fat button on their desks, like the one often seen on variety shows, to instantly disqualify low effort submissions? You can infer that the document (and the interaction between the culprit and the IETF) was half-assed with the help of AI: https://mailarchive.ietf.org/arch/msg/art/ss-g3OHTtwHwyBDl0c....

This doesn't look like it was written by a human

AGI?

This document defines a scheme for "AI-adressable" resources without much care about definition of "AI-addressesable" or even the properties of such resources, that require a dedicated protocol.

I get very strong "E = mc^2 + AI" vibes from it, just shoehorning the coveted letters everywhere