- From: John McGraw <j.mcgraw@taskhawktech.com>
- Date: Tue, 28 Jul 2026 19:23:59 +0000
- To: Mark Nottingham <mnot@mnot.net>
- CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Hi Mark, Thank you for the guidance. That sequence makes sense, and I appreciate you taking the time to clarify it. I will follow up with the HTTPAPI chairs and Working Group regarding adoption and scope. If HTTPAPI adopts the work, I will bring the relevant HTTP semantics questions back to HTTPBIS for review. Best regards, John ________________________________________ From: Mark Nottingham <mnot@mnot.net> Sent: Tuesday, July 28, 2026 5:37 AM To: John McGraw <j.mcgraw@taskhawktech.com> Cc: ietf-http-wg@w3.org <ietf-http-wg@w3.org> Subject: Re: Delegated authority challenges: 401/403 + WWW-Authenticate vs dedicated 4xx [You don't often get email from mnot@mnot.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Hi John, I suspect folks are waiting to see if HTTPAPI adopts this draft; if so, it will be reviewed. Cheers, > On 16 Jun 2026, at 1:31 am, John McGraw <j.mcgraw@taskhawktech.com> wrote: > > Hi all, > > I would appreciate HTTP Working Group guidance on a status-code question arising from an individual HTTPAPI draft: > > https://datatracker.ietf.org/doc/draft-mcgraw-httpapi-agent-budget/ > > The current revision defines a Delegation HTTP authentication scheme for request-bound delegated authority. The general pattern is that a client presents signed, bounded authority from a principal before an origin server or gateway performs protected processing. Budget is the initial authority profile, but the HTTP mechanism is intended to be broader than payment or agent-specific deployments. > > Earlier revisions proposed a dedicated 427 Budget Required status code. In -02, that is no longer requested. The draft now uses existing HTTP semantics as the baseline: > > - 401 with WWW-Authenticate: Delegation when no acceptable Delegation credential is present, invalid, incomplete, or needs to be obtained. > - 403 when a Delegation credential is understood but insufficient under local policy. > - Problem Details for machine-readable authority requirements and public reason tokens. > > The dedicated status-code question is now left open as a possible 4NN Delegated Authority Required code, if the Working Group sees an interoperability reason for that path. > > The question I would value guidance on is: > > Is 401/403 + WWW-Authenticate: Delegation + Problem Details the appropriate interoperable baseline for this behavior, or is there a distinct HTTP semantics, intermediary, or API-gateway reason to consider a dedicated 4xx status code? > > Related feedback would also be useful on whether defining a new Delegation authentication scheme is the right shape, or whether this work should instead define fields and Problem Details members around existing authentication semantics. > > Best, > John > -- Mark Nottingham https://mnot.net/
Received on Tuesday, 28 July 2026 19:24:08 UTC