ref: 958285e690bf8be738769a4e63c620563c9dcec0
parent: 8fd7c3fc8cede177aae1c61283d4853cc15a9a65
author: Ralph Giles <[email protected]>
date: Fri Sep 26 11:55:44 EDT 2014
Add wording about additional binary data in comment headers. From the codec wg mailing list thread https://www.ietf.org/mail-archive/web/codec/current/msg03107.html
--- a/doc/draft-ietf-codec-oggopus.xml
+++ b/doc/draft-ietf-codec-oggopus.xml
@@ -1166,6 +1166,15 @@
user comments than than could possibly fit in the packet.
</t>
+<t>
+Immediately following the user comment list, the comment header MAY
+ contain zero-padding or other binary data which is not specified here.
+If the least-significant bit of the first byte of this data is 1, then editors
+ SHOULD attempt to preserve the contents of this data when updating the tags,
+ but if this bit is 0, all such data MAY be treated as padding, and truncated
+ or discarded as desired.
+</t>
+
<section anchor="comment_format" title="Tag Definitions">
<t>
The user comment strings follow the NAME=value format described by