[dispatch] IANA Registry for parameters for the MIME header field "Content-Type" ?

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Tue, 18 April 2023 20:50 UTC

Return-Path: <dkg@fifthhorseman.net>
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 B6570C1516E2 for <dispatch@ietfa.amsl.com>; Tue, 18 Apr 2023 13:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.303
X-Spam-Level:
X-Spam-Status: No, score=-1.303 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_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b="L1e3S30w"; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b="alO2YhSy"
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 AVeygkjTShh8 for <dispatch@ietfa.amsl.com>; Tue, 18 Apr 2023 13:50:52 -0700 (PDT)
Received: from che.mayfirst.org (unknown [162.247.75.117]) (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 8F5E1C151530 for <dispatch@ietf.org>; Tue, 18 Apr 2023 13:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1681851049; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=1puya25qiB5STJywZxaG68OhbcnHUAhbTOblVAvABu8=; b=L1e3S30w+8qEw3xQje5aFG42+DtH5Tla/nbgniO8ueZqgIdwMI2Nmg6KbdhxHC+85vhrN kK1NzeiQmKmnRFKAA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1681851049; h=from : to : subject : date : message-id : mime-version : content-type : from; bh=1puya25qiB5STJywZxaG68OhbcnHUAhbTOblVAvABu8=; b=alO2YhSycSOF9y8gk/4vZ4GlmyK0uCWR7DuAMc1o3p7W/f6W2V9OSWObQG0c0lQRwIGZf O782PhMUHv7n7C0mmvMzWX+AkmHC2dOCXOrga8xzXRwWOTH3dIgRZs99B72NX5+QbErcrTD pYl0vJgT6t24YgAr7LiSRpT+5aA31Zpfhq5JfeEL0UMgcjpFI0FxJ96MBICIWG0A9nddceg EjtlOxtkithqWzF0WrJ3K1RJ0kr+Bqbq3jY5VnugGsEtQvtAB43UuIpXO7FAZHSC1y4jNn7 47GyuGalHVCoxUoPKNXSoJMfZBGK+OyG7zavne+14Jfgfy/ZUR90kDZODpNg==
Received: from fifthhorseman.net (unknown [38.109.115.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id EFC91F9AE for <dispatch@ietf.org>; Tue, 18 Apr 2023 16:50:48 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id CDE8E20967; Tue, 18 Apr 2023 16:50:45 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: dispatch@ietf.org
Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEX+i03xYJKwYBBAHaRw8BAQdACA4xvL/xI5dHedcnkfViyq84doe8zFRid9jW7CC9XBiI0QQf FgoAgwWCX+i03wWJBZ+mAAMLCQcJEOCS6zpcoQ26RxQAAAAAAB4AIHNhbHRAbm90YXRpb25zLnNl cXVvaWEtcGdwLm9yZ/tr8E9NA10HvcAVlSxnox6z62KXCInWjZaiBIlgX6O5AxUKCAKbAQIeARYh BMKfigwB81402BaqXOCS6zpcoQ26AADZHQD/Zx9nc3N2kj13AUsKMr/7zekBtgfSIGB3hRCU74Su G44A/34Yp6IAkndewLxb1WdRSokycnaCVyrk0nb4imeAYyoPtBc8ZGtnQGZpZnRoaG9yc2VtYW4u bmV0PojRBBMWCgCDBYJf6LTfBYkFn6YAAwsJBwkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3Rh dGlvbnMuc2VxdW9pYS1wZ3Aub3JnL0Gwxvypz2tu1IPG+yu1zPjkiZwpscsitwrVvzN3bbADFQoI ApsBAh4BFiEEwp+KDAHzXjTYFqpc4JLrOlyhDboAAPkXAP0Z29z7jW+YzLzPTQML4EQLMbkHOfU4 +s+ki81Czt0WqgD/SJ8RyrqDCtEP8+E4ZSR01ysKqh+MUAsTaJlzZjehiQ24MwRf6LTfFgkrBgEE AdpHDwEBB0DkKHOW2kmqfAK461+acQ49gc2Z6VoXMChRqobGP0ubb4kBiAQYFgoBOgWCX+i03wWJ BZ+mAAkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3Jnfvo+ nHoxDwaLaJD8XZuXiaqBNZtIGXIypF1udBBRoc0CmwICHgG+oAQZFgoAbwWCX+i03wkQPp1xc3He VlxHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3JnaheiqE7Pfi3Atb3GGTw+ jFcBGOaobgzEJrhEuFpXREEWIQQttUkcnfDcj0MoY88+nXFzcd5WXAAAvrsBAIJ5sBg8Udocv25N stN/zWOiYpnjjvOjVMLH4fV3pWE1AP9T6hzHz7hRnAA8d01vqoxOlQ3O6cb/kFYAjqx3oMXSBhYh BMKfigwB81402BaqXOCS6zpcoQ26AADX7gD/b83VObe14xrNP8xcltRrBZF5OE1rQSPkMNy+eWpk eCwA/1hxiS8ZxL5/elNjXiWuHXEvUGnRoVj745Vl48sZPVYMuDgEX+i03xIKKwYBBAGXVQEFAQEH QIGex1WZbH6xhUBve5mblScGYU+Y8QJOomXH+rr5tMsMAwEICYjJBBgWCgB7BYJf6LTfBYkFn6YA CRDgkus6XKENukcUAAAAAAAeACBzYWx0QG5vdGF0aW9ucy5zZXF1b2lhLXBncC5vcmcEAx9vTD3b J0SXkhvcRcCr6uIDJwic3KFKxkH1m4QW0QKbDAIeARYhBMKfigwB81402BaqXOCS6zpcoQ26AAAX mwD8CWmukxwskU82RZLMk5fm1wCgMB5z8dA50KLw3rgsCykBAKg1w/Y7XpBS3SlXEegIg1K1e6dR fRxL7Z37WZXoH8AH
Date: Tue, 18 Apr 2023 16:50:44 -0400
Message-ID: <87ildssymz.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/sp3BRhQbfo205HxIfbGXzxE9hzY>
Subject: [dispatch] IANA Registry for parameters for the MIME header field "Content-Type" ?
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 18 Apr 2023 20:50:56 -0000

Hey IETF folks--

While polishing draft-ietf-lamps-header-protection, i noticed that there
is no IANA registry for parameters for the Content-Type MIME header
field.

Some of these are pretty common, like "boundary" (for distinguishing
subparts of any multipart MIME part) and "charset" (for identifying the
encoding used in a text part), and others are more obscure.

Scanning a reasonably large mail corpus, i found a range of parameters
used:

  - boundary
  - charset
  - delsp
  - format
  - markup
  - micalg
  - name
  - protected-headers
  - protocol
  - reply-type
  - report-type
  - smime-type
  - type

I note that there are also some comparably-structured "parameter" fields
for the Content-Disposition header (e.g. "filename"), though i doubt
that there are so many as there are for Content-Type.

It seems like it might be worthwhile to try to establish a registry for
these parameters (at least for Content-Type, so that there is at least a
stable reference that can be used by a MUA that wants to handle the
parts appropriately..

Any thoughts about the right place to do this work on e-mail in the
IETF?

        --dkg

PS to be clear, it is not the intent of this message to:

 - create any new document dependency that might block
   draft-ietf-lamps-protected-headers

 - define any new parameters for Content-Type