Re: JPEG-XL as Content-Encoding?

Poul-Henning Kamp <phk@phk.freebsd.dk> Sun, 23 August 2020 22:04 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1CD53A0EA2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 23 Aug 2020 15:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.75
X-Spam-Level:
X-Spam-Status: No, score=-0.75 tagged_above=-999 required=5 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9GkPSPca-Ms5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 23 Aug 2020 15:04:41 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (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 3EE283A0EA3 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 23 Aug 2020 15:04:40 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1k9y3A-0005zv-Ua for ietf-http-wg-dist@listhub.w3.org; Sun, 23 Aug 2020 22:01:17 +0000
Resent-Date: Sun, 23 Aug 2020 22:01:16 +0000
Resent-Message-Id: <E1k9y3A-0005zv-Ua@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <phk@critter.freebsd.dk>) id 1k9y36-0005z4-IS for ietf-http-wg@listhub.w3.org; Sun, 23 Aug 2020 22:01:12 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <phk@critter.freebsd.dk>) id 1k9y33-0001VN-OU for ietf-http-wg@w3.org; Sun, 23 Aug 2020 22:01:12 +0000
Received: from critter.freebsd.dk (unknown [192.168.55.3]) (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 phk.freebsd.dk (Postfix) with ESMTPS id B02461AF211; Sun, 23 Aug 2020 22:00:56 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.16.1/8.16.1) with ESMTPS id 07NM0ueG099302 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 23 Aug 2020 22:00:56 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost) by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 07NM0s8D099299; Sun, 23 Aug 2020 22:00:54 GMT (envelope-from phk)
To: Alex Deymo <deymo@google.com>
cc: Sergey Ponomarev <stokito@gmail.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <CAGd9gwhFQPzULNrAnnpeWBLCX+0aZGa0xMVO-u+fwvJ6AfaJEg@mail.gmail.com>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <CACj=BEjdwH1OtS=uQXsgPN3XVJvVEUeisjeF5_iro1vg0omqWQ@mail.gmail.com> <20200820151401.GB21689@1wt.eu> <20200820183008.GA8086@lubuntu> <18159.1597960275@critter.freebsd.dk> <CADR0UcWkxb4ZtMgjqDeAv=m6G3ks2P75L-5pvt-ctz8WyJF29g@mail.gmail.com> <CAGd9gwhFQPzULNrAnnpeWBLCX+0aZGa0xMVO-u+fwvJ6AfaJEg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <99297.1598220054.1@critter.freebsd.dk>
Date: Sun, 23 Aug 2020 22:00:54 +0000
Message-ID: <99298.1598220054@critter.freebsd.dk>
Received-SPF: pass client-ip=130.225.244.222; envelope-from=phk@critter.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1k9y33-0001VN-OU 85ce3029ba679d9d1505ddb48c36e37e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: JPEG-XL as Content-Encoding?
Archived-At: <https://www.w3.org/mid/99298.1598220054@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37954
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

--------
Alex Deymo writes:

> I'm Alex and I'm working in the JPEG XL project. The transcoding being
> discussed for this is indeed the lossless recompression of JPEG files
> feature in JXL.
>
> JXL has many more features as a codec than what the lossless JPEG
> recompression can offer [...]

I'm sure JXL is fantastic, but despite that, a special-case
(re)compression belongs in the application-layer, not in the
transport layer.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.