Skip to content
IAM Insights

Explainers · Glossary

Structured Field Values for HTTP

RFC 9651 · RFC9651 · Structured Fields · HTTP-SF

RFC 9651: a typed grammar for HTTP header values (lists, dictionaries, strings, tokens) so new headers can be parsed without a bespoke format each time.

reference →

In our briefings

What our briefings say about Structured Field Values for HTTP itself, with the most direct claims first.

  1. The serialization algorithms in RFC 9651 define the recommended output behavior, and implementations MAY vary if the parsing algorithm still handles their output correctly. The RFC therefore allows more output flexibility than it allows in parser behavior. Its ABNF appendix is non-normative: when that grammar and the parsing algorithms disagree, the algorithms take precedence.

    RFC 9651 keeps the last duplicate dictionary or parameter valueBI-FIND-2024-0066

›Cited in 17 briefings

Every briefing that discusses this term, newest first.

  1. A disabled agent's old tokens still pass every check; a DNS draft now asks receivers to time how long

    Draft · · IETF Datatracker · Sriram Shankarlingam, HexaEight · Oct 20, 2026

  2. The OAuth working group split over a token-binding draft that never says what DPoP lacks

    Draft · · IETF Datatracker · Justin Richer et al. · Jul 28, 2026

  3. Hassan's agent delegation draft now classes granting access as execute, not write

    Draft · · IETF Datatracker · Amr Hassan · Oct 22, 2026

  4. An agent-evidence draft no longer checks every actor in a delegation chain before a service admits a call

    Draft · · IETF Datatracker · Shameer Thaha et al. · Oct 19, 2026

  5. An OAuth draft lets the API, not the agent, describe the approval, and now name the key the token is bound to

    Draft · · IETF Datatracker · Yaroslav Rosomakho et al. · Jun 25, 2026

  6. An attested OAuth client is one somebody vouched for; revision 12 says to trust its claims only as far as the voucher

    Draft · · IETF Datatracker · Tobias Looker et al. · Oct 13, 2026

  7. World's maker proposes a site-scoped handle for each verified human, and bars using it alone to log anyone in

    Draft · · IETF Datatracker · Aurélien Brézun, Tools for Humanity · Aug 6, 2026

  8. The signing-key draft under AAuth offers eight ways to trust a key, and only one says who the agent works for

    Draft · · IETF Datatracker · Dick Hardt et al. · Sep 13, 2026

  9. Folding every hop's signature into one would stop anyone stripping a signed hop out of an agent's request

    Draft · · IETF Datatracker · Tirumaleswar Reddy.K et al. · Sep 28, 2026

  10. Hardt's AAuth Budgets caps what an agent may spend at each resource, and hides the person's real limit from it

    Draft · · IETF Datatracker · Dick Hardt · Sep 28, 2026

  11. A draft token hides some claims, works with old servers unchanged, and leaves agent delegation claims visible

    Draft · · IETF Datatracker · Su-hyeon Forten Lee · Oct 3, 2026

  12. Protocol 427 offers agents a reusable spending allowance, then ties each signed proof to one request

    Draft · · IETF Datatracker · John Paul McGraw et al. · May 6, 2026

  13. IETF draft -02 gives each kind of AI use a yes or no; the draft makes honoring it optional, but local law may not

    Draft · · IETF Datatracker · Paul Keller et al. · Jul 21, 2025

  14. RFC 9651 keeps the last duplicate dictionary or parameter value

    Article · · IETF / RFC Editor · Mark Nottingham et al. · Sep 1, 2024

  15. A Content-Digest header can show a body arrived intact, not who sent it; RFC 9530 points to TLS or a signature for that

    Article · · RFC Editor · Roberto Polli et al. · Feb 1, 2024

  16. A valid RFC 9421 signature does not prove who signed; key and algorithm checks are left to each profile

    Article · · RFC Editor · Annabelle Backman et al. · Feb 1, 2024

  17. Richer's 2023 draft let each service in a call chain add a hash-linked token, but left serialization unfinished

    Draft · · IETF (individual Internet-Draft) · Justin Richer · Sep 15, 2023

Related terms

What appears alongside Structured Field Values for HTTP in the same briefings.

HTTP Message SignaturesProblem Details for HTTP APIsDigest Fields (RFC 9530)Agent delegationx402AI Identity Management System (draft-ietf-wimse-aims)JWT Profile for OAuth 2.0 Access TokensHTTP Semantics (RFC 9110)