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

On 2021-07-05 1:00, Michael Richardson wrote:
> 
> Hi, the members of this WG might like to comment on the charter for this new
> WG.  please use the "media-types@ietf.org" list.

It seems mostly related to MIME types. We don't use MIME types for media 
type identifications, just for attachments.

> 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.

The haptics track is interesting and something we should definitely 
support. It seems it would fall under the "control" (32) track type.

We do define some "unofficial" MIME types for Matroska:
* .mka : Matroska audio `audio/x-matroska`
* .mkv : Matroska video `video/x-matroska`
* .mk3d : Matroska 3D video `video/x-matroska-3d`

I don't know if we should register official ones. The Internet is 
probably using these everywhere already. Not sure there is much benefit 
apart from making them more official.

> 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 (iesg@ietf.org) by 2021-07-12.
>>
>> Media Type Maintenance (mediaman)
>> -----------------------------------------------------------------------
> 
>> Mailing list:
>>     Address: media-types@ietf.org
>>     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.
> 
> 
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> 
> 
> 
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar
> 