Re: [media-types] WG Review: Media Type Maintenance (mediaman)

[Larry Masinter <[e-mail]>]

I wrote an ID about MIME and web updates (in 2011):

https://www.ietf.org/archive/id/draft-masinter-mime-web-info-02.txt

I'd hoped also to review MIME Multipart for more modern uses (shades of WPACK)
https://mailarchive.ietf.org/arch/msg/wpack/EixjYebQDTdbcDS6FsE0eZye4ds/

although they haven't taken up my suggestion. Perhaps mediaman could take up such review?


Larry
--
https://LarryMasinter.net https://interlisp.org

> >> 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 reviewer’s 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 reviewer’s 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
> >> >
> >
> > _______________________________________________
> > media-types mailing list
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/media-types