From 1c178f98d5e03edf55463bbd82e29d475120b3e4 Mon Sep 17 00:00:00 2001
From: Aykut Bulut <aykutb@google.com>
Date: Tue, 20 Feb 2024 13:49:13 -0500
Subject: [PATCH] Fix TLS presentation language types

TLS presentation language types are in form of uint8 not uint8_t.
See https://www.rfc-editor.org/rfc/rfc8446.html#section-3.3
---
 draft-ietf-privacypass-auth-scheme.md | 20 +++++++-------
 draft-ietf-privacypass-protocol.md    | 38 +++++++++++++--------------
 2 files changed, 29 insertions(+), 29 deletions(-)

diff --git a/draft-ietf-privacypass-auth-scheme.md b/draft-ietf-privacypass-auth-scheme.md
index b9646576..f13245c5 100644
--- a/draft-ietf-privacypass-auth-scheme.md
+++ b/draft-ietf-privacypass-auth-scheme.md
@@ -190,7 +190,7 @@ The default TokenChallenge message has the following structure:
 
 ~~~
 struct {
-    uint16_t token_type;
+    uint16 token_type;
     opaque issuer_name<1..2^16-1>;
     opaque redemption_context<0..32>;
     opaque origin_info<0..2^16-1>;
@@ -400,11 +400,11 @@ The default Token message has the following structure:
 
 ~~~
 struct {
-    uint16_t token_type;
-    uint8_t nonce[32];
-    uint8_t challenge_digest[32];
-    uint8_t token_key_id[Nid];
-    uint8_t authenticator[Nk];
+    uint16 token_type;
+    uint8 nonce[32];
+    uint8 challenge_digest[32];
+    uint8 token_key_id[Nid];
+    uint8 authenticator[Nk];
 } Token;
 ~~~
 
@@ -476,10 +476,10 @@ protocol corresponding to the token type with the following value as the input:
 
 ~~~
 struct {
-    uint16_t token_type;
-    uint8_t nonce[32];
-    uint8_t challenge_digest[32];
-    uint8_t token_key_id[Nid];
+    uint16 token_type;
+    uint8 nonce[32];
+    uint8 challenge_digest[32];
+    uint8 token_key_id[Nid];
 } AuthenticatorInput;
 ~~~
 
diff --git a/draft-ietf-privacypass-protocol.md b/draft-ietf-privacypass-protocol.md
index 839c69ef..929cd5e9 100644
--- a/draft-ietf-privacypass-protocol.md
+++ b/draft-ietf-privacypass-protocol.md
@@ -340,9 +340,9 @@ The Client then creates a TokenRequest structured as follows:
 
 ~~~
 struct {
-  uint16_t token_type = 0x0001; /* Type VOPRF(P-384, SHA-384) */
-  uint8_t truncated_token_key_id;
-  uint8_t blinded_msg[Ne];
+  uint16 token_type = 0x0001; /* Type VOPRF(P-384, SHA-384) */
+  uint8 truncated_token_key_id;
+  uint8 blinded_msg[Ne];
 } TokenRequest;
 ~~~
 
@@ -408,8 +408,8 @@ structured as follows:
 
 ~~~
 struct {
-   uint8_t evaluate_msg[Ne];
-   uint8_t evaluate_proof[Ns+Ns];
+   uint8 evaluate_msg[Ne];
+   uint8 evaluate_proof[Ns+Ns];
 } TokenResponse;
 ~~~
 
@@ -454,11 +454,11 @@ succeeds, the Client then constructs a Token as follows:
 
 ~~~
 struct {
-  uint16_t token_type = 0x0001; /* Type VOPRF(P-384, SHA-384) */
-  uint8_t nonce[32];
-  uint8_t challenge_digest[32];
-  uint8_t token_key_id[32];
-  uint8_t authenticator[Nk];
+  uint16 token_type = 0x0001; /* Type VOPRF(P-384, SHA-384) */
+  uint8 nonce[32];
+  uint8 challenge_digest[32];
+  uint8 token_key_id[32];
+  uint8 authenticator[Nk];
 } Token;
 ~~~
 
@@ -580,9 +580,9 @@ The Client then creates a TokenRequest structured as follows:
 
 ~~~
 struct {
-  uint16_t token_type = 0x0002; /* Type Blind RSA (2048-bit) */
-  uint8_t truncated_token_key_id;
-  uint8_t blinded_msg[Nk];
+  uint16 token_type = 0x0002; /* Type Blind RSA (2048-bit) */
+  uint8 truncated_token_key_id;
+  uint8 blinded_msg[Nk];
 } TokenRequest;
 ~~~
 
@@ -637,7 +637,7 @@ TokenResponse structure:
 
 ~~~
 struct {
-  uint8_t blind_sig[Nk];
+  uint8 blind_sig[Nk];
 } TokenResponse;
 ~~~
 
@@ -669,11 +669,11 @@ follows:
 
 ~~~
 struct {
-  uint16_t token_type = 0x0002; /* Type Blind RSA (2048-bit) */
-  uint8_t nonce[32];
-  uint8_t challenge_digest[32];
-  uint8_t token_key_id[32];
-  uint8_t authenticator[Nk];
+  uint16 token_type = 0x0002; /* Type Blind RSA (2048-bit) */
+  uint8 nonce[32];
+  uint8 challenge_digest[32];
+  uint8 token_key_id[32];
+  uint8 authenticator[Nk];
 } Token;
 ~~~