Hi all, The IETF has a final draft of our RFC at ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes from 3534 to 5334 - funny!). If you have anything in need of change, speak up now. I have one question in particular: Ogg.k.ogg.k: is the kate codec parameter now down to 8 bytes? If so, it's ok, since I've already made that change. Cheers, Silvia.
ogg.k.ogg.k at googlemail.com
2008-Aug-15 08:16 UTC
[ogg-dev] final changes to mimetypes rfc
> I have one question in particular: Ogg.k.ogg.k: is the kate codec > parameter now down to 8 bytes? If so, it's ok, since I've already made > that change.Yes, it is now \200kate\0\0\0, and the remaining 0 is now deemed a reserved 0 byte in all headers, rather than part of the signature. I think I've changed all the docs/wiki to reflect this - anything still showing the old 9 byte signature I'll fix if I see. Thanks
Cool, thanks very much. Cheers, Silvia. On Fri, Aug 15, 2008 at 6:16 PM, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote:>> I have one question in particular: Ogg.k.ogg.k: is the kate codec >> parameter now down to 8 bytes? If so, it's ok, since I've already made >> that change. > > Yes, it is now \200kate\0\0\0, and the remaining 0 is now deemed a > reserved 0 byte in all headers, rather than part of the signature. > I think I've changed all the docs/wiki to reflect this - anything still > showing the old 9 byte signature I'll fix if I see. > > Thanks >
2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>:> Hi all, > > The IETF has a final draft of our RFC at > ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes > from 3534 to 5334 - funny!). > > If you have anything in need of change, speak up now. > > I have one question in particular: Ogg.k.ogg.k: is the kate codec > parameter now down to 8 bytes? If so, it's ok, since I've already made > that change. >Just one small question, 10.3: "In particular, .ogg is used for Ogg files that contain only a Vorbis bitstream, while .spx is used for Ogg files that contain only a Speex bitstream." Should that be a "Vorbis I" bitstream, or is it intentionally left open? -- imalone
On Fri, Aug 15, 2008 at 8:42 PM, Ian Malone <ibmalone at gmail.com> wrote:> 2008/8/15 Silvia Pfeiffer <silviapfeiffer1 at gmail.com>: >> Hi all, >> >> The IETF has a final draft of our RFC at >> ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes >> from 3534 to 5334 - funny!). >> >> If you have anything in need of change, speak up now. >> >> I have one question in particular: Ogg.k.ogg.k: is the kate codec >> parameter now down to 8 bytes? If so, it's ok, since I've already made >> that change. >> > > Just one small question, 10.3: "In particular, .ogg is used for Ogg > files that contain only a Vorbis bitstream, while .spx is used for Ogg > files that contain only a Speex bitstream." > > Should that be a "Vorbis I" bitstream, or is it intentionally left open?Technically it is a Vorbis I bitstream, but I think we should leave that flexible. Any other opinions? Cheers, Silvia.