Re: [Cellar] Adding private elements to Matroska

Michael Bradshaw <> Fri, 13 April 2018 19:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9E6C212783A for <>; Fri, 13 Apr 2018 12:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] 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 NeBy-wbyboV0 for <>; Fri, 13 Apr 2018 12:27:40 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E7C64126C89 for <>; Fri, 13 Apr 2018 12:27:39 -0700 (PDT)
Received: by with SMTP id h143-v6so4518973ita.4 for <>; Fri, 13 Apr 2018 12:27:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xF7RmPX+owiPPePqUe2kDVV/FEj9FPn8DWx08xZovGs=; b=F0QsXvvF9CBUJYFHLmo+FqvXsRh6S3GXSyF0BVN5rMYcVCLaVtSi6G9lupGzciWy3E gwSvICQwSgY1OCpYKfXOwN5xgSoFGEfdZHbA/0Hv9DKbOYYLOSiR+JdNHNg+u5Azigci PAI0cRNgmggFuqo8Rng5IFKOBnvZT9rrGxcsdckicJWpSsIFQDkPm+IHykUiIb2VHC0O jCtRYN5PGlDDqMYoMdwvwh7gLhtiyuCX7R9AOIq3IX7ztvKKrycN/oYj6B/d0BeLp+hp fVkQD7r4dW3GjwFwtD+nyMsBWvyG8zGF+cjyhCTmuDpl3K9iYLJhrUZGNzsKorJ7NtT8 pSRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xF7RmPX+owiPPePqUe2kDVV/FEj9FPn8DWx08xZovGs=; b=ZKjitgc3khbWWhvnHuX6KC/Kx53Hul+joVVWwXPfqBjRdzbsjzckgV3DhaSNS85H9t t/uMvrbd4Xr6jn28txpn8rjSCvMGr3HiOFcC1qQtPYdKkTgv90gyz1PPC/4wbP2Yw5Y2 QDPMTXdgoLlWd1rzthYI+FtQ48xSK9d4gj/k2MJxh829M0IDX4w6VgGS8amIhw6gIb3I 2i6nxIGE/wm+VdUxXcBn0u1YIFWmWeCY7bObroqfx0GiJQ7amFs1IzZSqAImNvO/OCWp Y7BrjGxBM+1PFpj8eoRpeHJv2UFVHcaDvQ8Z0/QqoChyv0Yw4mX9m4lVmqcrMNxArHTO wFDg==
X-Gm-Message-State: ALQs6tB91ytPnV/jODSDg9d/dPnu9C0b2zxqQ42SWKNUoBecUxWw9XNL Ljk0qsGTCSq1bCm4852Lg9gV/X5mxOUcDTIs7aag6w==
X-Google-Smtp-Source: AIpwx4/wQfC3pU++LuZHQGKK26ThIJLDtlKfHu5RSYw575orXkiXcUYWDe0HkOeh2bampYYvvq1e3cBKZc1933Sz+r4=
X-Received: by 2002:a24:e4c2:: with SMTP id o185-v6mr6651380ith.37.1523647658825; Fri, 13 Apr 2018 12:27:38 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Michael Bradshaw <>
Date: Fri, 13 Apr 2018 19:27:27 +0000
Message-ID: <>
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <>
Content-Type: multipart/alternative; boundary="0000000000007839300569bfdd34"
Archived-At: <>
Subject: Re: [Cellar] Adding private elements to Matroska
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 13 Apr 2018 19:27:42 -0000

I concur with Martin. For this particular case, I don't think new elements
should be introduced just for RAWcooked. RAWcooked, could instead add an
attachment or tag that contains its needed metadata.

In general, I'm opposed to private elements in Matroska. If, for some
reason, attachments and tags aren't feasible, I could concede to adding a
new global master element that is comprised of two child binary elements:
one acting as an identifier, and one acting as a payload. That way any
arbitrary private info could be identified stored anywhere in the file. But
I'd prefer to avoid that, if possible.