Re: [dispatch] Zstandard compression

"Murray S. Kucherawy" <> Mon, 13 November 2017 03:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 11224126DCA for <>; Sun, 12 Nov 2017 19:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vfmAtHZyZY9i for <>; Sun, 12 Nov 2017 19:22:15 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6C50F1293E0 for <>; Sun, 12 Nov 2017 19:22:15 -0800 (PST)
Received: by with SMTP id c36so11814109qtc.11 for <>; Sun, 12 Nov 2017 19:22:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kwVRUldIgAbqU100waqY76//t/VZjqbQifv7xDtuZCk=; b=MQSJM+bW8TXB2dLcAFOzpnNhPMyhqT4RJe86kGkF4Z2ylYgB9MWVUt9WiPnDfjwKzw YV4IDaQdOrpcOOBMPNwrPN6Hdugt7XTie1Hrxy3fFAbxdUz3PTxnJskt5euMeEuWyZZn v0R1bIp0Iv4vel0lB1KnBGLpy9j5lpbwXkFlqB4WKg9eJqwNgAQhQrboS+V+rHMDLR6I Lbh7Tx3dHS0BnlnfvJymzWmt3fnPaVd7VjwZXsYRZSgX1/f52K7MAFgpQ/s2Pskhn1ed L5lAtnj5ChmTBZf5A/cQCfwGR1bVLTmj9hICPYRHS2x8BpgM/u9JVYRiWnpSBnPZPb1d aPCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kwVRUldIgAbqU100waqY76//t/VZjqbQifv7xDtuZCk=; b=KShWCQLETE2AWteUXpP2f0/tw++D6WCOEGUMn9B4i/C9mr7xbzb7DEni9Ygops7C1v IDBbtLSzLV/6Un/Ax7IbDNL2yCP+n2B7x7hKBkD5/dG7IuVr8x7n61KxB0wv2DV0pwgu kFhnGUVRaH7Z89vv4uMjzk2rOU/sBOpRY0Kf7u+1LvqM9uCqFsxxFQyO/Xy8Hm+nsXc0 eyNagHex4ZPgeKWjt4oVpjDXI8se+gGY16BbJDU0T4/NPb1DZhWMGE46TAG03ZzFSOhJ PZzJX1hftAWo73YhHSYYaRwCYHnlqt8uPJuY0cujnijr/xYkUf/TtP9OIok+4s393Bax +cMg==
X-Gm-Message-State: AJaThX7mOm0GLRhFiecUZZbNr84JK9RTgNCd34FYzyZGPGrOe6rimM0T Rs8d4rqlYoWAKpp6tVkN9GEEHXqdK01tz+y0ug3JKg==
X-Google-Smtp-Source: AGs4zMY8DhcR1hXW7nN++qMe0w85MFaPfxkZmGDwsoahpE+6aOWdErBr//IPII2QJV9r4a0sxG1P1NTJhJPL4rBlOTs=
X-Received: by with SMTP id y14mr475844qta.84.1510543334505; Sun, 12 Nov 2017 19:22:14 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Sun, 12 Nov 2017 19:22:13 -0800 (PST)
In-Reply-To: <>
References: <> <>
From: "Murray S. Kucherawy" <>
Date: Mon, 13 Nov 2017 11:22:13 +0800
Message-ID: <>
To: Sean Leonard <>
Cc: DISPATCH list <>
Content-Type: multipart/alternative; boundary="001a113bef4cdf01c8055dd4c614"
Archived-At: <>
Subject: Re: [dispatch] Zstandard compression
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Nov 2017 03:22:17 -0000

On Mon, Nov 13, 2017 at 10:22 AM, Sean Leonard <> wrote:

> Those documents do not specify MIME types, and I do not think this
> document draft-kucherawy-dispatch-zstd should do so either. The media type
> registration is weak: there is no way to signal inside the format what is
> inside other than an arbitrary stream of bytes. It is not a file archive
> format, or another kind of container format that identifies parts.

Why does that imply that a media type is not appropriate?  A module
receiving this content for processing needs to know what format it's in,
and I believe that's what these are for.

I request that we get an OID registration for this for use with Compressed
> Data Content Type for CMS, RFC 3274. That way it could be used with S/MIME
> or other formats that use CMS or S/MIME (seeing as how CMS / S/MIME are
> general container formats).


Surveying other container formats and doing the appropriate registrations
> with them in this draft would be appropriate, if one can articulate a use
> case in those respective formats.

Can you suggest an example?