[media-types] Planning for IETF 112: Agenda?

Harald Alvestrand <harald@alvestrand.no> Fri, 08 October 2021 10:56 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2EC3A1638 for <media-types@ietfa.amsl.com>; Fri, 8 Oct 2021 03:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2LaosFWS5jg for <media-types@ietfa.amsl.com>; Fri, 8 Oct 2021 03:56:32 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D09E53A1639 for <media-types@ietf.org>; Fri, 8 Oct 2021 03:56:31 -0700 (PDT)
Received: from [192.168.3.157] (unknown [78.156.11.215]) by mork.alvestrand.no (Postfix) with ESMTPSA id B08887C7306 for <media-types@ietf.org>; Fri, 8 Oct 2021 12:56:26 +0200 (CEST)
To: media-types@ietf.org
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <65d0f7c1-24b8-5242-c2fe-42aaf82fccda@alvestrand.no>
Date: Fri, 8 Oct 2021 12:56:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/PiSk7Tt3ti_TkkIlA-1asfwiM5E>
Subject: [media-types] Planning for IETF 112: Agenda?
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Oct 2021 10:56:36 -0000

I've started trying to figure out an agenda for IETF 112.

One critical question that will be asked is: Do we have the engagemente 
needed to carry out our charter?

I've put together a "work items with assigned shepherds" document here:

https://github.com/alvestrand/mediaman/blob/main/work-items.md

As you can see, it's rather empty on the "assignments" front.

The very first item on our charter (and a blocking item for the -haptics 
document) is "guidelines for top level types". As part of the IETF 112 
discussion, I'll be asking:

- Do we need it?

- What form should it take? (Web page, registry intro paragraph, RFC for 
BCP 13 addition, other?)

- Who's willing to hold the pen on it?

This will be the first item on our agenda.

Second will be the question of WG adoption of 
draft-muthusamy-dispatch-haptics.

Suggestions for other agenda items welcome!


Harald