From ec0464eaaad7634f4a698aca70c4c91343fc59ef Mon Sep 17 00:00:00 2001 From: Henk Birkholz Date: Tue, 17 Oct 2023 13:43:00 +0200 Subject: [PATCH 1/7] proposal to rephrase the Reg_Info definition --- draft-ietf-scitt-architecture.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index b652757e..c9c002ef 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -624,9 +624,16 @@ All Signed Statements MUST include the following protected headers: - Issuer (label: `TBD`, temporary: `391`): DID (Decentralized Identifier {{DID-CORE}}) of the signer, as a string. `did:web:example.com` is an example of a DID. - Feed (label: `TBD`, temporary: `392`): The Issuer's name for the Artifact, as a string. - Content type (label: `3`): Media type of payload, as a string. For example, `application/spdx+json` is the media type of SDPX in JSON encoding. -- Registration Policy info (label: `TBD`, temporary: `393`): A map of additional attributes to help enforce Registration Policies. +- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs provided and controlled by the Issuer that are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each individual Issuer or are specific to the Issuer and Feed tupel. Examples include: sequence number of signed statement on feed, Issuer metadata, or reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). - Key ID (label: `4`): Key ID, as a bytestring. + +Registration: + +: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing it in the Registry, producing a Receipt, and returning it to the submitting Issuer. + + + In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows: ~~~ cddl From f7fa9f3e19f907f1f08f06351b42638ebfb397bf Mon Sep 17 00:00:00 2001 From: Steve Lasker Date: Tue, 17 Oct 2023 17:05:58 -0700 Subject: [PATCH 2/7] Apply suggestions from code review --- draft-ietf-scitt-architecture.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index c9c002ef..e5d6d2e1 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -630,9 +630,7 @@ All Signed Statements MUST include the following protected headers: Registration: -: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing it in the Registry, producing a Receipt, and returning it to the submitting Issuer. - - +: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, producing a Receipt, and returning it to the submitting Issuer. In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows: From 32181ed10dfcb0c8c7e580b394cd25a9d20960dc Mon Sep 17 00:00:00 2001 From: Henk Birkholz Date: Wed, 18 Oct 2023 16:15:20 +0200 Subject: [PATCH 3/7] Update draft-ietf-scitt-architecture.md Co-authored-by: Steve Lasker Co-authored-by: Henk Birkholz Co-authored-by: Steve Lasker --- draft-ietf-scitt-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index e5d6d2e1..ca1823c5 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -624,7 +624,7 @@ All Signed Statements MUST include the following protected headers: - Issuer (label: `TBD`, temporary: `391`): DID (Decentralized Identifier {{DID-CORE}}) of the signer, as a string. `did:web:example.com` is an example of a DID. - Feed (label: `TBD`, temporary: `392`): The Issuer's name for the Artifact, as a string. - Content type (label: `3`): Media type of payload, as a string. For example, `application/spdx+json` is the media type of SDPX in JSON encoding. -- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs provided and controlled by the Issuer that are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each individual Issuer or are specific to the Issuer and Feed tupel. Examples include: sequence number of signed statement on feed, Issuer metadata, or reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). +- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs set by the Issuer which are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each Issuer or are specific to the Issuer and Feed tupel. Examples include: the sequence number of signed statements on a feed, Issuer metadata, or a reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). - Key ID (label: `4`): Key ID, as a bytestring. From b24df6aee89d1c64d279bd65bac2b5d516b732b3 Mon Sep 17 00:00:00 2001 From: Henk Birkholz Date: Wed, 18 Oct 2023 16:17:03 +0200 Subject: [PATCH 4/7] Update draft-ietf-scitt-architecture.md Co-authored-by: Jon Geater Co-authored-by: Henk Birkholz Co-authored-by: Jon Geater --- draft-ietf-scitt-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index ca1823c5..1af6af47 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -630,7 +630,7 @@ All Signed Statements MUST include the following protected headers: Registration: -: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, producing a Receipt, and returning it to the submitting Issuer. +: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, and producing a Receipt. In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows: From f98e886edeed379d275be766e49b2ecd769ae846 Mon Sep 17 00:00:00 2001 From: Steve Lasker Date: Wed, 18 Oct 2023 07:31:56 -0700 Subject: [PATCH 5/7] Update draft-ietf-scitt-architecture.md --- draft-ietf-scitt-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index 1af6af47..f7c6b7fc 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -624,7 +624,7 @@ All Signed Statements MUST include the following protected headers: - Issuer (label: `TBD`, temporary: `391`): DID (Decentralized Identifier {{DID-CORE}}) of the signer, as a string. `did:web:example.com` is an example of a DID. - Feed (label: `TBD`, temporary: `392`): The Issuer's name for the Artifact, as a string. - Content type (label: `3`): Media type of payload, as a string. For example, `application/spdx+json` is the media type of SDPX in JSON encoding. -- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs set by the Issuer which are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each Issuer or are specific to the Issuer and Feed tupel. Examples include: the sequence number of signed statements on a feed, Issuer metadata, or a reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). +- Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs set by the Issuer which are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each Issuer or are specific to the Issuer and Feed tuple. Examples include: the sequence number of signed statements on a feed, Issuer metadata, or a reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). - Key ID (label: `4`): Key ID, as a bytestring. From fce952811118969011e21130eaa3956828fb1281 Mon Sep 17 00:00:00 2001 From: steve lasker Date: Mon, 16 Oct 2023 13:38:42 -0700 Subject: [PATCH 6/7] Move dupe of Registration definiton, merging content Signed-off-by: steve lasker --- draft-ietf-scitt-architecture.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index f7c6b7fc..04c24cf5 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -205,7 +205,7 @@ Receipt: Registration: -: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing it in the Registry, producing a Receipt, and returning it to the submitting Issuer. +: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, and producing a Receipt. Registration Policy: @@ -627,11 +627,6 @@ All Signed Statements MUST include the following protected headers: - Registration Policy info (label: `TBD`, temporary: `393`): A map containing key/value pairs set by the Issuer which are sealed on Registration and non-opaque to the Transparency Service. The key/value pair semantics are specified by each Issuer or are specific to the Issuer and Feed tuple. Examples include: the sequence number of signed statements on a feed, Issuer metadata, or a reference to other transparent statements (e.g., augments, replaces, new-version, CPE-for). - Key ID (label: `4`): Key ID, as a bytestring. - -Registration: - -: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, and producing a Receipt. - In CDDL {{-CDDL}} notation, a Signed_Statement is defined as follows: ~~~ cddl From 3694890a62b8c77afa42f5655da0e116ede2ac9a Mon Sep 17 00:00:00 2001 From: Steve Lasker Date: Wed, 18 Oct 2023 08:18:32 -0700 Subject: [PATCH 7/7] Update draft-ietf-scitt-architecture.md Merging as this is a well discussed pattern with SCITT Co-authored-by: Orie Steele --- draft-ietf-scitt-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-scitt-architecture.md b/draft-ietf-scitt-architecture.md index 04c24cf5..aa9cddeb 100644 --- a/draft-ietf-scitt-architecture.md +++ b/draft-ietf-scitt-architecture.md @@ -205,7 +205,7 @@ Receipt: Registration: -: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, storing the Signed Statement in the Registry, and producing a Receipt. +: the process of submitting a Signed Statement to a Transparency Service, applying the Transparency Service's Registration Policy, and producing a Receipt. Registration Policy: