Re: [Cellar] On the multiplicity of Info elements

"Sebastian G. <bastik>" <bastik.public.mailinglist@gmx.de> Thu, 14 January 2016 17:54 UTC

Return-Path: <bastik.public.mailinglist@gmx.de>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21FBA1A6FEC for <cellar@ietfa.amsl.com>; Thu, 14 Jan 2016 09:54:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 B6ybKdoshMLr for <cellar@ietfa.amsl.com>; Thu, 14 Jan 2016 09:54:35 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C58481A6FE8 for <cellar@ietf.org>; Thu, 14 Jan 2016 09:54:34 -0800 (PST)
Received: from [192.168.2.129] ([188.100.175.162]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MHHZT-1aNKsV2rtT-00E3tX for <cellar@ietf.org>; Thu, 14 Jan 2016 18:54:32 +0100
To: cellar@ietf.org
References: <CAOXsMFLCbe-W=h+tQpdRa8Nh0jz=xdbZTXEmoXsgQTbA=4OPCQ@mail.gmail.com> <C0E5EBA2-2A56-46F9-A049-629EFB11F280@dericed.com> <CAOXsMF+gc0d2LEisfHm0jnjDGQKcYquEMBt7FnZ_uuSNF=C0iw@mail.gmail.com> <568AC10F.9030303@gmx.de> <CAOXsMFKJJhzU-3CYqguDePY42T+Vvhx9ytAfvoM6xyqaZY+N4g@mail.gmail.com> <FCC4DC05-44CD-4C2B-8C59-8E3E5B494DC0@dericed.com> <568D6710.8000605@gmx.de> <692F039A-180D-4535-B4A1-529A777573F5@dericed.com> <5693D5D6.6030709@xiph.org> <F6B37DB3-EDCB-4BD2-9B0D-F8A4F353F36E@dericed.com> <20160112133656.GJ4063@bunkus.org>
From: "Sebastian G. <bastik>" <bastik.public.mailinglist@gmx.de>
Openpgp: id=BFE90DE515B6F548CDE298939902921C2B944DAE
X-Enigmail-Draft-Status: N1010
Message-ID: <5697E0D6.5000906@gmx.de>
Date: Thu, 14 Jan 2016 18:54:30 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160112133656.GJ4063@bunkus.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:yyE5uW9RrtOuJw5XdONnr5FVhEobclthpfdc3k3LKQaTjJeeOGN fy5W2rLwv28j7BfD0TH2dVAmkHA3xEYetl72McNglDEs5eARkGuZMGLK8uhZrDtVy8ACjvg tr4K3AXO+HII1qc+xK97SsJ9f83iQ/tep6diBoo3yGhOwjeqif7qXpMA4yCMd6BzFuO+R7w fADu7TZUdArUiDLjY75IA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:n07p7/6U0Q4=:4Iw8ue3GfaC6sMHhr66TSf yOFOlmvSunpYD6ca8o25Ze+aqWGPFiUUXWuzJr7eOEwJ7hZrhdk/6X3Shsjs1bNbf/bwkI9Jf /W3Kh+N4T3xoP3NTyjkaPO9VXXWqw/79a/1Kl57ZxcLtcLSAQ/Ce2pqsa8R4WayionNxNImKw m7w0S/VP/cXN5sjUp5LRUimxLpWGEgjgb/DMpvnX0jBgZWHqhkKCyxuAphFCq7PJJ9XSa0GdN pwvVJxIn2JRxPuD1BvoWj1F8HDVqsaZC0ywGyPte6ZPNdZLZmTsPPP1G0vLkJvL/Ylz3bPsXH iw6mUdOUpReKdhTHUcdjkH8YLSo/fL0jVLBgiWC/X71I33eNTG2+iyQ5OxucZntUJZZ7lCbaZ dpr8bxvBLpBuoB/xlf1bd74wGsY4xRN4VAjADNNyZ1Ky/s2XJQJIRGYtGdUsspoJszX5n3WrJ gRUWGK8hmGOpdv6fLPWHFo4QFz7IsRaFZLvKLmJhqC2RurGKEAuLWuWgHnQh6t1bva4tpTzvb WPa5v5+38dEPIZLV4zTZiEh0KvS6JP5yP9zhgme507c5OUUIpyKymmN50jP+oa1pW4XextkZq 1/4hXi2zgDVaKCBiZwQPFRWqSp1+CYNrVsH6vsld1Y+MnwieFZrrpZxsU9M0965FHtrDSlpUv 96Z8WGTsL4YzWRKsiTe6p8o58q+Hh0qlh5qb/JQ4w0ei14KqHhYOuVRdm7LkAXO9WCnYCzp41 GSePUb0gARQjQwobSpjq7Q0jPDWwO6gXAeYYG5R2oEFkiGMKkHWBnN5E7akes9THygZvrrYJ9 78/2iOB
Archived-At: <http://mailarchive.ietf.org/arch/msg/cellar/AucJxRjKBhWBFVtHtFRO6D6WsDM>
Subject: Re: [Cellar] On the multiplicity of Info elements
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2016 17:54:37 -0000

12.01.2016, 14:36 Moritz Bunkus:
> Hey,
> 
>> From a sample set of 59,881 Matroska files uploaded to archive.org
>> only 119 of them include CRC-32 Elements. Almost 0.2%! Additionally
>> the webm Document Type lists the CRC-32 Element as unsupported. So I
>> think it’s true that it’s rarely bothered with. The implementation of
>> CRC-32 Elements does add many complications and perhaps demand has
>> been too low to resolve them. Moritz may have comments here.
> 
> That's pretty much spot on. The CRC32 element was added comparatively
> late; a lot of muxers had already been created by that time.
> 
> Most requests I've received where more concerned with error recovery
> than with error detection. This is something that CRC32 wasn't meant
> for; additionally CRC32 elements weren't meant to be written in the
> cluster elements which make up the bulk of a Matroska file's data.
> 
> Yes, there is a feature request[1] for adding support in mkvmerge and
> mkvinfo. It has been created in 2010, but except for those two people
> mentioned in the bug I haven't really received any other requests for
> such a functionality.
> 
> Kind regards,
> mosu
> 
> [1] https://github.com/mbunkus/mkvtoolnix/issues/543
> 

Hi,

to said ticket you added two entries [2][3] which mention a problem with
verifying checksums.

Would that be much easier to handle if the CRC would be about the data
that should be present in the file, but are omitted due to default
values aren't written? Compared to creating a checksum of the data that
actually get written and verifying said checksum.

I had a rather strong opinion towards including a CRC that covers the
elements that are written. I'm just curious and if something can be
solved elegantly rather than having to invest too much resources into
it, it might be worth reconsidering. After all it would be defined
within a proper specification.

Back then when I offered the bounty I expected matroska to be used a lot
more often in the future by other people than me. My usecase for
checksums was indeed just error recovery. However I am not against
extending the potential usecases to have applications use it to detect
errors.

[2] https://github.com/mbunkus/mkvtoolnix/issues/543#issuecomment-171036571
[3] https://github.com/mbunkus/mkvtoolnix/issues/543#issuecomment-171422587

--
Sebastian