Re: [media-types] WG Review: Media Type Maintenance (mediaman)

Ned Freed <ned.freed@mrochek.com> Sun, 11 July 2021 22:00 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 0AAC23A2012; Sun, 11 Jul 2021 15:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.774
X-Spam-Level:
X-Spam-Status: No, score=0.774 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=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 DhKVX7__Su9I; Sun, 11 Jul 2021 15:00:01 -0700 (PDT)
Received: from plum.mrochek.com (bang.mrochek.com [98.153.82.210]) (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 74DD53A2011; Sun, 11 Jul 2021 15:00:01 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01S1A39YTF9S00IYMH@mauve.mrochek.com>; Sun, 11 Jul 2021 14:54:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1626040497; bh=5gD8u2B2XrlnMFTSXpTAxAzwiv9X83BguSQShURVjdM=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=JDGvfn7Sra43NIz8bKZWnot3FRb3pBPhcn9PeA7/gjwC2vqFRFlS+1AJaKv62WWKd lVtCLMqQbrpvmuS102ilbhfB5u07nvt2dMd8sKgVSbgUIEekc6ksx6bbm06vkduh/P qCwf9ELBfRUTSqXAaNJyz5dVln76j5o8HCiuPOuU=
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>; Sun, 11 Jul 2021 14:54:54 -0700 (PDT)
Cc: 'Alexey Melnikov' <alexey.melnikov@isode.com>, 'Ned Freed' <ned.freed@mrochek.com>, 'tom petch' <daedulus@btconnect.com>, media-types@ietf.org, iesg@ietf.org
Message-id: <01S1A39WZ8FI005PTU@mauve.mrochek.com>
Date: Sun, 11 Jul 2021 14:36:36 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 11 Jul 2021 13:53:40 -0700" <02e501d77696$d4d638e0$7e82aaa0$@acm.org>
References: <162524837970.13959.12407245450350054423@ietfa.amsl.com> <60E21648.3090107@btconnect.com> <01S10C1K8HZ2005PTU@mauve.mrochek.com> <9c017cb1-e81a-dad4-d2e5-c2f706471084@isode.com> <02e501d77696$d4d638e0$7e82aaa0$@acm.org>
To: Larry Masinter <LMM@acm.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/K7vc2HJYBUuCfvp-4fHZBHX4OQg>
Subject: Re: [media-types] WG Review: Media Type Maintenance (mediaman)
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, 11 Jul 2021 22:00:06 -0000

> I wrote an ID about MIME and web updates (in 2011):

> https://www.ietf.org/archive/id/draft-masinter-mime-web-info-02.txt

There's a lot here, but the only thing that seems relevant to this
effort is section 5.3:

   Problem: Internet Media Type registries are hard to update, and there
   can be different definitions of the same MIME type.

   STRAWMAN: Allow commenting or easier update; not all Internet Media
   Type owners need or have all the information the internet needs.
   Wiki for Internet Media Types as well as formal registry?  Ability to
   add comments about deployed senders, deployed content, deployed
   recievers.

First, the process to update a registration is the owner sends in an update.
For whatever reason we went a long time with few if any updates, but the rate
now seems to be increasing.

I can't recall a case where an update was difficult to deal with or ended up
being rejected. There have been occasional blips regarding ownership, but
again, I can't recall a case where a resolution was difficult to reach.

tl;dr I remain to be convinced that there's a problem to solve here.

As for comments, I don't have any problem with offering such a service, but I'm
skeptical that the desire to comment (in a constructive way) on media types is
sufficiently widespread that it would be useful.

> I'd hoped also to review MIME Multipart for more modern uses (shades of WPACK)
> https://mailarchive.ietf.org/arch/msg/wpack/EixjYebQDTdbcDS6FsE0eZye4ds/

> although they haven't taken up my suggestion. Perhaps mediaman could take up
> such review?

I'm sorry, but I *really* don't see the point. The advantages of multipart are
simplicity and fallback behavior. You lose both of those big-time with WPACK,
leaving you with just another way to package stuff. And like it or not, ZIP
seems to have won that battle.

				Ned