Hi Carsten,

On 11/02/2021 13:58, Carsten Bormann wrote:
The ACE AIF specification makes a number of media type registrations:

https://www.ietf.org/archive/id/draft-ietf-ace-aif-01.html#name-media-types-2

Excerpts below.

Please review.

This mostly looks fine, but the registration templates are missing some required and recommended fields from the template. Please review and update.

Thank you,

Alexey, as a media type designated expert

Grüße, Carsten


5.1.  Media Types

    IANA is requested to add the following Media-Type to the "Media
    Types" registry.

    +==========+======================+=====================+
    | Name     | Template             | Reference           |
    +==========+======================+=====================+
    | aif+cbor | application/aif+cbor | RFC XXXX, Section 4 |
    +----------+----------------------+---------------------+
    | aif+json | application/aif+json | RFC XXXX, Section 4 |
    +----------+----------------------+---------------------+

                             Table 3

    // RFC Ed.: please replace RFC XXXX with this RFC number and remove
    this note.

    Type name:  application
    Subtype name:  aif+cbor
    Required parameters:  none
    Optional parameters:  none
    Encoding considerations:  binary (CBOR)
    Security considerations:  Section 6 of RFC XXXX
    Published specification:  Section 4 of RFC XXXX
    Person & email address to contact for further information:  ACE WG
       mailing list ([email protected]), or IETF Applications and Real-Time
       Area ([email protected])
    Intended usage:  COMMON
    Restrictions on usage:  none
    Author/Change controller:  IETF



Bormann                  Expires 15 August 2021                 [Page 8]
Internet-Draft                   ACE AIF                   February 2021


    Type name:  application
    Subtype name:  aif+json
    Required parameters:  none
    Optional parameters:  none
    Encoding considerations:  binary (JSON is UTF-8-encoded text)
    Security considerations:  Section 6 of RFC XXXX
    Published specification:  Section 4 of RFC XXXX
    Person & email address to contact for further information:  ACE WG
       mailing list ([email protected]), or IETF Applications and Real-Time
       Area ([email protected])
    Intended usage:  COMMON
    Restrictions on usage:  none
    Author/Change controller:  IETF

_______________________________________________
media-types mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/media-types

_______________________________________________
Ace mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ace

Reply via email to