Re: [media-types] HTTP replying with what clients don't support (Re: Last tracker issue for mediaman-suffixes)

Martin Thomson <mt@lowentropy.net> Wed, 20 March 2024 03:29 UTC

Return-Path: <mt@lowentropy.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 0F7E8C14F680 for <media-types@ietfa.amsl.com>; Tue, 19 Mar 2024 20:29:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=lowentropy.net header.b="v+99flxz"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="Yz+sOppR"
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 T8apKN6SiSIL for <media-types@ietfa.amsl.com>; Tue, 19 Mar 2024 20:29:31 -0700 (PDT)
Received: from wfhigh3-smtp.messagingengine.com (wfhigh3-smtp.messagingengine.com [64.147.123.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2405FC180B63 for <media-types@ietf.org>; Tue, 19 Mar 2024 20:29:09 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id E697118000F4; Tue, 19 Mar 2024 23:29:06 -0400 (EDT)
Received: from imap41 ([10.202.2.91]) by compute6.internal (MEProxy); Tue, 19 Mar 2024 23:29:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=cc:cc: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=1710905346; x= 1710991746; bh=DfI0kSxAI3uGLCgntHvBsu15jxiZKCyqqL/3Fl2ZBeY=; b=v +99flxzfrTJJUqHyhl4uVBsMnJvR8m33w0L9CuOdjxuBU9K6fdZ71Mo5rxu/l5cJ ysf0U/HtZfdSD2UkfZbZAmBUmt6v0M+8pwckj7caB2na8MvJCSA7h0xZwB6/0Peg IXFXZ8CEnk04HgsAN3i0xHg7+0QuaUJhmCGa7Tz5eMJKKf9SIpKljC551x3Z4RcV 9wuBSCQsdvmcWiSVyYB8nWo6S6fSAeGTIBxVK7g6X6arzykNdNQGf8G43WqE74T+ dNYTbV6r/qujZs0qux6/hD3na0dtGCNijInwokeRKtp2jjaQ4jtcOOr9xkdMf7kO Xv+IhPU4qN5OnGEXSa5Hw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc: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=1710905346; x=1710991746; bh=DfI0kSxAI3uGLCgntHvBsu15jxiZ KCyqqL/3Fl2ZBeY=; b=Yz+sOppRh+96K3ksvSulCSSsDYRZb983B7zETYpldyVi jx7E60vNiwcgb82xiKZ5ldqyxzop61RtXY83toDbKhPHpXBzcaie+XDuHu0sp9J2 eVJhfEp0P5Ev0up+bqrlBhGrPqOqPrrmlGcmobT8tIQGhQZD4JtIooSJEI8xCd8q AuF8f1m2zael9i8Hqq9F11joO/sZleNYEXwY5bEnAF0C9DXE46Q6WRXcKonDiZDp hu0CqPK33/CbMYgWK/dFqzrTIkvRRFfu4uSw0ZlCtJwiRA3j3T1Dg/oDQfaUrpgR PUXl12Vmo4GLJ4i1ytafUl1RmUj+E2+YIPdyUsKh8g==
X-ME-Sender: <xms:Alj6ZRRSK2Et8bKIcXyqdTeLlLxWscBeTfGmx1zolB0_DKJgNTATtQ> <xme:Alj6ZawGlpWBnGON7zHqtzuCb-jwfqc2xr-8Ls8XRJXZAfnShSJqfGZZEoQIDyuom Y-rpKtoiE_Df9Mzgyk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrleefgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvvefutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepudelueeftdfhgeeiieeikeekjedvjefgveduffegfedvffelveef keduieeikeelnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:Alj6ZW23z8DXE-Hi-Qo8L0KZ52pUXUkgNfscTg_zNf3Vcec5cGxUYA> <xmx:Alj6ZZBznJr2QgqRa04gWJsn-A27fyKGnP9p0sq8aFPGspil3iFDpw> <xmx:Alj6ZahYdAm7AhwOsdkkWcoPmEFyK_hIQfgKEEsK36M9TpLjK1-Xjg> <xmx:Alj6ZdpL93n14a-5wubrcZH7jrSVzp7pvJqXBMzVkQU126ENw12svw> <xmx:Alj6ZTVVP8n8ua0aaUlyUUQZ3nq-PzAl7nOUB2MwwVxXiPV0-j0uoZpb_4E>
Feedback-ID: ic129442d:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 121472340080; Tue, 19 Mar 2024 23:29:06 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-332-gdeb4194079-fm-20240319.002-gdeb41940
MIME-Version: 1.0
Message-Id: <a596e2ac-a252-4e9e-9168-3fe215aa9a91@app.fastmail.com>
In-Reply-To: <ed01e7f9-49a5-46f3-b0e9-f9f516f55f98@alvestrand.no>
References: <CAMBN2CQbfAW2pmmxZZgbBOTUzY+TdYe5S8ve5cX_R30PXZJ=+w@mail.gmail.com> <CAN8C-_JGre8jtAenDCrV7JSwJWPhf9K7K6HiC4_cX6E+YLru+Q@mail.gmail.com> <CAMBN2CQy6GzJiZvU2fkvrDSLGpk=K-HUxv1Gwd8cDxEhjojtHw@mail.gmail.com> <PH0PR02MB7430A03285ECC49CADF584FAB7232@PH0PR02MB7430.namprd02.prod.outlook.com> <68739467-3819-4D6C-81F4-17AFE3D0A3E9@tzi.org> <CAMBN2CQVKmc9=hmm+rK2wK4aNVJfR_YDMEYUQJadzUiZCVTCkA@mail.gmail.com> <39D0F672-53F7-4AE6-8FCE-B0CA18355E05@tzi.org> <CAN8C-_K5EvziAE6h4AMnLtmFsfdNxi=ar16pzWZzfaj9cGBAtA@mail.gmail.com> <ed01e7f9-49a5-46f3-b0e9-f9f516f55f98@alvestrand.no>
Date: Wed, 20 Mar 2024 13:28:45 +1000
From: Martin Thomson <mt@lowentropy.net>
To: Harald Alvestrand <harald@alvestrand.no>, Orie Steele <orie@transmute.industries>, Carsten Bormann <cabo@tzi.org>
Cc: Manu Sporny <msporny@digitalbazaar.com>, Michael Jones <michael_b_jones@hotmail.com>, IETF Media Types <media-types@ietf.org>, Darrel Miller <darrel@tavis.ca>, Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/YJ86O2tRkEjN0hR2NHV_E4j4_xc>
Subject: Re: [media-types] HTTP replying with what clients don't support (Re: Last tracker issue for mediaman-suffixes)
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: Wed, 20 Mar 2024 03:29:36 -0000

On Wed, Mar 20, 2024, at 13:27, Harald Alvestrand wrote:
> This, as I understand it, is a HTTP violation no matter how I hold it: 
> the server is responding with a media type that the client has said that 
> it did not support.

Content negotiation can be ignored.  This is not a violation of the protocol.  The response might not be useful, but it is valid.