[Cellar] generate a version (0, 1, 3) and version 4 FFV1 document from single source

Dave Rice <dave@dericed.com> Sat, 03 February 2018 18:24 UTC

Return-Path: <dave@dericed.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D34512D96A for <cellar@ietfa.amsl.com>; Sat, 3 Feb 2018 10:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 EV9lfJ53rzVB for <cellar@ietfa.amsl.com>; Sat, 3 Feb 2018 10:24:23 -0800 (PST)
Received: from server172-2.web-hosting.com (server172-2.web-hosting.com [68.65.122.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 118E6124239 for <cellar@ietf.org>; Sat, 3 Feb 2018 10:24:23 -0800 (PST)
Received: from cpe-104-162-94-162.nyc.res.rr.com ([104.162.94.162]:47807 helo=[10.0.1.2]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from <dave@dericed.com>) id 1ei2U9-0046Rm-Ax for cellar@ietf.org; Sat, 03 Feb 2018 13:24:22 -0500
From: Dave Rice <dave@dericed.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0152A0A9-4EA0-4AF5-908C-66034FD7596F"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Message-Id: <F2A44982-6935-40B9-ABB9-AF6D88CFB285@dericed.com>
Date: Sat, 03 Feb 2018 13:24:15 -0500
To: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
X-Mailer: Apple Mail (2.3445.4.7)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/j66bsfibXC_3RhMHUG114yuNc6A>
Subject: [Cellar] generate a version (0, 1, 3) and version 4 FFV1 document from single source
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 03 Feb 2018 18:24:24 -0000

Hi cellar,

I’ve drafted a pull request at https://github.com/FFmpeg/FFV1/pull/102 based on Michael Niedermayer’s suggestion https://github.com/FFmpeg/FFV1/pull/93#issuecomment-356348383 <https://github.com/FFmpeg/FFV1/pull/93#issuecomment-356348383>. This attempts to create a method where the FFV1 specification may be worked upon within a single document while the parts that only relevant to the version 0,1,3 document are suppressed from the version 4 document and vice versa. To do this I’d created a method of ending lines with with "{V3}” (for version 3 and prior) or “{V4}” for version 4 or greater. I think this will help enable work to progress on the version 4 document as defined in our charter even while the version 0,1,3 hasn’t been reviewed by the IESG yet.

However some IETF questions:

In the PR the new outputs of the Makefile are:
draft-ietf-cellar-ffv1-01 (defines version 0, 1 and 3 of FFV1)
draft-ietf-cellar-ffv1-v4-00 (defines version 4 of FFV1)

This keeps the same id for version 0, 1, and 3 but would something else be more clear? Any examples of naming when IETF defines multiple versions of the same thing in separate documents?

I’ve separated the document version numbers for each, so draft-ietf-cellar-ffv1 stays at 01 and draft-ietf-cellar-ffv1-v4 starts at 00. Work?

In the version 4 output there are references to exceptions defined in our work on version 0,1,3. These include all lines starting with “Background”. I suggest resolving these in a subsequent commit, but perhaps the version 4 document need not include these but could only reference exceptions existed in prior version.

Best Regards,
Dave Rice