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

ned+dispatch@mrochek.com Thu, 01 July 2021 13:07 UTC

Return-Path: <ned+dispatch@mrochek.com>
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 55CAF3A0D6E for <dispatch@ietfa.amsl.com>; Thu, 1 Jul 2021 06:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
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 21ecZj6i_dyB for <dispatch@ietfa.amsl.com>; Thu, 1 Jul 2021 06:07:45 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [98.153.82.211]) (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 959873A0DB0 for <dispatch@ietf.org>; Thu, 1 Jul 2021 06:07:45 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01S0VLRAFQTS00GP7K@mauve.mrochek.com> for dispatch@ietf.org; Thu, 1 Jul 2021 06:02:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1625144547; bh=wQeVtaHonDoWbpFJq5VA9c2M6NbTQG3R4fMlXDL4UpU=; h=From:Cc:Date:Subject:In-reply-to:References:To:From; b=I1al44Y35XBkCuvf2YCLp0EnZH4H9j0FzF9K/LK4iswd4fBYcbtYzwT5uiBR96GYJ 5i3z+rv+E49Met5HYq5m9Viuoe56/CgDf9ndIPn5S+e77fXBffSlW1AJe9H/OtQB9B EClLApU8syQO5fXvGGSQrPZVWHar2cw6YkPJwCYo=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01S0F3SXH38G005PTU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for dispatch@ietf.org; Thu, 1 Jul 2021 06:02:22 -0700 (PDT)
From: ned+dispatch@mrochek.com
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, media-types@ietf.org, DISPATCH <dispatch@ietf.org>, Paul Libbrecht <paul@hoplahup.net>, Ned Freed <ned.freed@mrochek.com>
Message-id: <01S0VLR7TAIW005PTU@mauve.mrochek.com>
Date: Thu, 01 Jul 2021 05:54:18 -0700
In-reply-to: "Your message dated Thu, 01 Jul 2021 01:54:00 -0700" <CAL0qLwbALuW0uXXmu3kdCvPDbuK=mG4gwk2MZ1rMvMkdEaR9cQ@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> <F8EFFBD8-D8D4-439A-A6A7-0DBAD83FB939@hoplahup.net> <CAL0qLwamho3kpf1PAYMg77iTVohuUs-JQtz_fu3V7=4SAC5OVA@mail.gmail.com> <2aefbe02-bf86-4689-a8d3-b6fd8149ed56@www.fastmail.com> <CAL0qLwbALuW0uXXmu3kdCvPDbuK=mG4gwk2MZ1rMvMkdEaR9cQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/96H72YuOwWGWu6qOoXKr1AycreA>
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, 01 Jul 2021 13:07:50 -0000

> On Wed, Jun 30, 2021 at 9:24 AM Alexey Melnikov <aamelnikov@fastmail.fm>
> wrote:

> > Hi all,
> >
> > On Tue, Jun 22, 2021, at 11:36 PM, Murray S. Kucherawy wrote:
> >
> > On Wed, Jun 16, 2021 at 11:00 PM Paul Libbrecht <paul@hoplahup.net> wrote:
> >
> >
> > 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.
> >
> >
> > I am the guilty IETF-aware person...
> >
> > I am thinking that if we are doing all other related work we might as well
> > tackle this, so I am in support of doing this in the WG. Now ideally I
> > would like this to be addressed as an extension to the media type
> > registration template that list extra optional fields. So I don't want to
> > reopen RFC6838, but a separate draft that updates it would be great.

IMO a separate draft discussing additinal information would be the way
to go, assuming a separate draft is even needed. A quick check of the
form shows an OID field that isn't in RFC 6838. Additionally, RFC 6838
says to include the information "if available". I think an argument can
be made that Mac file type/creator codes are never available, so why
bother asing for them?

> It's in an internal review state now before being sent out for wider
> review, so there's time to make that sort of a change unless there's some
> kind of objection from the community.  I interpret Ned's earlier objections
> to touching RFC 6838 as being specific to the issue of top level media
> types, but you're talking about something else here.  Hopefully he can
> confirm (or correct) my understanding.

Speaking as a reviwer, the only additional information that's proved to be
difficult to deal with on occasions is magic numbers. It would be very helpful
to have some guidance as to how to specify them. The form of such guidance
doesn't really matter to me: A note to IANA, draft, whatever.

In any case, a work item to discuss what additional information to add/delete
would be  fine with me.

				Ned