[dispatch] Proposed/draft charter for "mediaman"

["Murray S. Kucherawy" <[e-mail]>]

Comments welcome, including my late-night choice of name.

-MSK



Media Type Maintenance (“MEDIAMAN”) Working Group Charter [DRAFT]

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

Several 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.  In particular, we have for the first time a request for a
new top-level media type, and such requests are sufficiently rare that our
current processes don’t make it clear how this request should be evaluated
and dispatched.

This working group will therefore, under this instance of the charter, take
up the following work.  The working group has discretion to order these as
appropriate.


   -

   Establish criteria and procedures for registering top-level media
   types.  In particular, specify whether these requests can be handled by the
   current IANA media type review team, require IETF Consensus, or should
   follow some other process.
   -

   Develop and process the pending ‘haptics’ top-level media type request,
   based on draft-muthusamy-dispatch-haptics.
   -

   Consider whether and how to permit multiple media type suffixes.
   -

   Consider any issues around media types for programming languages.
   -

   Determine revised criteria regarding Security Considerations sections in
   media type applications.
   -

   Review the format of the media types registry itself.


It is expected that the working group will produce a document updating RFC
6838 (BCP 13) as a result of the points above, and a “haptics” standards
track registration RFC.  Any other work is out of scope.

On completion of these goals, the working group will discuss whether it
would be appropriate for this to become a standing (perhaps usually
dormant) working group containing the expertise needed to repeat these
reviews periodically, and/or to handle those applications such as the
top-level request that are too large in scope for the IANA media type
review team.  If so, the working group will negotiate a new charter
accordingly.

Input Document(s):

   -

   draft-muthusamy-dispatch-haptics


Proposed milestones (target dates TBD):

   -

   draft-muthusamy-dispatch-haptics (or equivalent) to the IESG for
   approval (Proposed Standard)
   -

   RFC6838bis to the IESG for approval (BCP)