Merge pull request #247 from oauth-wg/PieterKas-patch-7

Clarify "request_context"

Author: PieterKas

draft-ietf-oauth-transaction-tokens.md

@@ -519,9 +519,9 @@ To request a Txn-Token the workload invokes the OAuth 2.0 {{RFC6749}} token endp
   The type of the `subject_token` field is identified by `subject_token_type`.
 * `subject_token_type` REQUIRED. The value MUST indicate the type of the token or value present in the `subject_token` parameter
 
-The following additional parameters MAY be present in a Txn-Token Request:
+The following additional parameters are RECOMMENDED to be present in a Txn-Token Request:
 
-* `request_context` OPTIONAL. This parameter contains a base64url encoded JSON object which represents the context of this transaction. The parameter SHOULD be present and how the Transaction Token Service uses this parameter is out of scope for this specification.
+* `request_context` OPTIONAL. This parameter contains a base64url encoded JSON object which represents the context of this transaction.
 * `request_details` OPTIONAL. This parameter contains a base64url encoded JSON object which represents additional details of the transaction that MUST remain immutable throughout the processing of the transaction by multiple workloads. The Transaction Token Service uses this information to construct the `tctx` claim.
 
 The figure below {{figtxtokenrequest}} shows a non-normative example of a Txn-Token Request.
@@ -780,6 +780,7 @@ The authors would like to thank the contributors and the OAuth working group mem
 # Document History
 {: numbered="false"}
 [[ To be removed from final specification ]]
+* Remove contradiction in "request_details" description and simpliffy normative langugage [Clarify claim usage](https://github.com/oauth-wg/oauth-transaction-tokens/issues/228).
 
 ## Since Draft 06
 {:numbered="false"}