Re: [dispatch] Zstandard compression

On 11/13/2017 10:25 AM, Martin J. Dürst wrote:
> On 2017/11/13 15:18, Murray S. Kucherawy wrote:
>> On Mon, Nov 13, 2017 at 2:01 PM, Sean Leonard <dev+ietf@seantek.com>
>> wrote:
>
>>> Working on this. It strikes me as either…odd…or just not really that
>>> useful for the purpose. It is a format, but it’s just a format for a
>>> stream
>>> of arbitrary bytes. There is no way to label it internally beyond the
>>> implicit “application/octet-stream” type.
>>>
>>
>> Don't you need a hint as to how to decode an octet stream that's
>> encoded in
>> some way?
>
> Yes. But I think what Sean is saying is that above and beyond that,
> you'd (in many if not most use cases) also want to know what the
> decoded octet stream is about. Otherwise, this information has to be
> transmitted on a side channel.

One (horribly ugly) way of doing this is to have something like a
"contains" parameter:

mime-type: application/zstandard; contains="text/plain; charset=utf-8"

That's one form of side channel for passing the data around. Not sure if
anyone would use it.
But it's such an ugly way of doing things that it should definitely be
suggested on the media-types list, not here.

>
> Regards,    Martin.
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

-- 
Surveillance is pervasive. Go Dark.