Re: [Cellar] FFV1 nits

Dave Rice <dave@dericed.com> Wed, 14 June 2017 23:32 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 3A10F128D6F for <cellar@ietfa.amsl.com>; Wed, 14 Jun 2017 16:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] 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 0P0ZovXzzZci for <cellar@ietfa.amsl.com>; Wed, 14 Jun 2017 16:32:05 -0700 (PDT)
Received: from s172.web-hosting.com (s172.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 427D312025C for <cellar@ietf.org>; Wed, 14 Jun 2017 16:32:05 -0700 (PDT)
Received: from cpe-104-162-86-103.nyc.res.rr.com ([104.162.86.103]:39192 helo=[10.0.1.3]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from <dave@dericed.com>) id 1dLHla-000NLG-CA; Wed, 14 Jun 2017 19:32:03 -0400
From: Dave Rice <dave@dericed.com>
Message-Id: <23BFF235-C4A1-4162-85F8-173AC2C1CA70@dericed.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE87A15C-2ACB-4CB1-84D6-BEBC525D36D4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 14 Jun 2017 19:31:59 -0400
In-Reply-To: <73b5bfa6-2de6-ede8-4f05-f7c5b382202f@mediaarea.net>
Cc: cellar@ietf.org
To: Jerome Martinez <jerome@mediaarea.net>
References: <CADK0Wux=z7UEp2Q8Lto-tkJ9tjYF=ZyOB-Q9L5eMwZFgF=rETw@mail.gmail.com> <7F342F81-40F1-4AF6-9083-5D556BFD447E@dericed.com> <73b5bfa6-2de6-ede8-4f05-f7c5b382202f@mediaarea.net>
X-Mailer: Apple Mail (2.3273)
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/SiQTUJuDdWUj8dr0suJK_6yxrrA>
Subject: Re: [Cellar] FFV1 nits
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: Wed, 14 Jun 2017 23:32:07 -0000

> On Jun 9, 2017, at 10:23 AM, Jerome Martinez <jerome@mediaarea.net> wrote:
> 
> Le 08/06/2017 à 01:51, Dave Rice a écrit :
>> AFAIK there are no IANA considerations for FFV1. Anyone suggest otherwise? I added a pull request at github.com/FFmpeg/FFV1/pull/71 <https://github.com/FFmpeg/FFV1/pull/71> to just say "This document has no IANA actions."
> 
> I understand that IANA has several lists:
> - one for "containers" so more Matroska
> - one for RTP payload types, so more FFV1 and FLAC.
> Additionally, HTML video element may contain a "codecs" attribute and we need to have an identifier for matroska, ffv1, flac.
> 
> For example, currently we currently have on Internet that:
> <video width="720" height="486">
>   <source src="movie.webm" type='video/webm; codecs="vp8, vorbis"'>
>   <source src="movie.mp4" type='video/mp4; codecs="mp4v.20.240, mp4a.40.2"'>
> Your browser does not support the video tag.
> </video>
> 
> it may be good to have an additional line:
>   <source src="movie.mkv" type='video/matroska; codecs="ffv1, flac"'>
> 
> Does it fit in IANA section or elsewhere?
> 
> BTW, FFV1 codec could have suffixes, e.g. "ffv1.3" 3 being the version, as mp4v has something for defining requested capabilities.

Could be something like the draft below. Please consider this as a my-first-iana-considerations-draft. Comments?

# IANA Considerations

One media subtype (video/ffv1) has been defined and registered as described in the following section.

## FFV1 Media Type Registration

Media type registration is done according to [@!RFC6838] and [@!RFC4855].

Type name: video

Subtype name: ffv1

Required parameters:
	version: The FFV1 version, see section X.X.

Optional parameters:
	[[ what is worthwhile: frame size, frame rate, pix_fmt, duration? ]]

Encoding considerations:
          This media type is framed binary data (see RFC 4288, Section 4.8).

Security considerations: See Section X of this document.

Interoperability considerations:
	[[To do]]

Published specification: RFC nnnn

Applications that use this media type:
	Any application that requires the transport of lossless video can use this media type. Some examples are, but not limited to screen recording, scientific imaging, and digital video preservation.

Additional information: none

Person & email address to contact for further information:
	[[ suggestions? ]]

Intended usage: COMMON

Restrictions on usage:
	[[to do, such the contains section of the document add an ffv1 in RTP section?]]

Author:
	[[ to do]]

Change controller:
          IETF cellar working group delegated from the IESG.

Thanks,
Dave Rice