Add clarification for media type

All media types declared with IANA registered the same subtype. This
commit addresses it.

In addition, this commit makes the Content-Type for request and
responses normative with `MUST be`.

Closes ietf-wg-privacypass#33

Author: thibmeu

Diff for: draft-ietf-privacypass-batched-tokens.md

@@ -154,7 +154,7 @@ struct {
 } StructWithVectors;
 ~~~
 
-# Batched Privately Verifiable Token
+# Batched Privately Verifiable Token {#batched-privately-verifiable-token}
 
 This section describes a batched issuance protocol for select token types,
 including 0x0001 (defined in {{RFC9578}}) and 0x0005 (defined in this document).
@@ -221,7 +221,7 @@ The structure fields are defined as follows:
 
 The Client then generates an HTTP POST request to send to the Issuer Request
 URL, with the BatchTokenRequest as the content. The media type for this request
-is "application/private-token-privately-verifiable-batch-request". An example
+MUST be "application/private-token-privately-verifiable-batch-request". An example
 request for the Issuer Request URL "https://issuer.example.net/request" is shown
 below.
 
@@ -323,7 +323,7 @@ The structure fields are defined as follows:
   Scalar values, computed as `concat(SerializeScalar(proof[0]),
   SerializeScalar(proof[1]))`, where Ns is as defined in {{OPRF, Section 4}}.
 
-The Issuer generates an HTTP response with status code 200 whose content
+The Issuer MUST generate an HTTP response with status code 200 whose content
 consists of TokenResponse, with the content type set as
 "application/private-token-privately-verifiable-batch-response".
 
@@ -409,7 +409,7 @@ struct {
 If the FinalizeBatch function fails, the Client aborts the protocol. Token
 verification works exactly as specified in {{RFC9578}}.
 
-# Arbitrary Batched Token Issuance
+# Arbitrary Batched Token {#arbitrary-batched-token}
 
 This section describes an issuance protocol mechanism for issuing multiple
 tokens in one round trip between Client and Issuer. An arbitrary batched token
@@ -455,7 +455,7 @@ The structure fields are defined as follows:
 
 The Client then generates an HTTP POST request to send to the Issuer Request
 URL, with the BatchTokenRequest as the content. The media type for this request
-is "application/private-token-arbitrary-batch-request". An example request for
+MUST be "application/private-token-arbitrary-batch-request". An example request for
 the Issuer Request URL "https://issuer.example.net/request" is shown below.
 
 ~~~
@@ -508,7 +508,7 @@ prefixed with two bytes. OptionalTokenResponse.token_response is a
 length-prefix-encoded TokenResponse, where a length of 0 indicates that the
 Issuer failed or refused to issue the associated TokenRequest.
 
-The Issuer generates an HTTP response with status code 200 whose content
+The Issuer MUST generate an HTTP response with status code 200 whose content
 consists of TokenResponse, with the content type set as
 "application/private-token-arbitrary-batch-response".
 
@@ -591,7 +591,7 @@ Type name:
 
 Subtype name:
 
-: private-token-request
+: private-token-privately-verifiable-batch-request
 
 Required parameters:
 
@@ -619,7 +619,8 @@ Published specification:
 
 Applications that use this media type:
 
-: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
+: Applications that want to issue or facilitate issuance of Privacy Pass
+  Batched Privately Verifiable tokens as defined in {{batched-privately-verifiable-token}},
   including Privacy Pass issuer applications themselves.
 
 Fragment identifier considerations:
@@ -664,7 +665,7 @@ Type name:
 
 Subtype name:
 
-: private-token-response
+: private-token-privately-verifiable-batch-response
 
 Required parameters:
 
@@ -692,7 +693,8 @@ Published specification:
 
 Applications that use this media type:
 
-: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
+: Applications that want to issue or facilitate issuance of Privacy Pass
+  Batched Privately Verifiable tokens as defined in {{batched-privately-verifiable-token}},
   including Privacy Pass issuer applications themselves.
 
 Fragment identifier considerations:
@@ -737,7 +739,7 @@ Type name:
 
 Subtype name:
 
-: private-token-request
+: private-token-arbitrary-batch-request
 
 Required parameters:
 
@@ -765,7 +767,8 @@ Published specification:
 
 Applications that use this media type:
 
-: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
+: Applications that want to issue or facilitate issuance of Privacy Pass
+  Arbitrary Batched tokens as defined in {{arbitrary-batched-token}},
   including Privacy Pass issuer applications themselves.
 
 Fragment identifier considerations:
@@ -810,7 +813,7 @@ Type name:
 
 Subtype name:
 
-: private-token-response
+: private-token-arbitrary-batch-response
 
 Required parameters:
 
@@ -838,7 +841,8 @@ Published specification:
 
 Applications that use this media type:
 
-: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
+: Applications that want to issue or facilitate issuance of Privacy Pass
+  Arbitrary Batched tokens as defined in {{arbitrary-batched-token}},
   including Privacy Pass issuer applications themselves.
 
 Fragment identifier considerations: