RFC 3533 Errata: Difference between revisions
Jump to navigation
Jump to search
(cat) |
(comment on "Standards Track") |
||
| Line 9: | Line 9: | ||
'''Category''' | '''Category''' | ||
It should NOT be Informational but Standards Track. | It should NOT be Informational but Standards Track. [This is not possible because it is not a standard developed by the IETF. It will only go on Standards Track if it comes out of an IETF working group.] | ||
'''Section 4, paragraph 4''' | '''Section 4, paragraph 4''' | ||
Revision as of 16:07, 25 February 2008
This is the official errata page for RFC 3533 "The Ogg Encapsulation Format Version 0".
Errata
Title
It should be simply "The Ogg Encapsulation Format". The last bit certainly doesn't build trust on Ogg.
Category
It should NOT be Informational but Standards Track. [This is not possible because it is not a standard developed by the IETF. It will only go on Standards Track if it comes out of an IETF working group.]
Section 4, paragraph 4
The sentence "It also uses two additional header pages per logical bitstream." should read "It also uses two additional header packets per logical bitstream.
Additions
Ideas for new stuff in 3533bis:
- the multiplexing should be rewritten, in particular to give a seek algorithm
- how to deal with large pagerate differentials?