IANA: Address early review feedback

[mickenordin]

Feedback from early review:

Dear Authors (cc: ocm),

Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document:

https://datatracker.ietf.org/doc/html/draft-ietf-ocm-open-cloud-mesh-05

Section 14.1: Please add the registry’s “Status” field. 

Sections 14.2-14.4: it’s hard to read the registration data here, but one note: IANA will add a reference to the descriptions presented here. If you’d like us to point to a specific section of the document instead of just the document, you should add something like “See RFC XXXX, Section Y.” to the end of the description. 

14.4: For this section, we'll add an entry to the “JSContact Enum Values” registry and then creating a subregistry for it. Could you separate the creation of the subregistry into a Section 14.4.1, possibly called “JSContact Enum Values Subregistry”? This could be introduced with a line like  “IANA will create a subregistry for [if I understand correctly] ietf.org:ocmAddresses/source (Context: Card) in accordance with RFC 9553, Section 3.7.2. Initial contents:”

Note that the subregistry should have the “Since,” “Until,” etc. fields in the parent registry (i.e., JSContact Enum Values). Those aren’t represented in the tables from RFC 9553, Section 3.7.3 on because the authors described the contents of those fields in the first paragraph of each subsection. 

If you have any questions, just let us know. If you'd like to talk in person, you can find us at the IANA table from Monday through Thursday. You can also request another review at any time by contacting us at iana@iana.org.

For more information about IANA Considerations section requirements, please see

https://www.iana.org/help/protocol-registration

Best regards,

...
IANA

Changes made to address the concerns

• Status field added to the .well-known URI registration
• Make JSContact registration templates more readable
• Separate out the creation of the JSContact enum values subregistry into its own subsection
• Add references to RFC XXX (this document), with a note to the RFC editors to replace it with the RFC number once that is established
• Add version 06 changelog entry

[MahdiBaghbani]

Seems ok to me based on the email from IANA

[glpatcern]

Same here, thanks for the quick reaction Micke.
I'm not sure we need the extra leading : on the values but that's nitpicking and we can sort it out later.
I'll prepare some additional text for the changelog.

[mickenordin]

Same here, thanks for the quick reaction Micke. I'm not sure we need the extra leading : on the values but that's nitpicking and we can sort it out later. I'll prepare some additional text for the changelog.

I believe this is the syntax for a definition list in kramdown markdown, so it was put there deliberately: https://kramdown.gettalong.org/syntax.html#definition-lists

Although it is never easy to know how it will end up un rendered format :)