IETF Logo Mail Archive

Re: [dispatch] Zstandard compression

Mark Nottingham <mnot@mnot.net> Wed, 01 November 2017 23:44 UTC

Return-Path: <mnot@mnot.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 9001913F6D3 for <dispatch@ietfa.amsl.com>; Wed, 1 Nov 2017 16:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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=oedATDpt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WhDzNfCQ
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 jKUZJW0_ptBN for <dispatch@ietfa.amsl.com>; Wed, 1 Nov 2017 16:44:06 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04EF4138BD6 for <dispatch@ietf.org>; Wed, 1 Nov 2017 16:44:05 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5EF41208D8; Wed, 1 Nov 2017 19:44:05 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 01 Nov 2017 19:44:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=khrJTbLXvilAIuoNC1vrIMKobcN1J bUcRoZVrR3qXZU=; b=oedATDpt31Fq6ZljlZycf3Ogvgs6tyrMf3Xg35Kj3hnat pU0ymc71LsN4Kng20YqwOeoivCPY+FbXUldc77v8XNz7ZdgOEw4zKJTb35fqHzDb 7Vt/faxAkvEMr4CJpdO99q24+itKQtUiiSZRFCVFMuMl5yKcYg/hvR+m1mzx1ade da1v8HN+OfGHTmzjtFUX8w+Jz5F/+ew7m3iiz6k04WXz108yJkZZgKpyeCAMk7AA ggvrzuqj1otmipseL8DwIMxWIW+90fdF2ZUC8qCKRikkWGsbvBgMD5S1U6GXAzc6 2OrK5qpmQKn7766cH2LD92BjA7myJhgmZNdbbVVEA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=khrJTb LXvilAIuoNC1vrIMKobcN1JbUcRoZVrR3qXZU=; b=WhDzNfCQqyUKloAXAyZcGh eEUIPesEpL/DdSuaGhgeLrOvK9S4gh0SoorMFjgdpqVYrl9oji+5/G4zKVb5Vos2 vw8HiSb2M8OnN5jJ6PiNe+ECMrW4UXWODWI76Km4V+ALbZBjJJR+PQOwF+tJk/Pj xpzCNmy6H55nGi9tYTVhD/LkzOvk9YjbP6OCsEL2vGQHbIgHvBd+yupWdYpB4ZH2 L3/Sy0Mw/syeCbwCRVgTniaZe1ANSP7wldoD+HXioQoDkYjPcovQ2rUBp4rsybzL GUnDx6HAohYl8rLdrK5RMUsWbkoo2o5kx/wHk5JkZHUpFCkNyr+VHGltnrT2Un5A ==
X-ME-Sender: <xms:RVz6WapSDbdNWS-XgNiW37y8SSsG8lbLhIevXLuT5fP9JA5tgqqrCg>
Received: from [192.168.1.18] (cpe-124-188-19-231.hdbq1.win.bigpond.net.au [124.188.19.231]) by mail.messagingengine.com (Postfix) with ESMTPA id 3C0737FA8C; Wed, 1 Nov 2017 19:44:04 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CABkgnnURFCsrodz21EhuPZox5jwQq=dC28erMibYQtH+_E1rbA@mail.gmail.com>
Date: Thu, 02 Nov 2017 10:44:00 +1100
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, DISPATCH list <dispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2864909A-0B02-44F1-91BB-181CC687871F@mnot.net>
References: <CAL0qLwatePp87tC6YGRj4=K0xivMfSr2QSDkn6VVkojvs4DW7A@mail.gmail.com> <22EAF7AB-E6AB-44C5-A424-EF0AF2313EC6@mnot.net> <CABkgnnURFCsrodz21EhuPZox5jwQq=dC28erMibYQtH+_E1rbA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3445.1.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/SvFgDx5A2rrn-Y24WDJVhb1ONo0>
Subject: Re: [dispatch] Zstandard compression
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 01 Nov 2017 23:44:08 -0000

My .02 - I don't know that Brotli is a shining beacon of how things should be done here; I don't see any instrinc problem with registering the appropriate identifiers in the same document -- as long as appropriate consultation takes place.

Cheers,


> On 2 Nov 2017, at 10:32 am, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> I think that the right approach here is to approach this similarly
> cryptographic algorithms.  It seems like the basic compression
> structure is independently useful.  Document the format in one place,
> then have short documents that describe content codings and other
> things independently.  Then HTTP can take the content-coding work on
> at their discretion (or it can progress independently).
> 
> I realize that RFC 7932 (brotli) didn't do this, so it would be OK to
> just follow that pattern.  It also didn't define a media type. Did you
> have a use case in mind for that?
> 
> On Thu, Nov 2, 2017 at 9:40 AM, Mark Nottingham <mnot@mnot.net> wrote:
>> To be clear - HTTPbis needs a heads up and might want to have discuss the registration of the content-coding (Section 3.2). The whole spec probably belongs elsewhere.
>> 
>> Cheers,
>> 
>> 
>>> On 2 Nov 2017, at 8:35 am, Murray S. Kucherawy <superuser@gmail.com> wrote:
>>> 
>>> <chair hat clearly off>
>>> 
>>> In September, I submitted draft-kucherawy-dispatch-zstd, which introduces a new compression  mechanism and seeks to register media types and content encodings for it.  The most obvious application for it is HTTP payloads, but it has other possible applications.
>>> 
>>> I don't know of IETF venues other than this one and maybe the ART list where this kind of thing might be discussed, or how we might dispatch it.  Offlist conversation with Mark Nottingham suggested maybe HTTPBIS might like to at least discuss this, but I haven't looked to see if it fits within their current charter.
>>> 
>>> Suggestions for discussion venues or processing options are welcome.
>>> 
>>> -MSK
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dispatch
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch

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

v2.23.0 | Report a Bug | By Email