The OAuth 2.1 Internet-Draft
OAuth 2.1 consolidates the framework agent tooling already depends on, replacing RFC 6749 and RFC 6750 and folding in a decade of security practice. It is still an active Internet-Draft. The Model Context Protocol requires authorization servers to implement it, so a large part of agent authorization rests on a document that is not yet an RFC.
The verdict
Verified
The document exists. The ledger fetched it at its publisher and quotes it.
Key facts
What the sources say
- Record ID
- AAL-2026-0012
- Kind
- Draft in progress
- Jurisdiction
- Global
- Last verified
- Added
- The draft states that it replaces and obsoletes the OAuth 2.0 Authorization Framework described in RFC 6749 and the Bearer Token Usage in RFC 6750.
- The latest revision at the time of checking is draft-ietf-oauth-v2-1-16, dated 3 September 2026.
- It remains an active Internet-Draft rather than a published RFC.
- MCP authorization requires authorization servers to implement OAuth 2.1 for both confidential and public clients.
Dimension by dimension
1 dimension, each one stated, silent or open
Authorization. Stated means the document you can open below says it; silent means the ledger read the document and it does not.
- AuthorizationStated
- It is the authorization baseline the agent tooling ecosystem cites, including mandatory PKCE and the removal of the implicit and password grants.IETF Datatracker, draft-ietf-oauth-v2-1, primary source, 3 September 2026.
What it changes
For a team deploying an agent
Your agent stack cites a draft. That is normal in this field and not a defect, but it belongs in your risk register: revision numbers move, and a control you wrote against draft 13 may read differently at draft 16. Pin the revision you implemented and re read it when you upgrade.
Sources
What this record was verified against
- IETF Datatracker, draft-ietf-oauth-v2-1Primary · 3 September 2026
Related
Records that sit beside this one
RFC 6749, the OAuth 2.0 authorization framework
Global · verified 15 September 2026
The framework enables a third party application to obtain limited access to an HTTP service on behalf of a resource owner, or on its own behalf.
Model Context Protocol authorization
Global · verified 15 September 2026
Authorization servers must implement OAuth 2.1 with appropriate security measures for both confidential and public clients.
Does a spending limit belong to the agent or to the principal
Global · verified 15 September 2026
The Visa Trusted Agent Protocol addresses recognising an approved agent and its intent, and does not itself carry a spending ceiling.
How does a sub agent's authority attenuate
Global · verified 15 September 2026
RFC 8693 lets a token record that one party is acting for another, but does not require the exchanged token to be narrower.
Can an agent hold a credential of its own
Global · verified 15 September 2026
NIST SP 800-63-4 states that for that publication, person refers only to natural persons.
Who is liable when a delegated agent exceeds its mandate
Global · verified 15 September 2026
The EU AI Act allocates duties to providers and deployers, and does not address an agent acting beyond its instructions.
Cite this record
Free to reuse under CC BY 4.0, with attribution. The record ID AAL-2026-0012 is permanent and is never reused.
- In a sentence
- According to the GAGE Agent Authority Ledger (as of 15 September 2026), the oauth 2.1 internet-draft.
- APA
- GAGE (Global Academy of Generative-AI Education). (2026). The OAuth 2.1 Internet-Draft. Agent Authority Ledger. Retrieved 15 September 2026, from https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0012-oauth-2-1-internet-draft
- MLA
- "The OAuth 2.1 Internet-Draft." Agent Authority Ledger, GAGE (Global Academy of Generative-AI Education), 15 September 2026, https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0012-oauth-2-1-internet-draft.
- Chicago
- GAGE (Global Academy of Generative-AI Education). "The OAuth 2.1 Internet-Draft." Agent Authority Ledger. Last modified 15 September 2026. https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0012-oauth-2-1-internet-draft.
- Permalink
- https://www.gage.academy/tools/agent-authority-ledger/records/AAL-2026-0012-oauth-2-1-internet-draft
Last updated . Every record re verified . The ledger is checked weekly, every Monday, and the same day for any NIST, IETF or MCP publication.
Back to the full ledger, or every record for Global and every draft in progress record.
GAGE briefings tell you which AI regulation deadlines are coming, what they actually require of you, and when a program opens.