Minutes IETF117: mediaman: Thu 22:30
minutes-117-mediaman-202307272230-00
Meeting Minutes | Media Type Maintenance (mediaman) WG | |
---|---|---|
Date and time | 2023-07-27 22:30 | |
Title | Minutes IETF117: mediaman: Thu 22:30 | |
State | Active | |
Other versions | markdown | |
Last updated | 2023-08-04 |
Meeting of the Mediaman WG at IETF 117 - 2023-07-27 - San Francisco
draft-ietf-mediaman-toplevel
one review, ready
No objections, meeting attendees agree with the document moving forward.
draft-ietf-mediaman-haptics
Harald believes it is ready.
Alexey agrees. Suggests a minor update is required and will propose
correction on mailing list.
draft-ietf-mediaman-suffixes
Manu: removed processing pipeline content from draft and produced new
draft 05
Alexey: We should ask IANA to signal when a registration is being
requested that uses the same base subtype as an existing type.
Specification required: yes.
Revision needed to the suffix registration process. Clarify if
registration template is needed in an RFC when IETF is the change
controller.
Guidance is needed for expert reviewers if they are required to make
judgement calls on the overlap of semantics of media types with
different suffixes.
draft-ietf-mediaman-standards-tree
Alexey: Concern about having expert reviewers verify adoption.
Consensus amongst participants to adopt.
6838bis or patch docs?
Harald: Allow toplevel to go forward and then roll into 6838bis
Harald: Finished docs can go to RFC, and inflight documents with
consensus can become part of 6838bis.
Alexey: Update charter to ensure future ADs are aware of decisions made
here.
Current wording suggests only the last +suffix describes the structure
of the document.