IETF Logo Mail Archive

Re: [media-types] Thoughts on suffixes, single and multiple

Mark Nottingham <mnot@mnot.net> Mon, 08 April 2024 02:15 UTC

Return-Path: <mnot@mnot.net>
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 DA18FC14F60A for <media-types@ietfa.amsl.com>; Sun, 7 Apr 2024 19:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="TLjnn2kQ"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="uN5JldPu"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrzPG6QWFHgU for <media-types@ietfa.amsl.com>; Sun, 7 Apr 2024 19:15:20 -0700 (PDT)
Received: from fout4-smtp.messagingengine.com (fout4-smtp.messagingengine.com [103.168.172.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE757C14F5F8 for <media-types@ietf.org>; Sun, 7 Apr 2024 19:15:20 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 4ADB91380078; Sun, 7 Apr 2024 22:15:19 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 07 Apr 2024 22:15:19 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1712542519; x=1712628919; bh=Ze1QnzvhCX1tI6oJF3ohVWFajgUD+W7Vh2iSRz+pFy4=; b= TLjnn2kQ5fES1uvlzqFvFXiiytVv6Zqv1ubL/uo3SSs/WoXVAqBuYTDPPLYEt39E t6C11evUj81VoV9ETu9faV86E/F2uz3jxYu+Hg/J4weF59vSCkS39owBnmDJOXvN WCGPW76NbEeKfhILE8Fz2u5uRBhJVKvY2gKTj8kmklviMLalIkxTt40krnoXbm9U E1P9d5uOcWbIOnvvgeXyFS0lZF1pXvG7/KISBIy9Q0cVuBv1FIj1G8EEFLA3UK1d 2VVkcaM2Skema3Lng8c95eRNGwqVOfdXRCU1vftNFYcoM9H8l1SWJOulqYkzXoZx sVj1pJ28vfHV8hS3sGxEOg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1712542519; x= 1712628919; bh=Ze1QnzvhCX1tI6oJF3ohVWFajgUD+W7Vh2iSRz+pFy4=; b=u N5JldPu1mvSImEN6OwE5oJMmrqOkGtq2uGWr0rHAmrHHBUEXUSTJmcbFZ2I7uDEa cjvkbXq6SvM19PqMTpo0wANBFQTdccu521rykJD+JkXr2AktAxLuB82+K65XokEZ x0GWTjvT1bkOoWzl9xAUVjunfdsEE6hCbOlaFnfpRV6j3sveRCAiYhQI+xaR320Y DbOsYRZVTfKN9g/71cQ6TaW9CPUxpgzcbv5b0NiCYat3H3330114K9fm1y1/xfKZ 0Et/+Y9hWRUn16RnBgdDIq4aCRquXaX+62YKc7jyjdvpN0CbHuFP/wwb/RzRp/tG BNKLIKCWCUg4Ph0xfAXaA==
X-ME-Sender: <xms:NlMTZh7r5MZYTahzvE-xXZmnnEqsM01-Z_qJo97grkTSzA9Z6ntjZA> <xme:NlMTZu4rU2YiOZI7DZ9bXb0dXzbx0dScivrWes4xDQPdkBhi6gwb0ncywYF-F7RUL 5BX5Pn2b-RcMDtgZQ>
X-ME-Received: <xmr:NlMTZofgqSWPPB6JRRhhD5ZPtvaWWdBqdjO-n0Xp6WJ-vzQ4HcUp9Uv1SrppraWIhZWV>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudeghedgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffvefgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnheptddtgefgueevtddugfdtkeffudegveetffegjeelhfdvtedvueejteegueeg teetnecuffhomhgrihhnpehmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:NlMTZqJPZfztd-8iUkVmppotE96mT_Z3KjMvaR2l2CZgp3UmBBKWgQ> <xmx:NlMTZlI4Sp4j-FxtJvh8APkvPo0tKFGQqMWEOtHRFPtGsLKT-87Hfw> <xmx:NlMTZjxDspxUvvNqtqJsqHKuwKoAsgbIrj7T6Q4J9dmiI-x0br0fNg> <xmx:NlMTZhIaPFa61V4S6BynAj5fOhC_2nDyoeLQx05xxnRzWLk8--5RNQ> <xmx:N1MTZl1UEcwtE4LTfPMWT2QAh1B0y3O7_BffzP9mXJgAHwRqrZBvNr1L>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 7 Apr 2024 22:15:17 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAMBN2CT0qaYFqp1gMUZsBxepxZ=nzpKbAW+cAhHyHdASZHupgA@mail.gmail.com>
Date: Mon, 08 Apr 2024 11:15:12 +0900
Cc: IETF Media Types <media-types@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <25A01CF2-7529-4E8B-9B80-116D4C6FB4E9@mnot.net>
References: <2E20FEDE-C766-43EE-A6E2-1FB63E79CF0B@mnot.net> <1c404c4d-437c-464a-b414-4e0d39c1d8ea@alvestrand.no> <E83E80FF-5810-4A53-85D8-E5095F9C1C1C@openlinksw.com> <837B503B-B9F9-40F7-8078-7D1BCD66D076@mnot.net> <CAMBN2CTMk8GDeUT0ObHcW=xxaRMzd75PrtWwLa_YB-4JoF_FxA@mail.gmail.com> <F58ABF0E-56F3-462B-AA00-192A75AFEE41@mnot.net> <CAMBN2CSbxjX8GCi2E1gTwnaWNLvbNc7SWd=mStWDnj0eeZpgpQ@mail.gmail.com> <C2B4B44B-1282-4818-9B49-01E6B67593E0@mnot.net> <CAMBN2CT0qaYFqp1gMUZsBxepxZ=nzpKbAW+cAhHyHdASZHupgA@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/dDqqF1ErSoL1TE_guN-rEXOo66c>
Subject: Re: [media-types] Thoughts on suffixes, single and multiple
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 08 Apr 2024 02:15:25 -0000


> On 7 Apr 2024, at 11:26, Manu Sporny <msporny@digitalbazaar.com> wrote:
> 
>> What we need to sort out now, I think, is what implications this has for the multiple suffixes draft. I tend to think that it supports the 'bag of tags' approach that I outlined earlier; that puts the fewest constraints on how suffixes are defined (so that they can define their own constraints, as per above).
> 
> I'm not fully following, but I think you're saying that "the suffix to
> the left needs to say how it serializes itself to the the suffix to
> the right"? Or you might be saying "if you peel the suffix to the
> right off, everything to the left needs to be a valid media type"?

No - what I'm saying is that whatever we put into the multiple suffixes draft, it should be extremely generic, so that it can accommodate all of these different uses. I think that means:

- No requirement to register combinations of suffixes; only each individual suffix is required to be registered
- No default constraints on how suffixes are composed / how they relate to each other / what the semantics of their ordering or position means

Does that make sense? I could see an argument for still requiring combinations of suffixes to be registered, but am hoping that if we do a good job on describing the individual suffix constraints, that won't be necessary.

Cheers,


--
Mark Nottingham   https://www.mnot.net/

v2.23.0 | Report a Bug | By Email