From nobody Sun Sep  1 09:28:48 2019
Return-Path: <mcr@sandelman.ca>
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 6A9E112007A; Sun,  1 Sep 2019 09:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 3wFzja3H_cFz; Sun,  1 Sep 2019 09:28:38 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 621AB120033; Sun,  1 Sep 2019 09:28:37 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [142.169.78.110]) by relay.sandelman.ca (Postfix) with ESMTPS id 11AF91F45A; Sun,  1 Sep 2019 16:28:35 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 9372A3880; Sun,  1 Sep 2019 12:29:05 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Rice <dave@dericed.com>, tools-discuss@ietf.org
cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
In-reply-to: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com>
References: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com>
Comments: In-reply-to Dave Rice <dave@dericed.com> message dated "Sat, 31 Aug 2019 20:13:16 -0400."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Sun, 01 Sep 2019 12:29:05 -0400
Message-ID: <16851.1567355345@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/bPz8mAfyBnN10sHsEow99Ez9V1o>
Subject: Re: [Cellar] expressing both svg graphics and ascii-art fallback within an rfc2xml version 3 file?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 01 Sep 2019 16:28:40 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


{reposting to tools-discuss}

Hello cellar,

The draft of FFV1 now uses xml2rfc version 3 as defined at
https://tools.ietf.org/html/rfc7991
<https://tools.ietf.org/html/rfc7991>. Presently in the markdown source of
the FFV1 draft, the math is maintained in both LaTeX expressions (which are
converted to SVG for inclusion in the RFC XML) as well as an Ascii Art
representation (heavily reliant on functions defined within the draft). For
example:=20

vs

r_{i} =3D floor( ( R_{i} * S_{i,C_{i}} ) / 2^8 )

Whether in SVG or ascii art, this data is contained by the <artwork> node in
rfc2xml version 3. In https://tools.ietf.org/html/rfc7991#section-2.5
<https://tools.ietf.org/html/rfc7991#section-2.5> it states,=20

   Alternatively, the "src" attribute allows referencing an external
   graphics file, such as a vector drawing in SVG or a bitmap graphic
   file, using a URI.  In this case, the textual content acts as a
   fallback for output representations that do not support graphics;
   thus, it ought to contain either (1) a "line art" variant of the
   graphics or (2) prose that describes the included image in sufficient
   detail.

A bit later it says that SVG data may be encoded and stored within the
<artwork>=E2=80=99s @src attribute such as=20=20

   o  As a data: URI, such as: <artwork type=3D"svg" src=3D"data:image/
      svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3=E2=80=A6">

So from this I was hoping we could work on one draft rfc2xml version 3 file
that could use the SVG image data or use the ascii art as a fallback; howev=
er
when I try to craft the <artwork> node with both such as:=20

   <artwork type=3D"svg" src=3D"data:image/svg+xml,ENCODED_SVG_MATH_IMAGE_H=
ERE=E2=80=9D>FALLBACK_ASCII_ART_HERE</artwork>

then the output =E2=80=9Cv3-plaintext=E2=80=9D output of the conversion too=
l at
https://xml2rfc.tools.ietf.org/experimental.html
<https://xml2rfc.tools.ietf.org/experimental.html>, does not use the textual
content of the <artwork> node as a fallback but instead places a warning su=
ch
as=20

   (Artwork only available as svg: No external link available, see
   draft-ietf-cellar-ffv1-08.html for artwork.)

Is it feasible (recommended?) to have one rfc2xml XML document that could be
a source for both plaintext formats (using an ascii art fallback) and
non-plaintext formats such as HTML and PDF which would use the embedded SVG
data?=20

Kind Regards,
Dave Rice


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAl1r8dEACgkQlUzhVv38
QpCvwwf/W9ICCNy7DBXzl4Orx0AV8WROYpHmQ9OEzKyKIKRkIogIsXVyvhbLQ54x
nPaLIDWFHMQGtHRI8jwl3o8wu4RZtM0DoNkzvMsi7E4Cwrrhr9e9xsdzIicGuwbb
SXDhsXgKT/ys6pMbWe+te8GBhhpmlQ0+rgk1ZzZMWyrdOHgqPK1AFbkB8LQbilnN
1wMWU7ZO0iBvfru/JZ/X3SMqQ2nZWzadot1xlUTJVkDvebqQnhr3ok4CM3E6kqF8
2wXPFqKdpxdLJPWcnJkOYgjuYBMLta0eiMEEzmcKMx4qiyJRPH9HECcgVdJGGhIQ
EMqBHy75Ztu5nrLm4gh1AQLSrbkj4w==
=+act
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Sep  1 09:39:04 2019
Return-Path: <julian.reschke@gmx.de>
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 87EF5120077; Sun,  1 Sep 2019 09:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 fX53hTHMlD1P; Sun,  1 Sep 2019 09:38:53 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C148C120025; Sun,  1 Sep 2019 09:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1567355879; bh=pKV63Zna5NWebNYd4mQgVG6Q2oQSzR5h3S5Ai+1Ckbs=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=SbZ9xL+VcHUy9KAuSEmd4gmgBYZTUXj4dOa9HtoKZi/hKkE5sgniZgVPzrnQUxC8w lXcy5IrZh1/8OF2YzaOyVvTCLBuV1NrKoVEK7nu6/q61nfv+P6XUmuoIuGWdr9hbKc z89gCgiLImaSiTJ7qZS7uDKL3vtVfZ5SkRElVI1M=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([217.251.132.77]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MuUj2-1iLIvN1R9m-00rYCN; Sun, 01 Sep 2019 18:37:59 +0200
To: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Rice <dave@dericed.com>,  tools-discuss@ietf.org
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
References: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com> <16851.1567355345@dooku.sandelman.ca>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <edd3b1b5-7f6a-bd8b-54d0-f247fc5eb573@gmx.de>
Date: Sun, 1 Sep 2019 18:37:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <16851.1567355345@dooku.sandelman.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:BlwlTOJcKlW4wXrXt+vAUqsDUm+RuCndjBW6O/yQkwsL0j1bgM8 sfuV1CUTu6lihZzQJZ8sWa1Wk7D7lLTdU1zHCOejTnLCd2tDK1+KjRB66DlypvaEWdLoZ1d XAcwm6sjSBXU7kOVue0fUDSeCR7O9JOUcf+VMzIfnd7Y2+S31smsC6si/5ZO11wttSstSKq 0o5RxrfdF8OR6mrvGOUwQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:2HeDP/Q5Ccs=:xBsRtDi6kB8WsBz1SNRw8L fOwSYQSIfkorDSy49nrQtZ8szFDI0VDBH5AoVVNiKpvAf4BRCbXmpxZn8KFnK4V0RXk+5MLTa nalQ9tVMxAHGIubV+idhVF14CraFuIQs7kw6WlCIhu/jWmAi66sQy+JlqMyrgsGUCqwJLiT4X oSsPN6sG7QMmzEZz+EdhxhfpnmaJvImhsrqqSw5WbUZ3bYde0CyS+NdK30QigcVKQTp9HfpKL ecE8H80AiK41q3UpBG8dMCW84p3d32/LbGBHhYbTASV0YHmRLLgZx1ALL8SkbaSixdcfywO8C /vYZjpgWepoCb4O7QUnDzHI3z6NipfFI5a/1kRfpR1NkiHpscHQYVc93qcczkHDDsHc4oqDhE NY722bjh/ebNJRdawgCWnU0k2g5F+d3MmrV9P7Tj1QMH05wS7vEsOUgSZBXqrPz03G6TqRYPE 7cN6RYjlT4Qn7d+4YYQ+fD/wozsKqSIG7DzdoGsNc6C3PeOQ8qA3KqFPWMtC+PcOUjcOz5ksz PPKLrOh0sgcoTZO7COA1TUTbO1N3GwkjipYYgPphlX7X4oQnVdwDO3ccPoIpw7MilhKnyhH/Y KbSZpVwpDLy/13randdEmUN5vSl6EHoAhUYxGH0B//ujC4hN2cid0oTSojDxyMhWzdHSrVRRN 7KbQiiiu9zdcHQgaMOBp2Fkotylekz09N2lpqqzn06ynieJdbyk6ZUEx4p398rnuuAPZpzJQm mIA36Uv66qEIhiSUnxq/zSdUByCWwb8NhkgTpXYSHvd3ksarQNYZ4rpjdPgZXSEpYIAIQ+ZkA 1ZJh4gNGq8aMiGz1wYXw4cN64wiBNcuKZ7fixM7blpeUpR6f+nm3f5SIFZjEhukfSYbkIdYtB 8I3JIrCrTm1vf+v84XqxI6WxyDOBreiQ9PvI2je79eZl7rRp6OxhBpDNKBavteHcW6RGIJ4fN r6BP9ulRV4OrbiSenM4Y2GBt8tbiM/OIeiEBzgYxP+UiqbBXOU0IpqKIL4R8mBmMd4kAxteuX yZvdiGtAUx7+QFwH6wmLyvJlzVTvZYDt/b/r4BM6syChUrnhlRXXAvasb1jYm9nbWnUMhhe83 wWbaClAgm2uk4oHSA0HKE1aWKOxYL2YbXsBWpOThxGlWhpmluYdBEV1AemzmW4dawFIldXu4i JdIT5Rq37jbrb7xVzNpM8h5/+sFXJxYxjfHqmWOrEYobhH9w==
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/qErq-ba9DCLSSQbUu_Fyd4o3yM4>
Subject: Re: [Cellar] [Tools-discuss] expressing both svg graphics and ascii-art fallback within an rfc2xml version 3 file?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 01 Sep 2019 16:38:56 -0000

On 01.09.2019 18:29, Michael Richardson wrote:
>
> {reposting to tools-discuss}
>
> Hello cellar,
>
> The draft of FFV1 now uses xml2rfc version 3 as defined at
> https://tools.ietf.org/html/rfc7991
> <https://tools.ietf.org/html/rfc7991>. Presently in the markdown source =
of
> the FFV1 draft, the math is maintained in both LaTeX expressions (which =
are
> converted to SVG for inclusion in the RFC XML) as well as an Ascii Art
> representation (heavily reliant on functions defined within the draft). =
For
> example:
>
> vs
>
> r_{i} =3D floor( ( R_{i} * S_{i,C_{i}} ) / 2^8 )
>
> Whether in SVG or ascii art, this data is contained by the <artwork> nod=
e in
> rfc2xml version 3. In https://tools.ietf.org/html/rfc7991#section-2.5
> <https://tools.ietf.org/html/rfc7991#section-2.5> it states,
>
>     Alternatively, the "src" attribute allows referencing an external
>     graphics file, such as a vector drawing in SVG or a bitmap graphic
>     file, using a URI.  In this case, the textual content acts as a
>     fallback for output representations that do not support graphics;
>     thus, it ought to contain either (1) a "line art" variant of the
>     graphics or (2) prose that describes the included image in sufficien=
t
>     detail.
>
> A bit later it says that SVG data may be encoded and stored within the
> <artwork>=E2=80=99s @src attribute such as
>
>     o  As a data: URI, such as: <artwork type=3D"svg" src=3D"data:image/
>        svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3=E2=80=A6">
>
> So from this I was hoping we could work on one draft rfc2xml version 3 f=
ile
> that could use the SVG image data or use the ascii art as a fallback; ho=
wever
> when I try to craft the <artwork> node with both such as:
>
>     <artwork type=3D"svg" src=3D"data:image/svg+xml,ENCODED_SVG_MATH_IMA=
GE_HERE=E2=80=9D>FALLBACK_ASCII_ART_HERE</artwork>
>
> then the output =E2=80=9Cv3-plaintext=E2=80=9D output of the conversion =
tool at
> https://xml2rfc.tools.ietf.org/experimental.html
> <https://xml2rfc.tools.ietf.org/experimental.html>, does not use the tex=
tual
> content of the <artwork> node as a fallback but instead places a warning=
 such
> as
>
>     (Artwork only available as svg: No external link available, see
>     draft-ietf-cellar-ffv1-08.html for artwork.)
>
> Is it feasible (recommended?) to have one rfc2xml XML document that coul=
d be
> a source for both plaintext formats (using an ascii art fallback) and
> non-plaintext formats such as HTML and PDF which would use the embedded =
SVG
> data?
>
> Kind Regards,
> Dave Rice

<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-09#section-3.1.1>
might be what you're looking for.

Disclaimer: I proposed a much simpler solution, but that's where we are
right now.

Best regards, Julian


From nobody Sun Sep  1 09:47:25 2019
Return-Path: <henrik@levkowetz.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 0CEB212007C; Sun,  1 Sep 2019 09:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 HCeL_WEiYBbD; Sun,  1 Sep 2019 09:47:21 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E294D120025; Sun,  1 Sep 2019 09:47:21 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:57811 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1i4Szt-0007qP-1j; Sun, 01 Sep 2019 09:46:59 -0700
To: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Rice <dave@dericed.com>,  tools-discuss@ietf.org
References: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com> <16851.1567355345@dooku.sandelman.ca>
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <7b4e6a16-0b2b-a6f9-2ae6-5b1ddd3c05f8@levkowetz.com>
Date: Sun, 1 Sep 2019 18:46:17 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <16851.1567355345@dooku.sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="feswXRjrCknn6Me9upJ1L4VxvLept2Jri"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: cellar@ietf.org, tools-discuss@ietf.org, dave@dericed.com,  mcr+ietf@sandelman.ca
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/GSmQwN4D6PmvuNnsVESh6ua4JOw>
Subject: Re: [Cellar] [Tools-discuss] expressing both svg graphics and ascii-art fallback within an rfc2xml version 3 file?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 01 Sep 2019 16:47:24 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--feswXRjrCknn6Me9upJ1L4VxvLept2Jri
Content-Type: multipart/mixed; boundary="eA8BKDwSdBC5wku7S2wPFUcU52kW1eiJh";
 protected-headers="v1"
From: Henrik Levkowetz <henrik@levkowetz.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Rice <dave@dericed.com>,
 tools-discuss@ietf.org
Cc: Codec Encoding for LossLess Archiving and Realtime transmission
 <cellar@ietf.org>
Message-ID: <7b4e6a16-0b2b-a6f9-2ae6-5b1ddd3c05f8@levkowetz.com>
Subject: Re: [Tools-discuss] [Cellar] expressing both svg graphics and
 ascii-art fallback within an rfc2xml version 3 file?
References: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com>
 <16851.1567355345@dooku.sandelman.ca>
In-Reply-To: <16851.1567355345@dooku.sandelman.ca>

--eA8BKDwSdBC5wku7S2wPFUcU52kW1eiJh
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi David,

Response at the bottom:

On 2019-09-01 18:29, Michael Richardson wrote:
>=20
> {reposting to tools-discuss}
>=20
> Hello cellar,
>=20
> The draft of FFV1 now uses xml2rfc version 3 as defined at
> https://tools.ietf.org/html/rfc7991
> <https://tools.ietf.org/html/rfc7991>. Presently in the markdown source=
 of
> the FFV1 draft, the math is maintained in both LaTeX expressions (which=
 are
> converted to SVG for inclusion in the RFC XML) as well as an Ascii Art
> representation (heavily reliant on functions defined within the draft).=
 For
> example:=20
>=20
> vs
>=20
> r_{i} =3D floor( ( R_{i} * S_{i,C_{i}} ) / 2^8 )
>=20
> Whether in SVG or ascii art, this data is contained by the <artwork> no=
de in
> rfc2xml version 3. In https://tools.ietf.org/html/rfc7991#section-2.5
> <https://tools.ietf.org/html/rfc7991#section-2.5> it states,=20
>=20
>    Alternatively, the "src" attribute allows referencing an external
>    graphics file, such as a vector drawing in SVG or a bitmap graphic
>    file, using a URI.  In this case, the textual content acts as a
>    fallback for output representations that do not support graphics;
>    thus, it ought to contain either (1) a "line art" variant of the
>    graphics or (2) prose that describes the included image in sufficien=
t
>    detail.
>=20
> A bit later it says that SVG data may be encoded and stored within the
> <artwork>=E2=80=99s @src attribute such as =20
>=20
>    o  As a data: URI, such as: <artwork type=3D"svg" src=3D"data:image/=

>       svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3=E2=80=A6">
>=20
> So from this I was hoping we could work on one draft rfc2xml version 3 =
file
> that could use the SVG image data or use the ascii art as a fallback; h=
owever
> when I try to craft the <artwork> node with both such as:=20
>=20
>    <artwork type=3D"svg" src=3D"data:image/svg+xml,ENCODED_SVG_MATH_IMA=
GE_HERE=E2=80=9D>FALLBACK_ASCII_ART_HERE</artwork>
>=20
> then the output =E2=80=9Cv3-plaintext=E2=80=9D output of the conversion=
 tool at
> https://xml2rfc.tools.ietf.org/experimental.html
> <https://xml2rfc.tools.ietf.org/experimental.html>, does not use the te=
xtual
> content of the <artwork> node as a fallback but instead places a warnin=
g such
> as=20
>=20
>    (Artwork only available as svg: No external link available, see
>    draft-ietf-cellar-ffv1-08.html for artwork.)
>=20
> Is it feasible (recommended?) to have one rfc2xml XML document that cou=
ld be
> a source for both plaintext formats (using an ascii art fallback) and
> non-plaintext formats such as HTML and PDF which would use the embedded=
 SVG
> data?

Yes.  The specification of how to handle the text fallback in the RFC 799=
x
documents was in part contradictory, and also not as extensible and easil=
y
editable as one could wish.  It currently looks like rfc7991bis largely w=
ill
follow the proposal discussed on the xml2rfc-dev list earlier this year, =
and
captured in the xml2rfc implementation notes draft here:

https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-09#section-3.1.1

which introduces an <artset> element which can contain multiple <artwork>=

elements with different type attributes, for instance (artwork and some
details omitted:

  <artset>
    <artwork type=3D"svg" src=3D"..."/>
    <artwork type=3D"ascii-art" ...>
	# ascii art
    </artwork>
  </artset>

For more on this, and for a light introduction to the v3 schema, check:
http://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html#artwork-alt=
ernatives


Best regards,

	Henrik


>=20
> Kind Regards,
> Dave Rice
>=20
>=20
>=20
>=20
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>=20
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>=20
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org
>=20


--eA8BKDwSdBC5wku7S2wPFUcU52kW1eiJh--

--feswXRjrCknn6Me9upJ1L4VxvLept2Jri
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEifjc5+rnL1MJBcZSTptXS4+7FxoFAl1r9dkACgkQTptXS4+7
FxoaLQ//dGBO1Wa1oLI3stW1DJwXSG7pw3VU8y/yVexRc6ETgPKPnYdU8v4Tva0R
AS4HJz9Id1pw5CmlA2VwgmnYkOaQvu2e7IBvFVhvUxZwl5UqYSos9iqisRHnOtTT
d12D6zLHbWTYwarUAcEEFUo98SRJJXXS72wjWcG0s7xiPwOwnphqZzDQovsPmxcA
qfeeIpDoc+8EgZ2gfCLVi1X3Djqy9CwqC6grhpMSfY4afPItnqqmQPawm3OnaSw9
ACKxvxg0sNP9mnZ4MQUsGr4MBTXfN8OqkGVipCKupY3XxfrBm0WjtiHvudICsYSe
USUE1EmnJbHnJR9lWQd5QJvgikfBX5c/V198GwC84/dVWsJLhgLHmSSLNPnkY6o6
hYQEBQuuszK1z5C2T/zmcHA18nluC+xK99DCM3OsxS7BJGI7UjnFQzMogr8OCc+L
xZFTRNupSbanBAo+rDNHSoGOr3AEqevxt/aKpqVWMQZ83eK1B1NLHASJQOYXz07m
9BzT01vm7pQ45kg6Nuh35+Uq8RI7E9OpiJiEcRWr/Hbx81X/5QSmjItW3EHblSXN
B9t4a1vJVJG6nVEBRRAm5KGPdieEDO09elAKoji/opT0kD25agXIAeFpKwVBK2rj
olsPT2VKP0p85eUXRyOr6SSy+1x8OmLikErYf/TAHw1JsDZKk28=
=5rQf
-----END PGP SIGNATURE-----

--feswXRjrCknn6Me9upJ1L4VxvLept2Jri--


From nobody Sun Sep  1 15:13:15 2019
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 8A1561200CD; Sun,  1 Sep 2019 15:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.118
X-Spam-Level: 
X-Spam-Status: No, score=-1.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 yNjZbMx8a9S1; Sun,  1 Sep 2019 15:13:11 -0700 (PDT)
Received: from server172-3.web-hosting.com (server172-3.web-hosting.com [68.65.122.111]) (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 B141912008F; Sun,  1 Sep 2019 15:13:11 -0700 (PDT)
Received: from cpe-104-162-94-162.nyc.res.rr.com ([104.162.94.162]:48842 helo=[10.0.1.3]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <dave@dericed.com>) id 1i4Y5o-0002C2-V8; Sun, 01 Sep 2019 18:13:10 -0400
From: Dave Rice <dave@dericed.com>
Message-Id: <5C1CA680-3880-4D7B-A6D5-CC28DDC940DF@dericed.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8C6627AB-ACFA-4F7E-AC9D-9134A02895CA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sun, 1 Sep 2019 18:13:02 -0400
In-Reply-To: <7b4e6a16-0b2b-a6f9-2ae6-5b1ddd3c05f8@levkowetz.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, tools-discuss@ietf.org, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <3AAAEED4-87A9-4F5B-9910-55BABBDBBB15@dericed.com> <16851.1567355345@dooku.sandelman.ca> <7b4e6a16-0b2b-a6f9-2ae6-5b1ddd3c05f8@levkowetz.com>
X-Mailer: Apple Mail (2.3445.104.11)
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/LBle0gt7jYZJBcq_SOto1-uRWQk>
Subject: Re: [Cellar] [Tools-discuss] expressing both svg graphics and ascii-art fallback within an rfc2xml version 3 file?
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 01 Sep 2019 22:13:13 -0000

--Apple-Mail=_8C6627AB-ACFA-4F7E-AC9D-9134A02895CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Henrik, Julian,

> On Sep 1, 2019, at 12:46 PM, Henrik Levkowetz <henrik@levkowetz.com> =
wrote:
>=20
> Hi David,
>=20
> Response at the bottom:
>=20
> On 2019-09-01 18:29, Michael Richardson wrote:
>>=20
>> {reposting to tools-discuss}
>>=20
>> Hello cellar,
>>=20
>> The draft of FFV1 now uses xml2rfc version 3 as defined at
>> https://tools.ietf.org/html/rfc7991
>> <https://tools.ietf.org/html/rfc7991>. Presently in the markdown =
source of
>> the FFV1 draft, the math is maintained in both LaTeX expressions =
(which are
>> converted to SVG for inclusion in the RFC XML) as well as an Ascii =
Art
>> representation (heavily reliant on functions defined within the =
draft). For
>> example:=20
>>=20
>> vs
>>=20
>> r_{i} =3D floor( ( R_{i} * S_{i,C_{i}} ) / 2^8 )
>>=20
>> Whether in SVG or ascii art, this data is contained by the <artwork> =
node in
>> rfc2xml version 3. In https://tools.ietf.org/html/rfc7991#section-2.5
>> <https://tools.ietf.org/html/rfc7991#section-2.5> it states,=20
>>=20
>>   Alternatively, the "src" attribute allows referencing an external
>>   graphics file, such as a vector drawing in SVG or a bitmap graphic
>>   file, using a URI.  In this case, the textual content acts as a
>>   fallback for output representations that do not support graphics;
>>   thus, it ought to contain either (1) a "line art" variant of the
>>   graphics or (2) prose that describes the included image in =
sufficient
>>   detail.
>>=20
>> A bit later it says that SVG data may be encoded and stored within =
the
>> <artwork>=E2=80=99s @src attribute such as =20
>>=20
>>   o  As a data: URI, such as: <artwork type=3D"svg" src=3D"data:image/
>>      svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3=E2=80=A6">
>>=20
>> So from this I was hoping we could work on one draft rfc2xml version =
3 file
>> that could use the SVG image data or use the ascii art as a fallback; =
however
>> when I try to craft the <artwork> node with both such as:=20
>>=20
>>   <artwork type=3D"svg" =
src=3D"data:image/svg+xml,ENCODED_SVG_MATH_IMAGE_HERE=E2=80=9D>FALLBACK_AS=
CII_ART_HERE</artwork>
>>=20
>> then the output =E2=80=9Cv3-plaintext=E2=80=9D output of the =
conversion tool at
>> https://xml2rfc.tools.ietf.org/experimental.html
>> <https://xml2rfc.tools.ietf.org/experimental.html>, does not use the =
textual
>> content of the <artwork> node as a fallback but instead places a =
warning such
>> as=20
>>=20
>>   (Artwork only available as svg: No external link available, see
>>   draft-ietf-cellar-ffv1-08.html for artwork.)
>>=20
>> Is it feasible (recommended?) to have one rfc2xml XML document that =
could be
>> a source for both plaintext formats (using an ascii art fallback) and
>> non-plaintext formats such as HTML and PDF which would use the =
embedded SVG
>> data?
>=20
> Yes.  The specification of how to handle the text fallback in the RFC =
799x
> documents was in part contradictory, and also not as extensible and =
easily
> editable as one could wish.  It currently looks like rfc7991bis =
largely will
> follow the proposal discussed on the xml2rfc-dev list earlier this =
year, and
> captured in the xml2rfc implementation notes draft here:
>=20
> =
https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-note=
s-09#section-3.1.1 =
<https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-not=
es-09#section-3.1.1>
>=20
> which introduces an <artset> element which can contain multiple =
<artwork>
> elements with different type attributes, for instance (artwork and =
some
> details omitted:
>=20
>  <artset>
>    <artwork type=3D"svg" src=3D"..."/>
>    <artwork type=3D"ascii-art" ...>
> 	# ascii art
>    </artwork>
>  </artset>
>=20
> For more on this, and for a light introduction to the v3 schema, =
check:
> =
http://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html#artwork-alte=
rnatives =
<http://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html#artwork-alt=
ernatives>

Thanks, this was exactly the clarification that I needed! I see that =
with the <artset> use described here, that the v3-plaintext and v3-html =
outputs of https://xml2rfc.tools.ietf.org/experimental.html =
<https://xml2rfc.tools.ietf.org/experimental.html> use the appropriate =
<artwork> for the output. If you=E2=80=99re interested, my work to =
=E2=80=98build=E2=80=99 this XML from out markdown source is in =
https://github.com/FFmpeg/FFV1/pull/160 =
<https://github.com/FFmpeg/FFV1/pull/160>, and an example of <artset> in =
the output of this PR can be seen at =
https://gist.github.com/dericed/3063446119a6e5971ecad29027977073#file-draf=
t-ietf-cellar-ffv1-08-xml-L489-L502 =
<https://gist.github.com/dericed/3063446119a6e5971ecad29027977073#file-dra=
ft-ietf-cellar-ffv1-08-xml-L489-L502>.

Thanks so much,
Dave Rice


--Apple-Mail=_8C6627AB-ACFA-4F7E-AC9D-9134A02895CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
Henrik, Julian,<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Sep 1, 2019, at 12:46 PM, =
Henrik Levkowetz &lt;<a href=3D"mailto:henrik@levkowetz.com" =
class=3D"">henrik@levkowetz.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Hi David,</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Response at the =
bottom:</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">On 2019-09-01 =
18:29, Michael Richardson wrote:</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D"">{reposting to =
tools-discuss}<br class=3D""><br class=3D"">Hello cellar,<br =
class=3D""><br class=3D"">The draft of FFV1 now uses xml2rfc version 3 =
as defined at<br class=3D""><a =
href=3D"https://tools.ietf.org/html/rfc7991" =
class=3D"">https://tools.ietf.org/html/rfc7991</a><br =
class=3D"">&lt;https://tools.ietf.org/html/rfc7991&gt;. Presently in the =
markdown source of<br class=3D"">the FFV1 draft, the math is maintained =
in both LaTeX expressions (which are<br class=3D"">converted to SVG for =
inclusion in the RFC XML) as well as an Ascii Art<br =
class=3D"">representation (heavily reliant on functions defined within =
the draft). For<br class=3D"">example:<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><br =
class=3D"">vs<br class=3D""><br class=3D"">r_{i} =3D floor( ( R_{i} * =
S_{i,C_{i}} ) / 2^8 )<br class=3D""><br class=3D"">Whether in SVG or =
ascii art, this data is contained by the &lt;artwork&gt; node in<br =
class=3D"">rfc2xml version 3. In =
https://tools.ietf.org/html/rfc7991#section-2.5<br =
class=3D"">&lt;https://tools.ietf.org/html/rfc7991#section-2.5&gt; it =
states,<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""><br class=3D"">&nbsp;&nbsp;Alternatively, the "src" attribute =
allows referencing an external<br class=3D"">&nbsp;&nbsp;graphics file, =
such as a vector drawing in SVG or a bitmap graphic<br =
class=3D"">&nbsp;&nbsp;file, using a URI. &nbsp;In this case, the =
textual content acts as a<br class=3D"">&nbsp;&nbsp;fallback for output =
representations that do not support graphics;<br =
class=3D"">&nbsp;&nbsp;thus, it ought to contain either (1) a "line art" =
variant of the<br class=3D"">&nbsp;&nbsp;graphics or (2) prose that =
describes the included image in sufficient<br =
class=3D"">&nbsp;&nbsp;detail.<br class=3D""><br class=3D"">A bit later =
it says that SVG data may be encoded and stored within the<br =
class=3D"">&lt;artwork&gt;=E2=80=99s @src attribute such as &nbsp;<br =
class=3D""><br class=3D"">&nbsp;&nbsp;o &nbsp;As a data: URI, such as: =
&lt;artwork type=3D"svg" src=3D"data:image/<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;svg+xml,%3Csvg%20xmlns%3D%22http%=
3A%2F%2Fwww.w3=E2=80=A6"&gt;<br class=3D""><br class=3D"">So from this I =
was hoping we could work on one draft rfc2xml version 3 file<br =
class=3D"">that could use the SVG image data or use the ascii art as a =
fallback; however<br class=3D"">when I try to craft the &lt;artwork&gt; =
node with both such as:<span =
class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><br =
class=3D"">&nbsp;&nbsp;&lt;artwork type=3D"svg" =
src=3D"data:image/svg+xml,ENCODED_SVG_MATH_IMAGE_HERE=E2=80=9D&gt;FALLBACK=
_ASCII_ART_HERE&lt;/artwork&gt;<br class=3D""><br class=3D"">then the =
output =E2=80=9Cv3-plaintext=E2=80=9D output of the conversion tool =
at<br class=3D"">https://xml2rfc.tools.ietf.org/experimental.html<br =
class=3D"">&lt;https://xml2rfc.tools.ietf.org/experimental.html&gt;, =
does not use the textual<br class=3D"">content of the &lt;artwork&gt; =
node as a fallback but instead places a warning such<br class=3D"">as<span=
 class=3D"Apple-converted-space">&nbsp;</span><br class=3D""><br =
class=3D"">&nbsp;&nbsp;(Artwork only available as svg: No external link =
available, see<br class=3D"">&nbsp;&nbsp;draft-ietf-cellar-ffv1-08.html =
for artwork.)<br class=3D""><br class=3D"">Is it feasible (recommended?) =
to have one rfc2xml XML document that could be<br class=3D"">a source =
for both plaintext formats (using an ascii art fallback) and<br =
class=3D"">non-plaintext formats such as HTML and PDF which would use =
the embedded SVG<br class=3D"">data?<br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Yes. &nbsp;The specification of =
how to handle the text fallback in the RFC 799x</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">documents was in part =
contradictory, and also not as extensible and easily</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">editable as one could wish. =
&nbsp;It currently looks like rfc7991bis largely will</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">follow the proposal discussed on =
the xml2rfc-dev list earlier this year, and</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">captured in the xml2rfc =
implementation notes draft here:</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementat=
ion-notes-09#section-3.1.1" style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implemen=
tation-notes-09#section-3.1.1</a><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">which introduces an &lt;artset&gt; element which can contain =
multiple &lt;artwork&gt;</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">elements with different type attributes, for instance =
(artwork and some</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">details omitted:</span><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&nbsp;&lt;artset&gt;</span><br style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&nbsp;&nbsp;&nbsp;&lt;artwork type=3D"svg" =
src=3D"..."/&gt;</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&nbsp;&nbsp;&nbsp;&lt;artwork type=3D"ascii-art" =
...&gt;</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span class=3D"Apple-tab-span" style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: pre; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;">	</span><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D""># ascii art</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&nbsp;&nbsp;&nbsp;&lt;/artwork&gt;</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">&nbsp;&lt;/artset&gt;</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">For more on this, and for a =
light introduction to the v3 schema, check:</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"http://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html#artw=
ork-alternatives" =
class=3D"">http://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html#a=
rtwork-alternatives</a><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">Thanks, this was exactly the clarification =
that I needed! I see that with the &lt;artset&gt; use described here, =
that the v3-plaintext and v3-html outputs of&nbsp;<a =
href=3D"https://xml2rfc.tools.ietf.org/experimental.html" =
class=3D"">https://xml2rfc.tools.ietf.org/experimental.html</a>&nbsp;use =
the appropriate &lt;artwork&gt; for the output. If you=E2=80=99re =
interested, my work to =E2=80=98build=E2=80=99 this XML from out =
markdown source is in&nbsp;<a =
href=3D"https://github.com/FFmpeg/FFV1/pull/160" =
class=3D"">https://github.com/FFmpeg/FFV1/pull/160</a>, and an example =
of &lt;artset&gt; in the output of this PR can be seen at&nbsp;<a =
href=3D"https://gist.github.com/dericed/3063446119a6e5971ecad29027977073#f=
ile-draft-ietf-cellar-ffv1-08-xml-L489-L502" =
class=3D"">https://gist.github.com/dericed/3063446119a6e5971ecad2902797707=
3#file-draft-ietf-cellar-ffv1-08-xml-L489-L502</a>.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks so =
much,</div><div class=3D"">Dave Rice</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_8C6627AB-ACFA-4F7E-AC9D-9134A02895CA--


From nobody Fri Sep  6 08:08:30 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D6916120D07; Fri,  6 Sep 2019 08:08:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: cellar@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: cellar@ietf.org
Message-ID: <156778249282.21920.2305493713693863949@ietfa.amsl.com>
Date: Fri, 06 Sep 2019 08:08:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/wHC0f-h3owdNskTTF1nICg7JhaU>
Subject: [Cellar] I-D Action: draft-ietf-cellar-ffv1-09.txt
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 06 Sep 2019 15:08:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Codec Encoding for LossLess Archiving and Realtime transmission WG of the IETF.

        Title           : FFV1 Video Coding Format Version 0, 1, and 3
        Authors         : Michael Niedermayer
                          Dave Rice
                          Jerome Martinez
	Filename        : draft-ietf-cellar-ffv1-09.txt
	Pages           : 45
	Date            : 2019-09-06

Abstract:
   This document defines FFV1, a lossless intra-frame video encoding
   format.  FFV1 is designed to efficiently compress video data in a
   variety of pixel formats.  Compared to uncompressed video, FFV1
   offers storage compression, frame fixity, and self-description, which
   makes FFV1 useful as a preservation or intermediate video format.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cellar-ffv1/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-cellar-ffv1-09
https://datatracker.ietf.org/doc/html/draft-ietf-cellar-ffv1-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cellar-ffv1-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Sep  8 04:55:53 2019
Return-Path: <mcr@sandelman.ca>
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 08DA4120018 for <cellar@ietfa.amsl.com>; Sun,  8 Sep 2019 04:55:51 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 cKlay48wpWbP for <cellar@ietfa.amsl.com>; Sun,  8 Sep 2019 04:55:48 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E37712001E for <cellar@ietf.org>; Sun,  8 Sep 2019 04:55:48 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [88.214.187.115]) by relay.sandelman.ca (Postfix) with ESMTPS id 4FD021F459 for <cellar@ietf.org>; Sun,  8 Sep 2019 11:55:47 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 574BC2025; Sun,  8 Sep 2019 12:56:09 +0100 (WEST)
From: Michael Richardson <mcr@sandelman.ca>
To: cellar@ietf.org
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: message/rfc822
Content-Disposition: inline; filename=977
Content-Transfer-Encoding: 8bit
Content-Description: forwarded message
Date: Sun, 08 Sep 2019 12:56:09 +0100
Message-ID: <28860.1567943769@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/7SGH_DXo3ehLY9y6wl32yQVqNBY>
Subject: [Cellar] The upcoming transition to xml2rfc v3 (fwd) RFC Editor: The upcoming transition to xml2rfc v3
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 08 Sep 2019 11:55:51 -0000

Return-Path: <ietf-bounces@ietf.org>
Received: from tuna.sandelman.ca [2607:f0b0:f:3:216:3eff:fe7c:d1f3]
 by dooku.sandelman.ca with IMAP (fetchmail-6.3.26)
 for <mcr@sandelman.ca> (single-drop); Fri, 06 Sep 2019 21:41:01 +0300 (EEST)
Received: from tuna.sandelman.ca ([unix socket])
 by tuna (Cyrus git2.4.17+0-Debian-2.4.17+nocaldav-0+deb8u2) with LMTPA;
 Fri, 06 Sep 2019 00:22:36 -0400
X-Sieve: CMU Sieve 2.4
Received: from delivery.mtaroutes.com (delivery.mtaroutes.com [185.201.18.200])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by tuna.sandelman.ca (Postfix) with ESMTPS id BA4483818D
 for <mcr+ietf@sandelman.ca>; Fri,  6 Sep 2019 00:22:36 -0400 (EDT)
Received: from mail.ietf.org ([4.31.198.44])
 by mx135.antispamcloud.com with esmtps
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89)
 (envelope-from <ietf-bounces@ietf.org>) id 1i65mv-000CWG-Mz
 for mcr+ietf@sandelman.ca; Fri, 06 Sep 2019 06:23:58 +0200
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 11FDE120B34
 for <mcr+ietf@sandelman.ca>; Thu,  5 Sep 2019 21:23:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1567743836; bh=SE6VQ1u0/OurJBbWTfyXLb5mOs881K8mS3vajVkIvWI=;
 h=Date:From:To:Subject:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe:Cc;
 b=iVafiDTohmQduVJHy/SK+Njf5+b6fc1/gxNe/gRJB90Vy0A+tZxF1JTb/p55SS7qF
 8FmzFocShPd354WmwVJLIXe/JmHdjLHayvXh64klz2oWEmAdj8iCr8DB/BDfvNzBFE
 9JkswwmV3k6gKhojN9fqHNZw6pnxGGtBfKHVRagc=
X-Mailbox-Line: From ietf-bounces@ietf.org  Thu Sep  5 21:23:54 2019
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 8090A12007C;
 Thu,  5 Sep 2019 21:23:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1567743833; bh=SE6VQ1u0/OurJBbWTfyXLb5mOs881K8mS3vajVkIvWI=;
 h=Date:From:To:Subject:List-Id:List-Unsubscribe:List-Archive:
 List-Post:List-Help:List-Subscribe:Cc;
 b=fIkkMrGQY2ihO/bi5XkU+NKNAWJIUT42e68NBw3vH2d8Q18uJG1F+ez/Pt7MZO9XM
 +OCdMMG84uWrRJC+rzpPy2RGqo3n/+xAwIQFAbfTg3cVU9RlRKJXWvZDW1YmVmCLaC
 ExwoFy7/krLswF1a8/N/tR7PKONb8AYYX2TJq9BU=
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 00CFF12007C;
 Thu,  5 Sep 2019 21:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001,
 URIBL_BLOCKED=0.001] autolearn=ham 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 0k_cBrG6e_EP; Thu,  5 Sep 2019 21:23:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 373ED1208FA;
 Thu,  5 Sep 2019 21:23:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 6000)
 id 6A02DB80EAD; Thu,  5 Sep 2019 21:23:26 -0700 (PDT)
Date: Thu, 5 Sep 2019 21:23:25 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: RFC Interest <rfc-interest@rfc-editor.org>, ietf@ietf.org
Subject: The upcoming transition to xml2rfc v3
Message-ID: <20190906042325.GC12952@rfc-editor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A4bbRjrbAVrLvQC70IUOpxfhQ4I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
 <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
 <mailto:ietf-request@ietf.org?subject=subscribe>
Cc: irsg@irtf.org, rsoc@iab.org, IESG <iesg@ietf.org>, iab@iab.org,
 RFC Editor <rfc-editor@rfc-editor.org>
Errors-To: ietf-bounces@ietf.org
Sender: "ietf" <ietf-bounces@ietf.org>
Received-SPF: pass (mx135.antispamcloud.com: domain of ietf.org designates
 4.31.198.44 as permitted sender) client-ip=4.31.198.44;
 envelope-from=ietf-bounces@ietf.org; helo=mail.ietf.org; 
X-SPF-Result: mx135.antispamcloud.com: domain of ietf.org designates
 4.31.198.44 as permitted sender
Authentication-Results: antispamcloud.com;
 spf=pass smtp.mailfrom=ietf-bounces@ietf.org; dkim=pass header.i=ietf.org
X-Filter-Label: newsletter
X-MailAssure-Class: whitelisted
X-MailAssure-Evidence: sender
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0duM4P579sYYbdH8Mt+sPVWpSDasLI4SayDByyq9LIhVRJKuoL20070G
 U5Ufdh+41WqUuh2MpmQbQvmrab9RbAHqH6xvmyo++UsFY6JUjVh4shsxya8iQXED5vSUQ++rDser
 6nXFRBneIuQ/tHetyAjCO19LxTtRjq8KdnbboYd3WmuNA8WTybi1JN85FSnfKfltWGvLbCuZaQoe
 5UGcu4CliNXA8r3GwubHzFZFLD0hkVWClPVvbW5lVyQanRxw5nmS7Qi4DDvwnPe/m0ZwJguF4MXC
 BjASdP/gQilaCwuE7H2ZC56yr6xDfRL3L1neeyODJgPrCtC9pJVsir/Bwp2kDci70QkCOxa9CI+8
 v8i3KLTFpngmCzMfOMV6XuhaoWRIKsTuPqUeQKyAib+++enPmG9gFLeemzo5k4hIZa3cWkmx+1QV
 mJBBi3jMF/6P/LwqyT5p50x81ZKcmzCu2U2eiziRmrRLaxpyV/vMvHCOuf7kVjwr6h6NRWmP4+ZL
 RxjgXQ1cH0qbjA5HkG/mj+BSOGvIZvl3fTYm4ScQKyM0f3sqmmN5+4PiuNVZzZ62zzXdK3l/iDHX
 ZWhrbeGnTfKsvPTf8e8C/tpW4vqOOU3llgS6K9aAlnrXFI3hveFdl5yKIZYoOCMzT0aSo1aiylQv
 IK6BdVb2n98YLoZnO4CQgEodZYt3DvY+wudGBSvfRCwKIPJmWRKOBAndfLir+QvvmdPjycRVXO/e
 DmcrxEBncRSO9+vsLGsFgP6D4eeKdax4mImHwabrZm6PiQe0Mv8mTY4UHBMyDfwfNV6AKAQeIbtf
 63VNbf0lrvssY+k7AEc6cp7xnTnmmhMqOAGEEOfPVxpCiLjhZx+PXP8nm1O3v9J+eViTEmTa1h84
 LmoGGwmb0Vg+fXV4pEFqQcSpJwZWl7/9tWSDztd7rV7fQde5IRFsicyJMEhQFtD8PLoinns6biPS
 CArAigP6eur+34c=
X-Report-Abuse-To: spam@quarantine10.antispamcloud.com

Greetings,

With the RFC format transition approaching quickly, we want to share
some of the transition details.  

The RFC Editor will be switching to using xml2rfc v3 [0] [1] [2] to
create RFCs. (Authors do not have to change what they submit as an
Internet-Draft.)

There will be new publication formats (HTML, PDF, and text) and an XML
source file, which uses the v3 vocabulary as described in [3] and
[4]. 

Next week the RFC Editor's code base and database will be updated.
>From 16 September 2019, the RFC Editor will be ready to publish in the
new format.  See the transition details [6] for more information.  

For more details on why this change is taking place, see the "RFC
Format Framework” [5]. 

* How does this affect you?  
Please see the transition details page [6], especially if you
currently have a document in the RFC Editor queue [7].

* What if you find a bug in xml2rfc? 
Please add a ticket to the issue tracker [8] or send mail to the
xml2rfc-dev list [9].

[0] Tool: https://pypi.org/project/xml2rfc/
[1] Intro: https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html
[2] FAQ: https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html
[3] RFC 7991: https://www.rfc-editor.org/rfc/rfc7991
[4] Implementation Notes: https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-09
[5] RFC 7990: https://www.rfc-editor.org/rfc/rfc7990.txt
[6] Transition Details: https://www.rfc-editor.org/rse/wiki/doku.php?id=v3implementation 
[7] Current Queue: https://www.rfc-editor.org/current_queue.php
[8] Issue Tracker: https://trac.tools.ietf.org/tools/xml2rfc/trac/
[9] XML Development Mailing list: https://www.ietf.org/mailman/listinfo/xml2rfc-dev

Thank you.
RFC Editor


From nobody Thu Sep 12 05:11:30 2019
Return-Path: <pb@das-werkstatt.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 085711200DB for <cellar@ietfa.amsl.com>; Thu, 12 Sep 2019 05:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 icwfogtQCiTY for <cellar@ietfa.amsl.com>; Thu, 12 Sep 2019 05:11:27 -0700 (PDT)
Received: from zucker2.schokokeks.org (zucker2.schokokeks.org [178.63.68.90]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180811200CE for <cellar@ietf.org>; Thu, 12 Sep 2019 05:11:26 -0700 (PDT)
Received: from [IPv6:2001:4bca:11e:b318:f9a6:5182:205b:ebf5] ([2001:4bca:1039:f318:f9a6:5182:205b:ebf5]) (AUTH: PLAIN bubestinger@schokokeks.org, ) by zucker.schokokeks.org with ESMTPSA id 000000000000012E.000000005D7A35EB.0000078B; Thu, 12 Sep 2019 14:11:23 +0200
To: cellar@ietf.org
References: <156778249282.21920.2305493713693863949@ietfa.amsl.com>
From: "Peter B." <pb@das-werkstatt.com>
Message-ID: <3e8fd79b-3596-6bf4-4d8d-9f9b9a964045@das-werkstatt.com>
Date: Thu, 12 Sep 2019 14:11:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <156778249282.21920.2305493713693863949@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/iJCVroJw_DcN5liTaiNW-xeK0zY>
Subject: Re: [Cellar] I-D Action: draft-ietf-cellar-ffv1-09.txt
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Sep 2019 12:11:29 -0000

Hi,

It seems that the linebreaks in pseudo-code parts don't render correctly
(at least in TXT and HTML output):

  * https://www.ietf.org/id/draft-ietf-cellar-ffv1-09.txt

  * https://tools.ietf.org/html/draft-ietf-cellar-ffv1-09


For example:
  * 3.8.1.2.  Range Non Binary Values
  * 3.8.2.1.  Signed Golomb Rice Codes
  * 3.8.2.2.1.  Run Length Coding
  * 3.8.2.3.  Scalar Mode
  * ...


I haven't had time to look at the source yet, but wanted to check if anyone else is also seeing this?


Thanks and regards,
Peter


From nobody Thu Sep 12 05:34:06 2019
Return-Path: <lists@reto.ch>
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 4CAA2120052 for <cellar@ietfa.amsl.com>; Thu, 12 Sep 2019 05:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 97aRAHzQyXqk for <cellar@ietfa.amsl.com>; Thu, 12 Sep 2019 05:34:03 -0700 (PDT)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (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 093B5120041 for <cellar@ietf.org>; Thu, 12 Sep 2019 05:34:02 -0700 (PDT)
Received: from smtp7.infomaniak.ch (smtp7.infomaniak.ch [83.166.132.30]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id x8CCY0wZ006756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <cellar@ietf.org>; Thu, 12 Sep 2019 14:34:01 +0200
Received: from Castor ([IPv6:2a02:aa13:4680:f280:7d8b:4139:7be0:de0d]) (authenticated bits=0) by smtp7.infomaniak.ch (8.14.5/8.14.5) with ESMTP id x8CCXx70065957 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <cellar@ietf.org>; Thu, 12 Sep 2019 14:34:00 +0200
Date: Thu, 12 Sep 2019 14:34:00 +0200
From: Reto Kromer <lists@reto.ch>
To: cellar@ietf.org
X-Priority: 3
Message-ID: <r480Ps-10146i-7C288FF5EEF94EF3ABA7529BCA3AAFED@Castor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.4.3 (480)
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/z_fMqMJk2pyXFgbkGtSFPzjGcc0>
Subject: Re: [Cellar] I-D Action: draft-ietf-cellar-ffv1-09.txt
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Sep 2019 12:34:05 -0000

Peter B. wrote:

>It seems that the linebreaks in pseudo-code parts don't render
>correctly (at least in TXT and HTML output):

I guess, it's the "c" in "```c". Best regards, Reto


From nobody Mon Sep 16 10:19:43 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEDF120127; Mon, 16 Sep 2019 10:19:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: cellar@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: cellar@ietf.org
Message-ID: <156865437449.28094.1536573937825732846@ietfa.amsl.com>
Date: Mon, 16 Sep 2019 10:19:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/ZK9nuRc7vYJGGzU9Y6j8USqsr7E>
Subject: [Cellar] I-D Action: draft-ietf-cellar-ffv1-v4-06.txt
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 16 Sep 2019 17:19:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Codec Encoding for LossLess Archiving and Realtime transmission WG of the IETF.

        Title           : FFV1 Video Coding Format Version 4
        Authors         : Michael Niedermayer
                          Dave Rice
                          Jerome Martinez
	Filename        : draft-ietf-cellar-ffv1-v4-06.txt
	Pages           : 45
	Date            : 2019-09-16

Abstract:
   This document defines FFV1, a lossless intra-frame video encoding
   format.  FFV1 is designed to efficiently compress video data in a
   variety of pixel formats.  Compared to uncompressed video, FFV1
   offers storage compression, frame fixity, and self-description, which
   makes FFV1 useful as a preservation or intermediate video format.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cellar-ffv1-v4/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-cellar-ffv1-v4-06
https://datatracker.ietf.org/doc/html/draft-ietf-cellar-ffv1-v4-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cellar-ffv1-v4-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Sep 22 00:28:13 2019
Return-Path: <slhomme@matroska.org>
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 B1D3212003E for <cellar@ietfa.amsl.com>; Sun, 22 Sep 2019 00:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=matroska-org.20150623.gappssmtp.com
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 wP4PwNVtZJPb for <cellar@ietfa.amsl.com>; Sun, 22 Sep 2019 00:28:09 -0700 (PDT)
Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A26412002F for <cellar@ietf.org>; Sun, 22 Sep 2019 00:28:09 -0700 (PDT)
Received: by mail-pg1-x534.google.com with SMTP id u17so6123625pgi.6 for <cellar@ietf.org>; Sun, 22 Sep 2019 00:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matroska-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=KfKaBieVMtrS0bcGWRIKikRBi5ixbVHdLLbCIQIPCMI=; b=F2yz8e1kAcchGms5V3dueTVaGCJQrSronaAqKSqCBQ/7c8D1d98nzIDQSCHBnr52vP JYFpDKh2xnoZ6fcGB8e0Glyv8X8V5HCo52lfNZR1hlhAdvpUWqGIgDqRmxMf4KzDOi5x N4/T+7oiK6ZsCNceP+uZwiyNJWOAJepQ1CPNFisSe70y92lubjN+4Bp2mfQJHXRT5kDI niAdMvBLrFKmisV3XM+xcDwxMFQcHIaP1+6PZeh/KJny0KDluq5SvdwuWIfCdQaxGB4v pOhAcaJqoL0rt4KY3RQHNPKxgsXM654OU+Vsk/wXEpj6w7Y8yzV8LXfDfGC73TAL/ia3 mm3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=KfKaBieVMtrS0bcGWRIKikRBi5ixbVHdLLbCIQIPCMI=; b=lQs21RSm9jK1TtOF2VL8NrnR2LHjc6lwOw+G94pizHnTdgvdovWA2Pwzo9xpMfuFyw PpCE2jvwguVizQMYD7wNORuspB9gosDIp58lvVya+2eSHfj/w/m9ulAxWSthF61qeazh aRIIyXgPVfnIABvj/ujebIz81MfRx3ZNIEfP1y+KBIv1K0hnhGRVYS7NxW4zTjLoqpi1 PZ4vNux2cxJSAzNLgko4o4uh+N+ZODqRnA34Kcc0GOib1pwJfn77247QWf4B/13cHrhJ Fs3fwlQZ2XuRsD27neL1jL/U9huQ92Ay9VpGsohDOlDfgmlo45BL3+pUNIcQ587JfbC9 N7RA==
X-Gm-Message-State: APjAAAVa4svay5/pENisvyiTRYyKJRsNbWiFSXuAFyYk6XO3dh7B4G9B uFdSxUx+weZ/a29+Qedwd5+WUOxAFctcFbsx/tKhE0n+WjY=
X-Google-Smtp-Source: APXvYqwtOV1GjPXwW5Wj8mWs02s5z7wQvrb3InEP3K20oOXwrNvE0Crll8ZYpX4qqTitLK2y4vlC+3XDz0XVSXnPr20=
X-Received: by 2002:a17:90a:9d87:: with SMTP id k7mr14580479pjp.103.1569137288849;  Sun, 22 Sep 2019 00:28:08 -0700 (PDT)
MIME-Version: 1.0
References: <28860.1567943769@dooku.sandelman.ca>
In-Reply-To: <28860.1567943769@dooku.sandelman.ca>
From: Steve Lhomme <slhomme@matroska.org>
Date: Sun, 22 Sep 2019 09:27:56 +0200
Message-ID: <CAOXsMFLe0QTxgq6K5QeUaYaUXiuSy972tvsKiTyrS0LGtttXow@mail.gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/ElpUZcK4IQ1JVsx3eq5RfV92bU8>
Subject: Re: [Cellar] The upcoming transition to xml2rfc v3 (fwd) RFC Editor: The upcoming transition to xml2rfc v3
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 22 Sep 2019 07:28:12 -0000

Since we generate XML files in v2 and then generate HTML and TXT
versions, should we transition to generate v3 XML files and just
submit that ?

Le dim. 8 sept. 2019 =C3=A0 13:55, Michael Richardson <mcr@sandelman.ca> a =
=C3=A9crit :
>
>
>
>
> ---------- Forwarded message ----------
> From: RFC Editor <rfc-editor@rfc-editor.org>
> To: RFC Interest <rfc-interest@rfc-editor.org>, ietf@ietf.org
> Cc: irsg@irtf.org, rsoc@iab.org, IESG <iesg@ietf.org>, iab@iab.org, RFC E=
ditor <rfc-editor@rfc-editor.org>
> Bcc:
> Date: Thu, 5 Sep 2019 21:23:25 -0700
> Subject: The upcoming transition to xml2rfc v3
> Greetings,
>
> With the RFC format transition approaching quickly, we want to share
> some of the transition details.
>
> The RFC Editor will be switching to using xml2rfc v3 [0] [1] [2] to
> create RFCs. (Authors do not have to change what they submit as an
> Internet-Draft.)
>
> There will be new publication formats (HTML, PDF, and text) and an XML
> source file, which uses the v3 vocabulary as described in [3] and
> [4].
>
> Next week the RFC Editor's code base and database will be updated.
> >From 16 September 2019, the RFC Editor will be ready to publish in the
> new format.  See the transition details [6] for more information.
>
> For more details on why this change is taking place, see the "RFC
> Format Framework=E2=80=9D [5].
>
> * How does this affect you?
> Please see the transition details page [6], especially if you
> currently have a document in the RFC Editor queue [7].
>
> * What if you find a bug in xml2rfc?
> Please add a ticket to the issue tracker [8] or send mail to the
> xml2rfc-dev list [9].
>
> [0] Tool: https://pypi.org/project/xml2rfc/
> [1] Intro: https://tools.ietf.org/src/xml2rfc/trunk/cli/doc/xml2rfc3.html
> [2] FAQ: https://www.rfc-editor.org/materials/FAQ-xml2rfcv3.html
> [3] RFC 7991: https://www.rfc-editor.org/rfc/rfc7991
> [4] Implementation Notes: https://tools.ietf.org/html/draft-levkowetz-xml=
2rfc-v3-implementation-notes-09
> [5] RFC 7990: https://www.rfc-editor.org/rfc/rfc7990.txt
> [6] Transition Details: https://www.rfc-editor.org/rse/wiki/doku.php?id=
=3Dv3implementation
> [7] Current Queue: https://www.rfc-editor.org/current_queue.php
> [8] Issue Tracker: https://trac.tools.ietf.org/tools/xml2rfc/trac/
> [9] XML Development Mailing list: https://www.ietf.org/mailman/listinfo/x=
ml2rfc-dev
>
> Thank you.
> RFC Editor
>
>
>
>
> ---------- Forwarded message ----------
> From: Michael Richardson <mcr@sandelman.ca>
> To: cellar@ietf.org
> Cc:
> Bcc:
> Date: Sun, 08 Sep 2019 12:56:09 +0100
> Subject: [Cellar] The upcoming transition to xml2rfc v3 (fwd) RFC Editor:=
 The upcoming transition to xml2rfc v3
> _______________________________________________
> Cellar mailing list
> Cellar@ietf.org
> https://www.ietf.org/mailman/listinfo/cellar



--=20
Steve Lhomme
Matroska association Chairman


From nobody Mon Sep 23 18:53:16 2019
Return-Path: <mcr+ietf@sandelman.ca>
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 D0BFC1200DF for <cellar@ietfa.amsl.com>; Mon, 23 Sep 2019 18:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 4F5oxDzusN2e for <cellar@ietfa.amsl.com>; Mon, 23 Sep 2019 18:53:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DC231200DE for <cellar@ietf.org>; Mon, 23 Sep 2019 18:53:11 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3ADE63897D for <cellar@ietf.org>; Mon, 23 Sep 2019 21:51:20 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AA3AD764 for <cellar@ietf.org>; Mon, 23 Sep 2019 21:53:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cellar@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 23 Sep 2019 21:53:09 -0400
Message-ID: <29604.1569289989@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/JWlUMm8QbaGKzKikvWLG0tXu6sE>
Subject: [Cellar] DRAFT AGENDA for VIRTUAL INTERIM meeting 2019-09-24
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 24 Sep 2019 01:53:15 -0000

--=-=-=
Content-Type: text/plain


CELLAR -- DRAFT AGENDA for Virtual Interim Meeting
September 24, 2019     19:00 UTC
                       21:00 Amsterdam
                       15:00 NYC
                       12:00 San Francisco

   NOTE new regular time.

INFO:
   https://datatracker.ietf.org/meeting/interim-2019-cellar-08/session/cellar
   https://datatracker.ietf.org/doc/agenda-interim-2019-cellar-08-sessa/

WEB CONFERENCE:
   https://whereby.com/cellar-interim
   THERE IS NO TELEPHONE DIALIN (You can try this at any time.)
   These notes at: https://github.com/cellar-wg/chair-notes

1. Note Well.
2. Accept draft minutes from July 30 meeting (attached below)

3. Logistics for Meeting.
   2a) Etherpad for notes
       https://etherpad.ietf.org/p/notes-cellar-virtual?useMonospaceFont=true

   2b) APPEAR.IN is not called "whereby.com"
       https://whereby.com/cellar-interim

   2c) Roll call

4. WG status update
   * EBML -- STILL WAITING ON REVISED -11 document for AD evaluation.

5. Remining EBML issues, hoping for none.
      Issue #279 https://github.com/cellar-wg/ebml-specification/issues/279
      Pull request: https://github.com/cellar-wg/ebml-specification/pull/281

5. Work on Matroska issues.

6. Any other business.

====
CELLAR -- DRAFT AGENDA for Virtual Interim Meeting
August 27, 2019        19:00 UTC
	                       21:00 Amsterdam
	                       15:00 NYC
	                       12:00 San Francisco

	NOTE this is one hour earlier than last time!

Participants:
    1) Michael Richardson
    2) Martin Below
    3) Steve Lhomme
    4) Michael Niedermayer
    5) Dave Rice
    6) Reto Kromer
    7) Jerome Martinez
    8) Benjamin Turkus

Regrets:
    1) Moritz Bunkus


	INFO:
	   https://datatracker.ietf.org/meeting/interim-2019-cellar-07/session/cellar
	   https://datatracker.ietf.org/doc/agenda-interim-2019-cellar-07-sessa/

	WEB CONFERENCE:
	   https://appear.in/cellar-interim
	   THERE IS NO TELEPHONE DIALIN (You can try this at any time.)
	   These notes at: https://github.com/cellar-wg/chair-notes

	1. Note Well.
	2. Accept draft minutes from July 30 meeting (attached below)
	minutes accepted.
	Agenda amended to include FFV1.

	3. Logistics for Meeting.
	   2a) Etherpad for notes
	       https://etherpad.tools.ietf.org/p/notes-cellar-virtual?useMonospaceFont=true

	   2b) APPEAR.IN is now called "whereby.com"
	       https://whereby.com/cellar-interim

	   2c) Roll call

	4. WG status update
	   * EBML -- still waiting on revised -11 document for AD evaluation.
	   We had a lot of conversation last time about solving this logjam.
	   Much work on it 2019-08-26, is it done?

	5. Remining EBML issues, hoping for none.
	      Issue #279 https://github.com/cellar-wg/ebml-specification/issues/279
	      Pull request: https://github.com/cellar-wg/ebml-specification/pull/281
	ACTION: Dave will review the rest of the document to ensure that allowing Global Elements at
				Root Element is consistent with the rest of the document.
			(also will ping Moritz)

	5. FFV1
	--> https://mailarchive.ietf.org/arch/msg/cellar/noQ6X-9GPJ3yB3jSeLeHHMwOgh8
	--> how will SVG be sent to datatracker if the SVG are not embedded?
	-->

	6. Work on Matroska issues.

	ACTION: #335 Agree that NextUID is the way to use hard-linking, PrevUID is used as a safety for
				recovery of missing segments (optional).
	ACTION: #287 will get additional examples from Dave Rice.

	7. Any other business.

	====
	        CELLAR -- DRAFT AGENDA for Virtual Interim Meeting
	        July 30, 2019        20:00 UTC

	        Present:
	                1) Michael Richardson
	                2) Timothy B. Terriberry
	                3) Steve Lhomme
	                4) Martin Below
	                5) Dave Rice
	                6) Michael Niedermeier

	Regrets:
	            Jerome Martinez

	        INFO:
	           https://datatracker.ietf.org/meeting/interim-2019-cellar-06/session/cellar
	           https://datatracker.ietf.org/doc/agenda-interim-2019-cellar-06-sessa/

	        WEB CONFERENCE:
	           https://appear.in/cellar-interim
	           THERE IS NO TELEPHONE DIALIN (You can try this at any time.)
	           These notes at: https://github.com/cellar-wg/chair-notes

	        1. Note Well.
	                https://www.ietf.org/about/note-well/

	        2. Accept draft minutes from June 25 meeting (attached below)
	                No objections/changes, minutes passed.

	        3. Logistics for Meeting.
	           2a) Etherpad for notes
	               https://etherpad.tools.ietf.org/p/notes-cellar-virtual?useMonospaceFont=true

	           2b) APPEAR.IN for video and screen sharing.
	               https://appear.in/cellar-interim

	           2c) Roll call

	        4. WG status update
	           * EBML -- still waiting on revised -11 document for AD evaluation.
	        ACTION from last time:
	                       ==> issue #257, requested one more day to think about it.
	                                                The changes
	                    are fine in general, but want to make sure it precise enough. (MB)

	        We created issue #279 to introduce some new text to better explain what a Global Element is, and why it does not end an unlimited size Element.

	           * Thank for reposting of draft-ietf-cellar-tags-02,
	                 draft-ietf-cellar-matroska-03  and draft-ietf-cellar-codec-02

	           * The personal draft-weaver-cellar-flac-00 did not get reposted.
	             I believe that we adopted it, so it should have been reposted with a
	             draft-ietf-cellar-flac-00!

	        reposted today, thank you.

	        5. Any remining EBML issues.

	        none known.

	        6. ffv1-07 could be reposted in v3 format.
	        ACTION: mcr to ask DataTracker and RSE if they are ready for this.

	        7. Work on Matroska issues.

	        Closed issue #325 (merged).
	        Discussed issue #334 and related issue #308.

	        8. Any other business.

	        Matroska Pull request #318 will be on the agenda for next time.

	        Meeting will be moved to an hour earlier, until the time changes.
	        Currently it is 23:00 Berlin, so we will anchor the meeting to 22:00 Berlin time.





--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl2JdwUACgkQgItw+93Q
3WWBFQf9FrXAScgl74uyUl2YWJhck6RDPRGAK0jbleyBVsWIjt8YHwzG9W2yPNea
jF+0PXKak1WyJF78O15XyaH26RqhReptCmzvXEcgMGNcmeD2l6re1UiPk/NAfS7N
9qxTsluZgHpsFG+TZiCFn3mACzSqr/Q7g82sD/dObvW4w67+ok0ScUBb4cnSNsQf
I8sFgtGq/BPsrQByYRwA+F3CgrDSB5OHDnFhbiMmc+3pXSNZ7JOLt2F8AbydFOzH
yxbCJ0CZOmY9qUTZ/mvqJupORbEEy4u8eCKS2xskz01DusxzdaW6XkICxhocXq+P
Pt7OMkbW4hTiMwngwRfajiKWqCNoOw==
=fCAD
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Sep 24 12:19:19 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2171208ED; Tue, 24 Sep 2019 12:19:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: cellar@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: cellar@ietf.org
Message-ID: <156935275758.15745.12637124050151163558@ietfa.amsl.com>
Date: Tue, 24 Sep 2019 12:19:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/7lruOpfA7zLRwO7QAJqi7hkve3I>
Subject: [Cellar] I-D Action: draft-ietf-cellar-ebml-11.txt
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 24 Sep 2019 19:19:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Codec Encoding for LossLess Archiving and Realtime transmission WG of the IETF.

        Title           : Extensible Binary Meta Language
        Authors         : Steve Lhomme
                          Dave Rice
                          Moritz Bunkus
	Filename        : draft-ietf-cellar-ebml-11.txt
	Pages           : 49
	Date            : 2019-09-24

Abstract:
   This document defines the Extensible Binary Meta Language (EBML)
   format as a generalized file format for any type of data in a
   hierarchical form.  EBML is designed as a binary equivalent to XML
   and uses a storage-efficient approach to build nested Elements with
   identifiers, lengths, and values.  Similar to how an XML Schema
   defines the structure and semantics of an XML Document, this document
   defines how EBML Schemas are created to convey the semantics of an
   EBML Document.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-cellar-ebml/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-cellar-ebml-11
https://datatracker.ietf.org/doc/html/draft-ietf-cellar-ebml-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-cellar-ebml-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Sep 24 13:10:11 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: cellar@ietf.org
Delivered-To: cellar@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3209112004E; Tue, 24 Sep 2019 13:10:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: cellar@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.102.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <156935580905.15598.6511389190770051137@ietfa.amsl.com>
Date: Tue, 24 Sep 2019 13:10:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/odhwsIyyDIvsGqCDbbc43p2T3rY>
Subject: [Cellar] Codec Encoding for LossLess Archiving and Realtime transmission (cellar) WG Virtual Meeting: 2019-10-22 CHANGED
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 24 Sep 2019 20:10:09 -0000

MEETING DETAILS HAVE CHANGED.  SEE LATEST DETAILS BELOW.

The Codec Encoding for LossLess Archiving and Realtime transmission (cellar) Working Group will hold
a virtual interim meeting on 2019-10-22 from 21:00 to 22:00 Europe/Paris.

Agenda:
(No agenda submitted)

Information about remote participation:
https://appear.in/cellar-interim