Skip to content

Commit 6932a36

Browse files
Updates the prose for OptionalTokenResponse (#41)
* Updates the prose for OptionalTokenResponse Optional value is defined in the draft. OptionalTokenResponse should use it. * Update draft-ietf-privacypass-batched-tokens.md Co-authored-by: raphaelrobert <raphaelrobert@users.noreply.github.com> --------- Co-authored-by: raphaelrobert <raphaelrobert@users.noreply.github.com>
1 parent 0b70889 commit 6932a36

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

draft-ietf-privacypass-batched-tokens.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ structure of protocol messages. In addition to the base syntax, it uses two
123123
additional features: the ability for fields to be optional and the ability for
124124
vectors to have variable-size length headers.
125125

126-
## Optional Value
126+
## Optional Value {#optional-value}
127127

128128
An optional value is encoded with a presence-signaling octet, followed by the
129129
value itself if present. When decoding, a presence octet with a value other
@@ -509,10 +509,10 @@ struct {
509509
} BatchTokenResponse
510510
~~~
511511

512-
BatchTokenResponse.token_responses is a vector of OptionalTokenResponses, length
513-
prefixed with two bytes. OptionalTokenResponse.token_response is a
514-
length-prefix-encoded TokenResponse, where a length of 0 indicates that the
515-
Issuer failed or refused to issue the associated TokenRequest.
512+
BatchTokenResponse.token_responses is a variable-size vector of
513+
OptionalTokenResponses. OptionalTokenResponse.token_response is an
514+
optional TokenResponse (as specified in {{optional-value}}) , where an absence of TokenResponse indicates
515+
that the Issuer failed or refused to issue the associated TokenRequest.
516516

517517
The Issuer generates an HTTP response with status code 200 whose content
518518
consists of TokenResponse, with the content type set as

0 commit comments

Comments
 (0)