Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify "standard CoRIM type" #206

Merged
merged 5 commits into from
Mar 6, 2024
Merged

Clarify "standard CoRIM type" #206

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ed9892a
Clarify "standard CoRIM type"
deeglaze Feb 14, 2024
be12d1e
Update draft-ietf-rats-corim.md
yogeshbdeshpande Mar 6, 2024
89dd379
Update draft-ietf-rats-corim.md
yogeshbdeshpande Mar 6, 2024
d5a3c8d
Update draft-ietf-rats-corim.md
yogeshbdeshpande Mar 6, 2024
5731911
Merge branch 'main' into baseorstandard
yogeshbdeshpande Mar 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions draft-ietf-rats-corim.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -432,7 +432,7 @@ Profiling is the mechanism that allows the base CoRIM schema to be customised to

A profile defines which of the optional parts of a CoRIM are required,
which are prohibited and which extension points are exercised and how.
A profile MUST NOT alter the syntax or semantics of a standard CoRIM type.
A profile MUST NOT alter the syntax or semantics of CoRIM types defined in this document.
A profile MAY constrain the values of a given CoRIM type to a subset of the values.
A profile MAY extend the set of a given CoRIM type using the defined extension points (see {{sec-extensibility}}).
Exercised extension points should preserve the intent of the original semantics.
Expand All @@ -453,6 +453,7 @@ that MUST have a different identifier.
{::include cddl/profile-type-choice.cddl}
~~~


### Entities {#sec-corim-entity}

The CoRIM Entity is an instantiation of the Entity generic
Expand Down Expand Up @@ -1352,7 +1353,7 @@ CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the
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.
Non-negative integers are reserved for IANA to assign meaning globally.

### Data Type Extensions

Expand Down Expand Up @@ -2183,7 +2184,7 @@ Environments (CoRE) Parameters" Registry {{!IANA.core-parameters}}:

--- back

# Full CoRIM CDDL
# Full CoRIM CDDL {#sec-corim-cddl}

~~~ cddl
{::include cddl/corim-autogen.cddl}
Expand Down