Draft: draft-palombini-ace-key-groupcomm

Commentary: Following and a chat at IETF103 . 
 AP8 : ' pubkeysrepos ' , as a CBOR array of tstr containing URIs .
Mailing list commentary: Hi , Thanks a lot for your detailed review , as you might have seen we have included most comments in the latest version : Please note that this version includes also review comments from , which in some cases overlapped , so some text might be reformulated to include both inputs . , detailed comments and some questions . Thanks , Francesca
'kty', identifying the key type of the key.
'kty', identifying the key type of the key.  The set of values can
be found in the Key Type column of the "ACE Groupcomm Key".
Implementations MUST verify that the key type matches the profile
being used, if present, as registered in the "ACE Groupcomm Key"
registry.
The exact format of the 'key' value MUST be defined in applications
of this specifications.  Additionally, documents specifying the key
format MUST register it in the "ACE Groupcomm Key" registry,
including its name, type and profile to be used with, as defined in
the "ACE Groupcomm Key" registry, defined in iana-key.
This specification establishes the IANA "ACE Groupcomm Profile"
registry.  The registry has been created to use the "Expert Review
Required" registration procedure RFC8126.  It should be noted that,
in addition to the expert review, some portions of the registry
require a specification, potentially a Standards Track RFC, be
supplied as well.
Name: This is a descriptive name that enables easier reference to
the item.  The name MUST be unique.  It is not used in the
encoding.
Key Type Value: This is the value used to identify the keying
material.  These values MUST be unique.  The value can be a
positive integer, a negative integer, or a string.
Profile: This field may contain a descriptive string of a profile
to be used with this item.  This should be a value that is in the
Name column of the "ACE Groupcomm Profile" registry.
Description: This field contains a brief description of the keying
material.
References: This contains a pointer to the public specification
for the format of the keying material, if one exists.
This registry has been initially populated by the values in kty.  The
specification column for all of these entries will be this document.
This specification establishes the IANA "ACE Groupcomm Profile"
registry.  The registry has been created to use the "Expert Review
Required" registration procedure RFC8126.  Expert review guidelines
are provided in review.  It should be noted that, in addition to the
expert review, some portions of the registry require a specification,
potentially a Standards Track RFC, be supplied as well.
Reference: This contains a pointer to the public specification of
the profile abbreviation, if one exists.
The IANA registry 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
experts for a reason so they should be given substantial latitude.
Point squatting should be discouraged.  Reviewers are encouraged
to get sufficient information for registration requests to ensure
that the usage is not going to duplicate one that is already
registered and that the point is likely to be used in deployments.
The zones tagged as private use are intended for testing purposes
and closed environments, code points in other ranges should not be
assigned for testing.
Specifications are required for the standards track range of point
assignment.  Specifications should exist for specification
required ranges, but early assignment before a specification is
available is considered to be permissible.  Specifications are
needed for the first-come, first-serve range if they are expected
to be used outside of closed environments in an interoperable way.
When specifications are not provided, the description provided
needs to have sufficient information to identify what the point is
being used for.