Re: [dispatch] Stephen Farrell's Yes on charter-ietf-cellar-00-00: (with COMMENT)

Michael Niedermayer <michael@niedermayer.cc> Tue, 27 October 2015 19:16 UTC

Return-Path: <michael@niedermayer.cc>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B571ACE63 for <dispatch@ietfa.amsl.com>; Tue, 27 Oct 2015 12:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 E3VTlaAJ_6N5 for <dispatch@ietfa.amsl.com>; Tue, 27 Oct 2015 12:16:37 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66D071ACE6D for <dispatch@ietf.org>; Tue, 27 Oct 2015 12:16:37 -0700 (PDT)
Received: from mfilter22-d.gandi.net (mfilter22-d.gandi.net [217.70.178.150]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id 81F52C5A5C; Tue, 27 Oct 2015 20:16:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter22-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter22-d.gandi.net (mfilter22-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 2wtXvtcyWzNc; Tue, 27 Oct 2015 20:16:33 +0100 (CET)
X-Originating-IP: 84.114.129.144
Received: from localhost (chello084114129144.4.15.vie.surfer.at [84.114.129.144]) (Authenticated sender: michael@niedermayer.cc) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id DFED5C5A40; Tue, 27 Oct 2015 20:16:32 +0100 (CET)
Date: Tue, 27 Oct 2015 20:15:36 +0100
From: Michael Niedermayer <michael@niedermayer.cc>
To: Ben Campbell <ben@nostrum.com>
Message-ID: <20151027191536.GY4556@nb4>
References: <20151022133935.26487.12997.idtracker@ietfa.amsl.com> <2D88BA7A-6B89-465E-91FC-4FB6DC422434@nostrum.com> <CAOXsMFJY-EPt3u91Qy7A8Zf2OXt6_Y7pF4KWCMVxjXpi3J2_Jg@mail.gmail.com> <20151022211948.GS4556@nb4> <98E2EBE2-4580-4A12-A77C-FAE69185F171@nostrum.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="T/Mbx1CndTR58uu2"
Content-Disposition: inline
In-Reply-To: <98E2EBE2-4580-4A12-A77C-FAE69185F171@nostrum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/FwL04GKYYtBzHWfMgQGmw8Ejass>
Cc: DISPATCH <dispatch@ietf.org>
Subject: Re: [dispatch] Stephen Farrell's Yes on charter-ietf-cellar-00-00: (with COMMENT)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 27 Oct 2015 19:16:39 -0000

On Mon, Oct 26, 2015 at 02:23:54PM -0500, Ben Campbell wrote:
> On 22 Oct 2015, at 16:19, Michael Niedermayer wrote:
> 
> 
> [...]
> 
> >>>>
> >>>>I wonder is there any interest in the security of the archived
> >>>>stuff here, and whether the WG would want to possibly take
> >>>>that on, most likely later. I'm not saying they should, as that
> >>>>could be a lot of possibly contentious work, but if they did
> >>>>want to do it, it'd be good to say in the charter.
> >>
> >>Does he mean security as in only allowing certain people to
> >>access the
> >>data ? IMO it's out of the scope and better handled out of the file
> >>format/streaming. It's more a transport/storage issue than format.
> >>
> >>There is encryption possible in WebM though that's working with a EME
> >>DRM module.
> >>http://www.webmproject.org/docs/webm-encryption/
> >>
> >
> >>If he means data safety, that's something we can work on. We already
> >>have the CRC for checking. In the past we also discussed redundancy
> >>but it was ruled out (again, better handled outside of the file
> >>format).
> >
> >forward error correction, that is to add redundancy to recover from
> >damaged or lost parts of an archived file or stream/track, is
> >something that sounds interresting. CRCs also exist at the video
> >stream
> >(FFv1) layer. Theres currently no means to restore lost frames, slices
> >or disk sectors except through concealing them based on previous
> >frames. The existing CRCs are sufficient though to correct rare bit
> >errors, if that occurs in any actual use case.
> >Adding some layer of protection to protect from damaged or unreadable
> >disk sectors or other larger damges losslessly is possible and
> >interresting. Iam not sure at which layer that would be best to do
> >though.
> 
> For the record, I think Stephen was asking more about
> confidentiality than about error correction.
> 

> Do you think anything relative to error correction needs to be added
> to the charter? It seem to me that is something that could be added
> in a future recharter if people think something becomes needed
> beyond the currently planned work.

the charter is fine, i just wanted to comment on "data safety", which
as it turns out the original question wasnt about ...

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Rewriting code that is poorly written but fully understood is good.
Rewriting code that one doesnt understand is a sign that one is less smart
then the original author, trying to rewrite it will not make it better.