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

Ned Freed <ned.freed@mrochek.com> Sun, 21 October 2018 14:57 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 18C801292AD for <media-types@ietfa.amsl.com>; Sun, 21 Oct 2018 07:57:17 -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 ID6drBjCJv_6 for <media-types@ietfa.amsl.com>; Sun, 21 Oct 2018 07:57:15 -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 BEE02127333 for <media-types@ietf.org>; Sun, 21 Oct 2018 07:57:15 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QYP2UH49TS00FI5W@mauve.mrochek.com> for media-types@ietf.org; Sun, 21 Oct 2018 07:52:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1540133531; bh=bonbwyIBvPnJEvvBHqW5m2/i+Q46FI8UoJXh8cS4GOQ=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=Y9vgixCojM36NUkIa9C3OQCGN0b7rbWIYiNq/ZAe8gt/z4uLHJ0l0G3IWz0qc6qdI fmwhi8Hqk6biDgJR+zbR9ZbrW8fBmofnWgpgEYjz2peG+yW/9Qu1HpXdWtITMN8XCU JyXudjLN7OWG8q0wc8Hq6sn6+hgK2VXySRF8JEm8=
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 <01QYM8BK7VLS00BGSX@mauve.mrochek.com>; Sun, 21 Oct 2018 07:52:07 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, Paul Libbrecht <paul@hoplahup.net>, media-types@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, Chris Lilley <chris@w3.org>
Message-id: <01QYP2UEXT9E00BGSX@mauve.mrochek.com>
Date: Sun, 21 Oct 2018 07:48:37 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 21 Oct 2018 00:43:16 -0400" <20181021044314.GA15061@w3.org>
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> <01QYNOB5YLQS00BGSX@mauve.mrochek.com> <20181021044314.GA15061@w3.org>
To: Eric Prud'hommeaux <eric@w3.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/HL6hqZhhaxtE9F5HdMysBDwYTlI>
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: Sun, 21 Oct 2018 14:57:17 -0000

> Speaking from experience, it occurs to almost no one to think about a
> clipboard type name and then wedge it into an unreceptive form. I
> believe that the folks who fill these out are pretty diligent.

Some are. Many are not.

Having seen every registration that has come in for the past 10+ year, I
speak with some authority here.

> Clearly
> marking optional fields as such and providing links to understand,
> e.g. clipboard type names, allows said diligent netizens to leave less
> interop to chance, which is why they're filling out the form in the
> first place.

Again, I have no objection to adding such fields if people want to spend
the time to do so. However, my skepticism as to their utility remains.

				Ned