Re: [Cellar] WG Review: Media Type Maintenance (mediaman) (fwd) tom petch: Re: WG Review: Media Type Maintenance (mediaman)

[Michael Richardson <[e-mail]>]

Hi, the members of this WG might like to comment on the charter for this new
WG.  please use the "[e-mail]" list.

It may be that there should be some cross-discussion about this new
"haptics" top-level MIME type with CELLAR when the WG is chartered.

I've forwarded the entire email, but I wanted to highlight:

> A new IETF WG has been proposed in the Applications and Real-Time Area. The
> IESG has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please send your
> comments to the IESG mailing list ([e-mail]) by 2021-07-12.
>
> Media Type Maintenance (mediaman)
> -----------------------------------------------------------------------

> Mailing list:
>    Address: [e-mail]
>    To subscribe: https://www.ietf.org/mailman/listinfo/media-types
>    Archive: https://mailarchive.ietf.org/arch/browse/media-types/
>
> Group page: https://datatracker.ietf.org/group/mediaman/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-mediaman/

...

> The registration of a top-level media type is a rare event.  BCP 13 describes
> the process for doing so, as was used in RFC 8081, but it does not provide
> any guidance or criteria regarding what constitutes an appropriate
> registration.

...
> * Develop and process the pending ‘haptics’ top-level media type request,
> based on draft-muthusamy-dispatch-haptics, and the outcome of the previous
> work item.

and from draft-muthusamy-dispatch-haptics:

2.  Background and Justification

   Haptic signals provide an additional layer of entertainment and
   sensory immersion for the user.  Haptic tracks, in separate files,
   can be combined with audio/video files and played back in sync to
   provide an overall immersive media experience (audio, visual,
   tactile) for the user.  More recently, haptic tracks embedded in
   standard file formats such as ISOBMFF (ISO Base Media File Format),
   enable playback of the haptic signals over one or more actuators,
   simultaneously with audio and video playback.

--- Begin Message ---

A small tweak.

Most of the discussions I see about media types relate to NETCONF and
YANG.  The text below talks of programming languages.  I would like that
expanded to be clear that it includes YANG, if not all such DDL.

The registrations thereof might have been different had multiple
suffixes been specified.

Tom Petch

On 02/07/2021 18:53, The IESG wrote:
> A new IETF WG has been proposed in the Applications and Real-Time Area. The
> IESG has not made any determination yet. The following draft charter was
> submitted, and is provided for informational purposes only. Please send your
> comments to the IESG mailing list ([e-mail]) by 2021-07-12.
>
> Media Type Maintenance (mediaman)
> -----------------------------------------------------------------------
> Current status: Proposed WG
>
> Chairs:
>    TBD
>
> Assigned Area Director:
>    Murray Kucherawy <[e-mail]>
>
> Applications and Real-Time Area Directors:
>    Murray Kucherawy <[e-mail]>
>    Francesca Palombini <[e-mail]>
>
> Mailing list:
>    Address: [e-mail]
>    To subscribe: https://www.ietf.org/mailman/listinfo/media-types
>    Archive: https://mailarchive.ietf.org/arch/browse/media-types/
>
> Group page: https://datatracker.ietf.org/group/mediaman/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-mediaman/
>
> IANA maintains a registry of media types and subtypes that are used to
> identify particular payloads and their semantics as they are transported via
> application level protocols such as messaging (email) and the web (HTTP).
> The core structure and use of media types is the MIME framework, defined in
> RFCs 2045 through 2049, and amended by various later documents.  Registration
> of new media types is defined by BCP 13, which was last updated in 2013.
>
> The registration of a top-level media type is a rare event.  BCP 13 describes
> the process for doing so, as was used in RFC 8081, but it does not provide
> any guidance or criteria regarding what constitutes an appropriate
> registration.
>
> Several other topics have appeared in the interim that are large enough in
> scope and importance to warrant the formation of a working group to develop
> and process them.  This working group will therefore take up the following
> items, in this order (or as otherwise negotiated with the supervising Area
> Director):
>
> * Determine whether any specific criteria or guidance are warranted to handle
> registration of future top-level media types, and publish any such guidance.
>
> * Develop and process the pending haptics top-level media type request,
> based on draft-muthusamy-dispatch-haptics, and the outcome of the previous
> work item.
>
> * Consider whether and how to permit multiple media type suffixes.
>
> * Develop a reviewers checklist regarding Security Considerations sections
> in media type applications.
>
> * Consider any issues around media types for programming languages.
>
> * Review the format of the media types registry itself.
>
> * Evaluate the registry policies and procedures in the context of how media
> types are currently used, and modify them if necessary.
>
> This last item will consider the existing use of GitHub for managing
> registrations and the processing queues for the link relations and well
> known URIs registries as examples.
>
> Input Document(s):
> * draft-muthusamy-dispatch-haptics
>
> * draft-w3cdidwg-media-types-with-multiple-suffixes
>
> Proposed milestones (target dates TBD):
> * Publish any specific criteria or guidance for handling registration of
> future top-level media types, either as an RFC or a wiki page.
>
> * draft-muthusamy-dispatch-haptics (or equivalent) to the IESG for approval
> (Proposed Standard)
>
> * A draft about handling multiple suffixes to the IESG for approval (BCP)
>
> * Publish a reviewers checklist about Security Considerations in media type
> applications, either as an RFC or a wiki page.
>
> * Deliver recommendations about the media types registry format.
>
> * Deliver any recommendations about future registration and queue management.
>
> Milestones:
>
> TBD
>
> _______________________________________________
> IETF-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

--- End Message ---

--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide