@@ -187,10 +187,10 @@ The structure fields are defined as follows:
187
187
- " token_type" is a 2-octet integer, in network byte order, as described
188
188
above.
189
189
190
- - " issuer_name" is a string containing the name of the issuer. This is a
191
- hostname that is used to identify the issuer that is allowed to issue
192
- tokens that can be redeemed by this origin. The string is prefixed with a
193
- 2-octet integer indicating the length, in network byte order.
190
+ - " issuer_name" is an ASCII string that identifies the issuer using the format of the authority portion of a URI
191
+ as defined in {{Section 3.2 of !URI=RFC3986}}. This name identifies the issuer that is allowed to
192
+ issue tokens that can be redeemed by this origin. The field that stores this string in the challenge
193
+ is prefixed with a 2-octet integer indicating the length, in network byte order.
194
194
195
195
- " redemption_context" is a field that is either 0 or 32 bytes, prefixed with a single
196
196
octet indicating the length (either 0 or 32). If value is non-empty, it is a 32-byte value
@@ -199,13 +199,14 @@ bound to a specific context, as opposed to reusing tokens that were fetched for
199
199
contexts. See {{context-construction}} for example contexts that might be useful in
200
200
practice. Challenges with redemption_context values of invalid lengths MUST be ignored.
201
201
202
- - " origin_info" is a string that is either empty, or contains one or more origin
203
- names that allow a token to be scoped to a specific set of origins. The string
204
- is prefixed with a 2-octet integer indicating the length, in network byte
205
- order. If empty, any non-origin-specific token can be redeemed. If the string
206
- contains multiple origin names, they are delimited with commas "," without any
207
- whitespace. If this field is not empty, the Origin MUST include its own name
208
- as one of the names in the list.
202
+ - " origin_info" is an ASCII string that is either empty, or contains one or more
203
+ origin names that allow a token to be scoped to a specific set of origins. Each
204
+ origin name uses the format of the authority portion of a URI as defined in
205
+ {{Section 3.2 of URI}}. The string is prefixed with a 2-octet integer indicating
206
+ the length, in network byte order. If empty, any non-origin-specific token can be
207
+ redeemed. If the string contains multiple origin names, they are delimited with
208
+ commas "," without any whitespace. If this field is not empty, the Origin MUST
209
+ include its own name as one of the names in the list.
209
210
210
211
When used in an authentication challenge, the "PrivateToken" scheme uses the
211
212
following parameters :
0 commit comments