From 864d51964b92b0fbdb1710a9526a62bb38c27030 Mon Sep 17 00:00:00 2001 From: nedmsmith Date: Tue, 15 Aug 2023 16:26:38 -0700 Subject: [PATCH 1/7] Extensibility section updated Added text to extensibility section - see issue #10 --- draft-ietf-rats-corim.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index 76fcea22..cd73d1e5 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -99,6 +99,7 @@ informative: seriesinfo: Version 1.0, Revision 0.19 date: July 2020 target: https://trustedcomputinggroup.org/wp-content/uploads/DICE-Layering-Architecture-r19_pub.pdf + IANA.concise-software-identifier: coswid-reg entity: SELF: "RFCthis" @@ -1194,7 +1195,22 @@ applies to all measurements in the triple, including those in `measurement-value ## Extensibility {#sec-extensibility} -[^issue] https://github.com/ietf-rats-wg/draft-ietf-rats-corim/issues/10 +CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "sockets" (a.k.a., map structures) +and data types. CDDL socket extensions have the form `($$NAME-extension)` where "NAME" is the name of the map. +CDDL socket extensibility enables a CoRIM profile to extend the standard definition. +Typically, map extension requires a convention for code point naming that avoids code-point resue. +Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}. +Additionally, a range of code points may be reserved for vendor-specific use such as negative integers. + +Data type extensibility has the form `($NAME-type-choice)` where "NAME" is the type name and '$' signifies type extensibility. + +Socket and type extensions are permitted by the CoRIM schema where the above CDDL extensibility points are defined. +Schema extensions should be documented to facilitate interoperability. CoRIM profiles are best used to documennt +vendor or industry defined extensions. + +This specification uses CDDL type extension. Type extensions contained in this specification are considered +as "standard CoRIM types". Standard CoRIM types, along with the other CDDL expressions in this specification, +set the baseline for CoRIM interoperability. # CoBOM {#sec-cobom} From c6d88ef4989eeff20ada259b7432bace55df5f25 Mon Sep 17 00:00:00 2001 From: Ned Smith Date: Wed, 16 Aug 2023 07:00:21 -0700 Subject: [PATCH 2/7] Update draft-ietf-rats-corim.md Co-authored-by: Henk Birkholz --- draft-ietf-rats-corim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index cd73d1e5..771ce089 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1198,7 +1198,7 @@ applies to all measurements in the triple, including those in `measurement-value CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "sockets" (a.k.a., map structures) and data types. CDDL socket extensions have the form `($$NAME-extension)` where "NAME" is the name of the map. CDDL socket extensibility enables a CoRIM profile to extend the standard definition. -Typically, map extension requires a convention for code point naming that avoids code-point resue. +Typically, map extension requires a convention for code point naming that avoids code-point reuse. Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}. Additionally, a range of code points may be reserved for vendor-specific use such as negative integers. From fac5a626a11cdb567906752be4f19d6e815eaf62 Mon Sep 17 00:00:00 2001 From: Ned Smith Date: Thu, 14 Sep 2023 16:34:31 -0700 Subject: [PATCH 3/7] word choice replace socket with extension points --- draft-ietf-rats-corim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index 771ce089..b1ea7aac 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1195,7 +1195,7 @@ applies to all measurements in the triple, including those in `measurement-value ## Extensibility {#sec-extensibility} -CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "sockets" (a.k.a., map structures) +CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "extension points" (a.k.a., map structures) and data types. CDDL socket extensions have the form `($$NAME-extension)` where "NAME" is the name of the map. CDDL socket extensibility enables a CoRIM profile to extend the standard definition. Typically, map extension requires a convention for code point naming that avoids code-point reuse. From cd72ebdebb5d224381df7b2493aaf0a59c9528f4 Mon Sep 17 00:00:00 2001 From: Ned Smith Date: Thu, 14 Sep 2023 16:35:08 -0700 Subject: [PATCH 4/7] word choice replace socket with extension point --- draft-ietf-rats-corim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index b1ea7aac..e1772848 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1196,7 +1196,7 @@ applies to all measurements in the triple, including those in `measurement-value ## Extensibility {#sec-extensibility} CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "extension points" (a.k.a., map structures) -and data types. CDDL socket extensions have the form `($$NAME-extension)` where "NAME" is the name of the map. +and data types. CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the name of the map and '$$' signifies map extensibility. CDDL socket extensibility enables a CoRIM profile to extend the standard definition. Typically, map extension requires a convention for code point naming that avoids code-point reuse. Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}. From ec7ebd5f484e1e6e750b4251da258a7194a0e34d Mon Sep 17 00:00:00 2001 From: Ned Smith Date: Thu, 14 Sep 2023 16:35:37 -0700 Subject: [PATCH 5/7] wording replace socket with map --- draft-ietf-rats-corim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index e1772848..c8fc71f1 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1197,7 +1197,7 @@ applies to all measurements in the triple, including those in `measurement-value CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "extension points" (a.k.a., map structures) and data types. CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the name of the map and '$$' signifies map extensibility. -CDDL socket extensibility enables a CoRIM profile to extend the standard definition. +CDDL map extensibility enables a CoRIM profile to extend the base CoRIM definition. Typically, map extension requires a convention for code point naming that avoids code-point reuse. Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}. Additionally, a range of code points may be reserved for vendor-specific use such as negative integers. From 433c19ba563576983edb9c57aa31da38b5c808b7 Mon Sep 17 00:00:00 2001 From: Ned Smith Date: Thu, 14 Sep 2023 16:35:58 -0700 Subject: [PATCH 6/7] word choice replace socket with map --- draft-ietf-rats-corim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index c8fc71f1..65b257a5 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1204,7 +1204,7 @@ Additionally, a range of code points may be reserved for vendor-specific use suc Data type extensibility has the form `($NAME-type-choice)` where "NAME" is the type name and '$' signifies type extensibility. -Socket and type extensions are permitted by the CoRIM schema where the above CDDL extensibility points are defined. +Map and type extensions are permitted by the CoRIM schema where the above CDDL extensibility points are defined. Schema extensions should be documented to facilitate interoperability. CoRIM profiles are best used to documennt vendor or industry defined extensions. From b0f5fa147ddae4580b9fc2aef55d0d5062db0ba5 Mon Sep 17 00:00:00 2001 From: Yogesh Deshpande Date: Wed, 27 Sep 2023 15:23:01 +0100 Subject: [PATCH 7/7] Update draft-ietf-rats-corim.md --- draft-ietf-rats-corim.md | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/draft-ietf-rats-corim.md b/draft-ietf-rats-corim.md index 119538fe..86c0ec3b 100644 --- a/draft-ietf-rats-corim.md +++ b/draft-ietf-rats-corim.md @@ -1240,22 +1240,26 @@ applies to all measurements in the triple, including those in `measurement-value ## Extensibility {#sec-extensibility} -CoRIM is described using CDDL {{-cddl}} which includes extensibility support for "extension points" (a.k.a., map structures) -and data types. CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the name of the map and '$$' signifies map extensibility. +The base CORIM schema is described using CDDL {{-cddl}} that can be extended +only at specific allowed points known as "extension points" + +The following types of extensions are supported in CoRIM + +## Map Extensions +Map Extensions provides extensibility support to CoRIM Map structures. CDDL map extensibility enables a CoRIM profile to extend the base CoRIM definition. -Typically, map extension requires a convention for code point naming that avoids code-point reuse. +CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the name of the map +and '$$' signifies map extensibility. Typically, map extension requires a convention +for code point naming that avoids code-point reuse. Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}. Additionally, a range of code points may be reserved for vendor-specific use such as negative integers. -Data type extensibility has the form `($NAME-type-choice)` where "NAME" is the type name and '$' signifies type extensibility. +## Data Type Extensions -Map and type extensions are permitted by the CoRIM schema where the above CDDL extensibility points are defined. -Schema extensions should be documented to facilitate interoperability. CoRIM profiles are best used to documennt -vendor or industry defined extensions. +Data type extensibility has the form `($NAME-type-choice)` where "NAME" is the type name +and '$' signifies type extensibility. -This specification uses CDDL type extension. Type extensions contained in this specification are considered -as "standard CoRIM types". Standard CoRIM types, along with the other CDDL expressions in this specification, -set the baseline for CoRIM interoperability. +Schema extensions (Map or Data Type) should be documented to facilitate interoperability. CoRIM profiles are best used to document vendor or industry defined extensions. # CoBOM {#sec-cobom}