Re: [dispatch] [media-types] Proposed/draft charter for "mediaman"

Paul Libbrecht <paul@hoplahup.net> Thu, 17 June 2021 06:00 UTC

Return-Path: <paul@hoplahup.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A43B3A0BF1 for <dispatch@ietfa.amsl.com>; Wed, 16 Jun 2021 23:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 MlIRtKbaUWI9 for <dispatch@ietfa.amsl.com>; Wed, 16 Jun 2021 23:00:45 -0700 (PDT)
Received: from 8.mo6.mail-out.ovh.net (8.mo6.mail-out.ovh.net [178.33.42.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CB7C3A0BF5 for <dispatch@ietf.org>; Wed, 16 Jun 2021 23:00:45 -0700 (PDT)
Received: from player756.ha.ovh.net (unknown [10.108.4.127]) by mo6.mail-out.ovh.net (Postfix) with ESMTP id 9DA54252FE5 for <dispatch@ietf.org>; Thu, 17 Jun 2021 08:00:39 +0200 (CEST)
Received: from hoplahup.net (pd9526c86.dip0.t-ipconnect.de [217.82.108.134]) (Authenticated sender: paul@hoplahup.net) by player756.ha.ovh.net (Postfix) with ESMTPSA id 5DE6F1E6B4519; Thu, 17 Jun 2021 06:00:31 +0000 (UTC)
Authentication-Results: garm.ovh; auth=pass (GARM-103G0051e9e8aaa-9f3f-44bf-8dd6-867e44977416, F6872317591DAD382EA4BBECE7B115767A5CA861) smtp.auth=paul@hoplahup.net
X-OVh-ClientIp: 217.82.108.134
From: Paul Libbrecht <paul@hoplahup.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: DISPATCH list <dispatch@ietf.org>, media-types@ietf.org, John C Klensin <john-ietf@jck.com>, Mark Nottingham <mnot@mnot.net>, Ned Freed <ned.freed@mrochek.com>
Date: Thu, 17 Jun 2021 08:00:29 +0200
X-Mailer: MailMate (1.14r5757)
Message-ID: <F8EFFBD8-D8D4-439A-A6A7-0DBAD83FB939@hoplahup.net>
In-Reply-To: <CAL0qLwY0AMORExhAT=Euzn6y2jWQmA9r4vSYCsymBj8_-fshuQ@mail.gmail.com>
References: <CAL0qLwavrxxa=fdn48-F8Dt2qBDFEJyPoNjSkYOiHi-46k1Wtw@mail.gmail.com> <01RYY5BDVHVK0085YQ@mauve.mrochek.com> <5F193852-2CBE-4885-A7E9-14B377DFB5E2@mnot.net> <CAL0qLwZOvFqYtcXGV_bdHJ_PkUjJdGZJ+itoUxjF-4xYzgbDGQ@mail.gmail.com> <01RZSLCQGG9Y00IM2V@mauve.mrochek.com> <CAL0qLwZJ2nPaiFOWZf9SOPP3pAK5kmm8t1Xu7A36xiwJDd8_Jw@mail.gmail.com> <DD5C1199-9179-460C-B4F7-B26451EAF754@mnot.net> <CAL0qLwZeqdko+7+MtawzXe=BDys1LH=wzUdv+9ye4uSr7yNURA@mail.gmail.com> <CAL0qLwY0AMORExhAT=Euzn6y2jWQmA9r4vSYCsymBj8_-fshuQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_6E092FDA-B3FC-4C71-A732-4B91B137EC81_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"plain":[690, 1346], "uuid":"D8F3582F-A199-4D36-B27D-C23814523BBC"}]
X-Ovh-Tracer-Id: 16503159360533825669
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledrfeeftddgleekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffoffkjghfgggtgfesrgekmherredtjeenucfhrhhomhepfdfrrghulhcunfhisggsrhgvtghhthdfuceophgruhhlsehhohhplhgrhhhuphdrnhgvtheqnecuggftrfgrthhtvghrnhepudeggeetudeujeefuefgteeikefhheeufffftdehvdelgedtleegffdthfdvtefhnecuffhomhgrihhnpehivghtfhdrohhrghenucfkpheptddrtddrtddrtddpvddujedrkedvrddutdekrddufeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpqdhouhhtpdhhvghlohepphhlrgihvghrjeehiedrhhgrrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpehprghulheshhhophhlrghhuhhprdhnvghtpdhrtghpthhtohepughishhprghttghhsehivghtfhdrohhrgh
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/4iuJZwZKCliMhnY2o2wr5utxabM>
Subject: Re: [dispatch] [media-types] Proposed/draft charter for "mediaman"
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jun 2021 06:00:50 -0000

Hello list,

It’s interesting to see a renovation wind about the registration 
process and details.

I am wondering if the group is the right place to prepare an update of 
the registration template so as remove the Macintosh 4-letter-codes and 
insert clipboard flavours for windows and universal type identifiers for 
macOS.

This was discussed a few times on this mailing list.
I have been in contact with a few media-type proposers, some of which 
have accepted a change of their declaration in this direction.
I have been in contact with one IETF-aware person to update RFC6838 but 
that has not progressed.

Thanks in advance.

Paul

On 16 Jun 2021, at 21:49, Murray S. Kucherawy wrote:

> On Sun, Jun 13, 2021 at 11:47 PM Murray S. Kucherawy 
> <superuser@gmail.com>
> wrote:
>
>> I've folded this suggestion and John's into the draft charter, which 
>> I've
>> now added to the datatracker so that people can see changes over time 
>> as we
>> iterate:
>>
>> https://datatracker.ietf.org/doc/charter-ietf-mediaman/
>>
>> Please have a look and let me know if this is good enough to proceed 
>> to
>> the formal part of chartering.  Note that the process still requires 
>> two
>> review passes through the IESG and one formal round of public 
>> commentary,
>> so I'm wondering if people feel like it might be close enough to 
>> start
>> those processes, or if we should iterate here again first.
>>
>> I've also, per John's suggestion, inquired about whether ISO 
>> generally, or
>> a TC specific to haptics, is already listed as an approved SDO for 
>> media
>> type registrations.   Even if they are, though, BCP 13 still requires 
>> a
>> standards track RFC for a top-level registration, though the path he
>> proposes would be fine for all the sub-registrations they might want 
>> to
>> make.
>>
>
> (Adding the "media-types@ietf.org" list, so people there can comment 
> if
> needed before I start the process)
>
> An additional question: Would it be better to use the existing media 
> types
> IETF list for this work, or should it get a separate mailing list?
>
> -MSK

> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types