From f76d2a5baa8cb29539606efb2cd6383df1270992 Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Tue, 27 Aug 2024 15:09:24 +0200 Subject: [PATCH] Fix management token description copy-paste error It seems this paragraph about the management token was copy-pasted from the description of the request continuation token and not yet fully adapted. This commit attempts to fix that. --- draft-ietf-gnap-core-protocol.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/draft-ietf-gnap-core-protocol.md b/draft-ietf-gnap-core-protocol.md index ed5003f..a838df0 100644 --- a/draft-ietf-gnap-core-protocol.md +++ b/draft-ietf-gnap-core-protocol.md @@ -2043,15 +2043,15 @@ The value of the `manage` field is an object with the following properties: REQUIRED. `access_token` (object): -: A unique access token for continuing the request, called the "token management access token". +: A unique access token for managing the token, called the "token management access token". The value of this property MUST be an object in the format specified in {{response-token-single}}. This access token MUST be bound to the client instance's key used in the request (or its most recent rotation) and MUST NOT be a bearer token. As a consequence, the `flags` array of this access token MUST NOT contain the string `bearer` and the `key` field MUST be omitted. - This access token MUST NOT have a `manage` field. + This access token MUST NOT itself have a `manage` field. This access token MUST NOT have the same value as the token it is managing. - The client instance MUST present the continuation access token in all requests to the continuation URI as described in {{use-access-token}}. + The client instance MUST present the continuation access token in all requests to the token management URI as described in {{token-management}}. REQUIRED. The values of the `flags` field defined by this specification are as follows: