From 8da217b79dba5df6d00d057dbe9dc67becf1734d Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Tue, 6 Aug 2024 18:45:22 -0700 Subject: [PATCH 1/4] Enhance JPT payload description --- draft-ietf-jose-json-proof-token.md | 26 ++++++++++++++++++-------- 1 file changed, 18 insertions(+), 8 deletions(-) diff --git a/draft-ietf-jose-json-proof-token.md b/draft-ietf-jose-json-proof-token.md index 379ba10c..fa9e8c58 100644 --- a/draft-ietf-jose-json-proof-token.md +++ b/draft-ietf-jose-json-proof-token.md @@ -133,20 +133,29 @@ The following is an example JWP Protected Header that includes a `cid`: > Editor's Note: This section is incomplete. Use it only as an indicator of the intended direction. Application resolves each claim as required when processing the JPT. Resolution can result in one of three things: -1. A disclosed JSON value -2. A custom proof method -3. A `null` value +1. A disclosed JSON value. +1. An indicator that the value was not disclosed. +1. An algorithm-specific proof method. ## Disclosed -Always an octet string of valid JSON text. +A disclosed payloads are represented as a base64url-encoded UTF-encoded octet string +representing a valid JSON value. + +## Undisclosed + +The placeholder indicating that a payload was not disclosed is represented as +a `null` value for the JWP JSON Serialization +or the empty string value for the JWP Compact Serialization. ## Proof Methods -* proof methods can be returned instead of a disclosed payload -* these are generated by the algorithm from information in the JWP's proof value -* a proof method may be custom based on the capabilities of the algorithm -* define common proof method types available? +Proof methods can be returned instead of a disclosed payload. +These are generated in an algorithm-specific manner from information in the JWP's proof value. + +A proof method may be custom based on the capabilities of the algorithm. + +* TBD: Describe common proof method types available? * range * membership * time @@ -205,6 +214,7 @@ for his valuable contributions to this specification. [[ To be removed from the final specification ]] * Update reference to new repository home + * Enhance JPT payload description. -05 From 5827a5ce72a3081c83955f8869f0c4d05162e177 Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Tue, 6 Aug 2024 18:58:51 -0700 Subject: [PATCH 2/4] Discuss issued and presented forms of JPTs --- draft-ietf-jose-json-proof-token.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/draft-ietf-jose-json-proof-token.md b/draft-ietf-jose-json-proof-token.md index fa9e8c58..3b611c1c 100644 --- a/draft-ietf-jose-json-proof-token.md +++ b/draft-ietf-jose-json-proof-token.md @@ -128,18 +128,16 @@ The following is an example JWP Protected Header that includes a `cid`: <{{./fixtures/template/jpt-issuer-protected-header-with-cid.json}} -# Payloads +# Presented Claims and Proofs -> Editor's Note: This section is incomplete. Use it only as an indicator of the intended direction. - -Application resolves each claim as required when processing the JPT. Resolution can result in one of three things: +Each claim in the issued form of the JPT results in one of three things in the presented form of the JPT: 1. A disclosed JSON value. 1. An indicator that the value was not disclosed. 1. An algorithm-specific proof method. ## Disclosed -A disclosed payloads are represented as a base64url-encoded UTF-encoded octet string +A disclosed payload is represented as a base64url-encoded UTF-encoded octet string representing a valid JSON value. ## Undisclosed @@ -214,7 +212,7 @@ for his valuable contributions to this specification. [[ To be removed from the final specification ]] * Update reference to new repository home - * Enhance JPT payload description. + * Fixed #99: Discussed issued and presented forms of JPTs. -05 From a57873394a7d36545e03db5f067a21fcade239d4 Mon Sep 17 00:00:00 2001 From: "Michael B. Jones" Date: Tue, 20 Aug 2024 15:57:07 -0700 Subject: [PATCH 3/4] Applied DW's suggestion Co-authored-by: David Waite --- draft-ietf-jose-json-proof-token.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/draft-ietf-jose-json-proof-token.md b/draft-ietf-jose-json-proof-token.md index 3b611c1c..b8c67d6f 100644 --- a/draft-ietf-jose-json-proof-token.md +++ b/draft-ietf-jose-json-proof-token.md @@ -137,8 +137,7 @@ Each claim in the issued form of the JPT results in one of three things in the p ## Disclosed -A disclosed payload is represented as a base64url-encoded UTF-encoded octet string -representing a valid JSON value. +A disclosed payload is represented as a UTF-encoded octet string representing a valid JSON value. ## Undisclosed From dd57464a7590875b96ecac699d4ef2c662a66005 Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Tue, 20 Aug 2024 20:28:39 -0700 Subject: [PATCH 4/4] Applied modularity suggestion by DW --- draft-ietf-jose-json-proof-token.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/draft-ietf-jose-json-proof-token.md b/draft-ietf-jose-json-proof-token.md index 3b611c1c..c84d4d85 100644 --- a/draft-ietf-jose-json-proof-token.md +++ b/draft-ietf-jose-json-proof-token.md @@ -143,8 +143,7 @@ representing a valid JSON value. ## Undisclosed The placeholder indicating that a payload was not disclosed is represented as -a `null` value for the JWP JSON Serialization -or the empty string value for the JWP Compact Serialization. +described in Section 6 (Serializations) of [@!I-D.ietf-jose-json-web-proof]. ## Proof Methods