Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Martijn van Beurden <mvanb1@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Request For Comment no Matroska specs
Date: Sat, 2 Apr 2022 11:27:17 +0200
Message-ID: <CADQbU6_MtcdUP94QubMG2x5bmWo2N-_RJbV1Vbt=jHQYK_83JA@mail.gmail.com> (raw)
In-Reply-To: <84c8e30f-1f4b-6aac-6e54-f109cab09449@ycbcr.xyz>

Op vr 1 apr. 2022 14:53 schreef Steve Lhomme <robux4@ycbcr.xyz>:

> On 2022-04-01 14:33, Steve Lhomme wrote:
> > Hi ffmmpeg developers,
> >
> > As you may know, we are working hard on the Matroska specifications at
> > the IETF. We already got EBML as an RFC [1]. We are in the process of
> > finalizing the main Matroska document. Before we submit the document for
> > formal review before "final" publishing, we would like people who know a
> > bit about Matroska to review the current draft in case there are parts
> > missing, hard to decipher or, even worse, bugs.
> >
> > This is a 200 pages document, so it may take a while. You can find draft
> > 09 at [2]. It should explain what is found in Matroska 1 to 4. Some
> > unused elements have been deprecated since the original informal
> > specifications. These elements can be found in Annex A.
>
> I forgot to mention you can reply here or on the GitHub repository of
> the specs [3] by creating an issue or even a Pull Request.
>
> [3] https://github.com/ietf-wg-cellar/matroska-specification
>
> > Thanks
> >
> > [1] https://datatracker.ietf.org/doc/rfc8794/
> > [2] https://datatracker.ietf.org/doc/draft-ietf-cellar-matroska/


There is also a HTML version of the draft available, which is perhaps
easier to read:
https://www.ietf.org/archive/id/draft-ietf-cellar-matroska-09.html
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-04-02  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 12:33 Steve Lhomme
2022-04-01 12:53 ` Steve Lhomme
2022-04-02  9:27   ` Martijn van Beurden [this message]
2022-04-15 18:07     ` Martijn van Beurden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADQbU6_MtcdUP94QubMG2x5bmWo2N-_RJbV1Vbt=jHQYK_83JA@mail.gmail.com' \
    --to=mvanb1@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git