[media-types] Re: [Ext] Re: Standards tree registratio n and RFC 6838
Martin J. Dürst <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Organization | Aoyama Gakuin University |
| Message-ID | <[email protected]> |
Hello Amanda, Mark, others,
On 2025-09-12 13:56, Amanda Baber wrote:
> Hi Mark,
>
> Sorry about the late review here. The community formats section looks pretty clear to me, but some notes/questions about other sections:
>
> Section 3.1.1:
>
> This section's last bullet point says that the example top-level type has an "example" subtype, but RFC 4735 told us not to register that (although it did have us register an example subtype for the other then-extant top-level types). I have no idea whether this would be confusing to anyone outside of IANA.
This is text taken over verbatim from RFC 9694 (Section 2.1), and so
essentially my bad, sorry. I don't have the time to dig further to find
out where this might have been coming from.
I propose to change the bullet to read as follows:
* At a minimum, one subtype (not including a potential 'example'
subtype) MUST be described. A top-level type without any subtypes
serves no purpose. The only exception is the 'example' top-level
type, with no registered subtypes.
Please take this as a Last Call comment on draft-ietf-mediaman-6838bis-06.
Regards, Martin.
_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]