Re: [media-types] updates to RFC6838 in the horizon?

Ned Freed <ned.freed@mrochek.com> Sat, 20 October 2018 14:50 UTC

Return-Path: <ned.freed@mrochek.com>
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 BE20612D4F0 for <media-types@ietfa.amsl.com>; Sat, 20 Oct 2018 07:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.208
X-Spam-Level:
X-Spam-Status: No, score=-1.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 GYMtUptNbOsO for <media-types@ietfa.amsl.com>; Sat, 20 Oct 2018 07:50:04 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) (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 878A1127B92 for <media-types@ietf.org>; Sat, 20 Oct 2018 07:50:04 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYNOB7XALC00F1SO@mauve.mrochek.com> for media-types@ietf.org; Sat, 20 Oct 2018 07:45:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1540046699; bh=v2pUtaFa13gLWeRtBfZZ6Nx/7TxXl8JqeLmG4wuWdWo=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=L/UytjLMQ1rPy3n7opRHFGxyPD+cTeoAQoLEnY7jKOePXCjcCeeJKo3L2tBIKJssU 7Wk+Cu7YMjzi9qkGFQyePrxpBGzKHaMydderYpS5gfo/12EQ8IOo26aU4qyfPDVNW9 I7x+sFOgarCGR4CncJedNFq9v9uaraRszvHY1ZGc=
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="utf-8"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYM8BK7VLS00BGSX@mauve.mrochek.com>; Sat, 20 Oct 2018 07:44:56 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, Alexey Melnikov <alexey.melnikov@isode.com>, media-types@ietf.org, Chris Lilley <chris@w3.org>
Message-id: <01QYNOB5YLQS00BGSX@mauve.mrochek.com>
Date: Sat, 20 Oct 2018 07:41:33 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 19 Oct 2018 08:17:33 +0200" <D2F76E58-663D-4BCD-8F85-B30224BA4EAE@hoplahup.net>
References: <e25a4143-7999-4ed0-9947-776033636f15@getmailbird.com> <01Q88GLSKJC4011H9Q@mauve.mrochek.com> <44F6AEF0-8A25-4981-8620-293FD5907483@hoplahup.net> <D01957F2-D4C6-4899-8417-C90B7546CD54@hoplahup.net> <f63aa5c6-5c45-8c91-3285-3421621e2621@isode.com> <01QYLCD6GWBE00BGSX@mauve.mrochek.com> <D2F76E58-663D-4BCD-8F85-B30224BA4EAE@hoplahup.net>
To: Paul Libbrecht <paul@hoplahup.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/K67vqa6hYrDGrNmqqQ4JLiOKk1Y>
Subject: Re: [media-types] updates to RFC6838 in the horizon?
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: Sat, 20 Oct 2018 14:50:06 -0000

> Thank you Ned,

> On 19 Oct 2018, at 0:38, Ned Freed wrote:

> > I don't see a problem with a draft updating the template. Pretty low
> > cost thing
> > to do. OTOH, nothing prevents a registration from including
> > "additional"
> > additional information, nor is a registration precluded from omitting
> > any or
> > all of the additional information fields.

> That’s pretty clear and it seems like, such an actualisation is
> probably useful to at least give a hint that clipboard types may be
> relevant.

> > So the value of formally adding the fields would be if it gets people
> > to
> > list them when they wouldn't otherwise. Given past experience I'm
> > skeptical
> > this will happen.

> Well, on this, I think it does depend a lot on the type.
> Sometimes it makes no sense (to all or to some) to make consider put
> this into a clipboard (e.g. because a selection does not make sense) and
> for these, the authors will simply ignore it. At least, it seems to me
> that clipboard type names make more sense than Macintosh 4-letter codes.

It's not a question of what makes sense, it's a question of the information
people have available and thus what they are able and willing to put in a
registration.

Past experience says people are unlikely to go the extra mile to think
about any of this stuff even if we prompt them for it.

				Ned