RFC 3533 Errata: Difference between revisions
No edit summary |
(added two new errata) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
'''Title''' | '''Title''' | ||
It should be simply "The Ogg Encapsulation Format". The last bit certainly doesn't build trust on Ogg. | It should be simply "The Ogg Encapsulation Format". The last bit certainly doesn't build trust on Ogg. [I disagree; Silvia] | ||
'''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.; Silvia] | ||
'''Section 4, paragraph 4''' | '''Section 4, paragraph 4''' | ||
| Line 16: | Line 16: | ||
per logical bitstream." should read "It also uses two additional header packets | per logical bitstream." should read "It also uses two additional header packets | ||
per logical bitstream. | per logical bitstream. | ||
'''non-decreasing granulepos''' | |||
The RFC needs to specify non-decreasing granulepos - see discussion at https://trac.xiph.org/ticket/1306. | |||
'''incomplete packets on the e_o_s page of a logical bitstream''' | |||
The RFC needs to clarify that incomplete packets on the e_o_s page of a logical bitstream are undesired and will be ignored - see discussion at https://trac.xiph.org/ticket/1308. | |||
== Additions == | == Additions == | ||
| Line 24: | Line 32: | ||
* how to deal with large pagerate differentials? | * how to deal with large pagerate differentials? | ||
[[Category:Ogg]] | |||
Latest revision as of 16:12, 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. [I disagree; Silvia]
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.; Silvia]
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.
non-decreasing granulepos
The RFC needs to specify non-decreasing granulepos - see discussion at https://trac.xiph.org/ticket/1306.
incomplete packets on the e_o_s page of a logical bitstream
The RFC needs to clarify that incomplete packets on the e_o_s page of a logical bitstream are undesired and will be ignored - see discussion at https://trac.xiph.org/ticket/1308.
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?