Re: [media-types] [Ext] Francesca Palombini's No Objection on draft-ietf-mediaman-toplevel-03: (with COMMENT)

[Harald Alvestrand <[e-mail]>]

On 9/18/23 19:30, Amanda Baber wrote:
> Hi,
> 
> IANA is actually being asked to create a registry, but we haven't been told how to fully populate it. This is what we've pieced together:
> 
> Name: Top-Level Media Types
> Reference: this document
> Registration Procedure: Standards Action
> 
> Type | Reference | Comment
> Application | ? |
> Audio | ? |
> Font | RFC 8081 |
> Example | RFC 4735 |
> Image | ? |
> Message | ? |
> Model | RFC 2077 |
> Multipart | ? |
> Text | ? |
> Video | ? |

I think the references can be:

- Text: RFC 6838 section 4.2.1
- Image: RFC 6838 section 4.2.2
- Audio: RFC 6838 section 4.2.3
- Video: RFC 6838 section 4.2.4
- Application: RFC 6838 section 4.2.5
- Multipart: RFC 6838 section 4.2.6
- Message: RFC 6838 section 4.2.6

I hope this helps!

Harald

>   
> The narrative in Section 3 (not part of the IANA Considerations section) appears to indicate that RFC 1341 should be listed as the reference for the other types, but when we were revising the media type submission form (for submissions outside for RFCs), the designated experts told us that RFC 2046 was the relevant document, as recording in the "Type Name" menu: https://www.iana.org/form/media-types
> 
> The IANA Considerations section also says that the comment field "may" list "requires CRLF for newlines" for the "text" registration and "no registrations, for examples only" for the "example" registration, but IANA cannot determine whether to implement those suggestions.
> 
> We strongly prefer that a table or list of registrations that tells us how to populate each field in the new registry be added to the IANA Considerations section.
> 
> Thanks,
> 
> Amanda Baber
> IANA Operations Manager
> 
> On 9/18/23, 5:20 AM, "iesg on behalf of Francesca Palombini via Datatracker" <[e-mail] on behalf of [e-mail]> wrote:
> 
>      Francesca Palombini has entered the following ballot position for
>      draft-ietf-mediaman-toplevel-03: No Objection
> 
>      When responding, please keep the subject line intact and reply to all
>      email addresses included in the To and CC lines. (Feel free to cut this
>      introductory paragraph, however.)
> 
> 
>      Please refer to https://urldefense.com/v3/__https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/__;!!PtGJab4!_NAu_UmFAcUUTwYZyp8gUKGVGvJkWwHGiMjXWqQlYBtX04XYYSWfb9_ND61BT-LgFjlaLLPIVVWbEKAA-64OXUQ$ [ietf[.]org]
>      for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
>      The document, along with other ballot positions, can be found here:
>      https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-mediaman-toplevel/__;!!PtGJab4!_NAu_UmFAcUUTwYZyp8gUKGVGvJkWwHGiMjXWqQlYBtX04XYYSWfb9_ND61BT-LgFjlaLLPIVVWbEKAAN2Lvsgc$ [datatracker[.]ietf[.]org]
> 
> 
> 
>      ----------------------------------------------------------------------
>      COMMENT:
>      ----------------------------------------------------------------------
> 
>      Thank you for the work on this document.
> 
>      I would suggest to request IANA to add a pointer to this document in the media
>      types IANA page
>      (https://www.iana.org/assignments/media-types/media-types.xhtml) either in one
>      of the existing "Notes", or creating a new one. Not a strong suggestion since
>      the link exists via RFC 6838, but why not making it easier for the reader to
>      find this. Also, I would suggest IANA to add a link to this doc in their
>      Application page https://www.iana.org/form/media-types.
> 
>      Francesca
> 
>