Grant Negotiation and Authorization Protocol (GNAP)
RFC 9635
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['authentication', 'delegation', 'security']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "F. Imbault": changed name from "Fabien Imbault" to "F. Imbault" |
|
2026-05-20
|
(System) | Changed author "J. Richer": changed name from "Justin Richer" to "J. Richer", changed is_editor from "False" to "True" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2025-12-28
|
(System) | Received changes through RFC Editor sync (removed Errata tag (all errata rejected)) |
|
2024-12-04
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2024-10-09
|
(System) | IANA registries were updated to include RFC9635 |
|
2024-10-08
|
(System) | Received changes through RFC Editor sync (created document RFC 9635, created became rfc relationship between draft-ietf-gnap-core-protocol and RFC 9635, set title to 'Grant … Received changes through RFC Editor sync (created document RFC 9635, created became rfc relationship between draft-ietf-gnap-core-protocol and RFC 9635, set title to 'Grant Negotiation and Authorization Protocol (GNAP)', set abstract to 'The Grant Negotiation and Authorization Protocol (GNAP) defines a mechanism for delegating authorization to a piece of software and conveying the results and artifacts of that delegation to the software. This delegation can include access to a set of APIs as well as subject information passed directly to the software.', set pages to 187, set standardization level to Proposed Standard, added RFC published event at 2024-10-08) |
|
2024-10-08
|
(System) | RFC published |