Original text:
8.1. IANA has created a new registry titled "EDHOC Exporter Label" under <del> the new heading "EDHOC".  The registration procedure is "Expert Review".  The columns of the registry are Label, Description, and Reference.  All columns are text strings.  The initial contents of the registry are: </del>  8.2. IANA has created a new registry titled "EDHOC Cipher Suites" under <del> the new heading "EDHOC".  The registration procedure is "Expert Review".  The columns of the registry are Value, Array, Description, and Reference, where Value is an integer and the other columns are text strings.  The initial contents of the registry are: </del>  8.3. IANA has created a new registry entitled "EDHOC Method Type" under <del> the new heading "EDHOC".  The registration procedure is "Expert Review".  The columns of the registry are Value, Description, and Reference, where Value is an integer and the other columns are text strings.  The initial contents of the registry are shown in fig- method-types. </del>  8.4. IANA has created a new registry entitled "EDHOC Error Codes" under <del> the new heading "EDHOC".  The registration procedure is "Specification Required".  The columns of the registry are ERR_CODE, ERR_INFO Type and Description, where ERR_CODE is an integer, ERR_INFO is a CDDL defined type, and Description is a text string.  The initial contents of the registry are shown in fig-error-codes. </del>  8.5. IANA has created a new registry entitled "EDHOC External <del> Authorization Data" under the new heading "EDHOC".  The registration procedure is "Expert Review".  The columns of the registry are Value, Description, and Reference, where Value is an integer and the other columns are text strings. </del>  8.6. <del> This document registers the following entries in the "COSE Header Parameters" registry under the "CBOR Object Signing and Encryption (COSE)" heading.  The value of the 'cwt' header parameter is a COSE Web Token (CWT) RFC8392 and the value of the 'uccs' header parameter is an Unprotected CWT Claims Set (UCCS), see term. </del>  8.7. <del> IANA has extended the Value Type of the COSE Header Parameter 'kid' to also allow the Value Type int.  The resulting Value Type is bstr / int.  The 'kid' parameter can be used to identify a key stored in a UCCS, in a CWT, or in a public key certificate.  (The Value Registry for this item is empty and omitted from the table below.) </del>  8.8. <del> IANA has extended the Value Type of the COSE Key Common Parameter 'kid' to the COSE Key Value Type int.  The resulting Value Type is bstr / int.  (The Value Registry for this item is empty and omitted from the table below.) </del>  8.9. <del> IANA has extended the Value Type of the WT Confirmation Methods 'kid' to the COSE Key Value Type int.  The incorrect term binary string has been corrected to bstr.  The resulting Value Type is bstr / int.  The new updated content for the 'kid' method is shown in the list below. </del>  Confirmation Method Name: kid 8.10. <del> IANA has added the well-known URI "edhoc" to the Well-Known URIs registry. </del>  URI suffix: edhoc 8.11. <del> IANA has added the media type "application/edhoc" to the Media Types registry. </del>  Type name: application 8.12. <del> IANA has added the media type "application/edhoc" to the CoAP Content-Formats registry. </del>  Media Type: application/edhoc 8.13.  The IANA Registries established in this document is defined as "Expert Review".  This section gives some general guidelines for what the experts should be looking for, but they are being designated as

Reviewer comments:
A new Resource Type (rt=) Link Target attribute like "URL" may be registered in the "Resource Type (rt=) Link Target Attribute Values" subregistry under the "Constrained RESTful Environments (CoRE) Parameters" registry.
That seems like a good idea.
Marco, do you want to provide a PR? Then we could merge that for -11
Done, see URL Note that the first commit is just about removing trailing whitespace to avoid compiling errors. The content you need is in the commit URL
Looks good. I tried to align the whole IANA section with RFC 8126. Then I merged.

Revised text:
8.1. IANA has created a new registry titled "EDHOC Exporter Label" under  <ins> the new group name "Ephemeral Diffie-Hellman Over COSE (EDHOC)".  The registration procedure is "Expert Review".  The columns of the registry are Label, Description, and Reference.  All columns are text strings.  The initial contents of the registry are: </ins> 8.2. IANA has created a new registry titled "EDHOC Cipher Suites" under  <ins> the new group name "Ephemeral Diffie-Hellman Over COSE (EDHOC)".  The registration procedure is "Expert Review".  The columns of the registry are Value, Array, Description, and Reference, where Value is an integer and the other columns are text strings.  The initial contents of the registry are: </ins> 8.3. IANA has created a new registry entitled "EDHOC Method Type" under  <ins> the new group name "Ephemeral Diffie-Hellman Over COSE (EDHOC)".  The registration procedure is "Expert Review".  The columns of the registry are Value, Description, and Reference, where Value is an integer and the other columns are text strings.  The initial contents of the registry are shown in fig-method-types. </ins> 8.4. IANA has created a new registry entitled "EDHOC Error Codes" under  <ins> the new group name "Ephemeral Diffie-Hellman Over COSE (EDHOC)".  The registration procedure is "Specification Required".  The columns of the registry are ERR_CODE, ERR_INFO Type and Description, where ERR_CODE is an integer, ERR_INFO is a CDDL defined type, and Description is a text string.  The initial contents of the registry are shown in fig-error-codes. </ins> 8.5. IANA has created a new registry entitled "EDHOC External  <ins> Authorization Data" under the new group name "Ephemeral Diffie- Hellman Over COSE (EDHOC)".  The registration procedure is "Expert Review".  The columns of the registry are Value, Description, and Reference, where Value is an integer and the other columns are text strings. </ins> 8.6.  <ins> IANA has registered the following entries in the "COSE Header Parameters" registry under the group name "CBOR Object Signing and Encryption (COSE)".  The value of the 'cwt' header parameter is a COSE Web Token (CWT) RFC8392 and the value of the 'uccs' header parameter is an Unprotected CWT Claims Set (UCCS), see term.  The Value Registry for this item is empty and omitted from the table below. </ins> 8.7.  <ins> IANA has extended the Value Type of 'kid' in the "COSE Header Parameters" registry under the group name "CBOR Object Signing and Encryption (COSE)" to also allow the Value Type int.  The resulting Value Type is bstr / int.  The Value Registry for this item is empty and omitted from the table below. </ins> 8.8.  <ins> IANA has extended the Value Type of 'kid' in the "COSE Key Common Parameters" registry under the group name "CBOR Object Signing and Encryption (COSE)" to also allow the Value Type int.  The resulting Value Type is bstr / int.  The Value Registry for this item is empty and omitted from the table below. </ins> 8.9.  <ins> IANA has extended the Value Type of 'kid' in the "CWT Confirmation Methods" registry under the group name "CBOR Web Token (CWT) Claims" to also allow the Value Type int.  The incorrect term binary string has been corrected to bstr.  The resulting Value Type is bstr / int. The new updated content for the 'kid' method is shown in the list below. </ins> Confirmation Method Name: kid 8.10.  <ins> IANA has added the well-known URI "edhoc" to the "Well-Known URIs" registry under the group name "Well-Known URIs". </ins> URI suffix: edhoc 8.11.  <ins> IANA has added the media type "application/edhoc" to the "Media Types" registry. </ins> Type name: application 8.12.  <ins> IANA has added the media type "application/edhoc" to the "CoAP Content-Formats" registry under the group name "Constrained RESTful Environments (CoRE) Parameters". </ins> Media Type: application/edhoc 8.13. <ins> IANA has added the resource type "core.edhoc" to the "Resource Type (rt=) Link Target Attribute Values" registry under the group name "Constrained RESTful Environments (CoRE) Parameters". Value: "core.edhoc" Description: EDHOC resource. Reference: [[this document]] Client applications can use this resource type to discover a server's resource for EDHOC, where to send a request for executing the EDHOC protocol. 8.14. </ins> The IANA Registries established in this document is defined as "Expert Review".  This section gives some general guidelines for what the experts should be looking for, but they are being designated as