Re: x402

On Sun, Aug 30, 2026 at 11:22 AM Willy Tarreau <w@1wt.eu> wrote:
>
> On Sun, Aug 30, 2026 at 09:56:00AM -0700, Tim Bray wrote:
> >  Welllll...
> >
> > RFC9110 says that 402 is "reserved for future use". The solution is
> > obvious, let's send the IETF enforcement squad after anyone who uses it
> > anyhow. Kidding, the squad should be reserved for people who put UTF-16
on
> > the wire.
> >
> > The Wikipedia entry
> > https://en.wikipedia.org/wiki/List_of_HTTP_status_codes offers
> > a few more enforcement-squad targets.
> >
> > I really am kidding, 402 feels like it ought to be useful and these
people
> > as exploring use cases, maybe consensus will emerge and we can write an
RFC.
> >
> > As for x402.org, let's see. Agents. Working around those inconvenient
> > Know-Your-Customer laws. Crypto. Definitely a bit of a smell. I wonder
if
> > Google and Shopify and AWS and are really in on this?
> >
> > I like Mnot's draft but I think it's probably not OK to avoid mentioning
> > that in every conceivable situation where payment is occurring, it
occurs
> > against a legal backdrop. Maybe something along the lines of an
assertion
> > that the use of 402 implies makes no legal claim cannot serve as a basis
> > for any legal claims for or against an entity issuing that status.
> >
> > I'd go so far as to say something  "implementers MUST take legal issue
> > surrounding payment activities into consideration".
>
> Another approach is to use 402 the next time a status code is going to
> be used. It will get its spec and its official semantics, clearing the
> legitimacy of all the rogue ones.

xkcd.com/927

If the multiple implementations/efforts (some of which have nothing
resembling a spec I can find) coexist nicely we might just want to throw up
some documentation of the coexistence.



>
> Willy
>


Astra mortemque praestare gradatim

Received on Sunday, 30 August 2026 20:16:34 UTC