similar to: Updated Vorbis RTP I-D

Hi all, Below is the Vorbis RTP Internet Draft as sent to the AVT working group of the IETF. Comments and feedback is still welcomed from the Vorbis community. Cheers Phil ---------------------------8<-----------------8<------------------------ Network Working Group Phil Kerr Internet-Draft The Ogg Vorbis January 07, 2003 Community / OpenDrama

Hi All, Please find below an updated Vorbis-RTP Internet Draft document for review and discussion at the Xiph IRC meeting on Saturday. The changes in this version have been: Codebook caching mechanism Expanded SDP parameters Expanded MIME section Expanded introduction Packet loss section Minor tweaks and clarity changes to text There are probably some minor tweaks to the formatting needed

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Hi everybody, this is an update on the developed Ogg IETF standard documents and their status. All of these documents are in the process of discussion and have not yet been accepted as standards. <p>The following Internet-Drafts (I-Ds) have been prepared for standardisation and submitted to the IETF: 1) an I-D requesting to register "application/ogg" as a mime-type written by

Hi all, Please find below an updated Speex Internet Draft document. It would be good if we could book some time for discussion on Speex at the IETF meeting in Vienna (scheduled for 14th July). The cutoff for submission is 9:00am EDT, (GMT -04:00), 30th June. Comments and feedback welcomed! Regards Phil

Hi all, I'm in the final stages of putting a new Vorbis RTP draft together, the new sections are below. There are a number of open questions: 1.) At present there is a 16 bit length field for the codebooks. As they are spec'd as being unbound in length, but typically around 15K, are there situations where they may be greater than 64KB? The size limit can be extended to 2MB as there

Hi! What happened to this document? Was it just left dying in the IETF system? Tor --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the

Hi. I got bored of writing papers last week so I decided to write an app for sending and receiving multicast vorbis streams over RTP. A first version is available here: http://www.cdt.luth.se/~rolle/vorbis/ (I use the JOrbis decoder, so you need Java 2 with Javasound, e.g. JDK1.3. Since the decoding is done in Java, you probably need at least 300-350 MHz. Works with the IBM JDK1.3 on Linux on a

Hi. I got bored of writing papers last week so I decided to write an app for sending and receiving multicast vorbis streams over RTP. A first version is available here: http://www.cdt.luth.se/~rolle/vorbis/ (I use the JOrbis decoder, so you need Java 2 with Javasound, e.g. JDK1.3. Since the decoding is done in Java, you probably need at least 300-350 MHz. Works with the IBM JDK1.3 on Linux on a

Looks good to me. Jean-Marc Alfred E. Heggestad a ?crit : > Hi > > Please find an updated version of the Speex I-D attached. The only > change is addition of the copyright conditions in Appendix A, > as requested by Ivo. > > Many thanks for your input. > > I will give you a few more days before submitting to AVT working group > > > /alfred > > Ivo

Hi all We are about to send an updated version of the internet draft "RTP Payload Format for the Speex Codec" to the IETF AVT working group. Before submitting we would like your input, if you have any comments or input please send them to the mailing list. If we don't get any comments in 1 week (by 22. May 2007) we will go ahead and submit it to the IETF. Of course you can comment

(hello all, this is my first writing. so please bear with me if I'm wrong anywhere.) orry to break too lately, but how is the RTP payload submission is going? could we see the new payload at March IETF? I agree that it would be fairy straightforward to make an RTP payload for ogg vorbis, assuming raw packets, AFAIK. using physical bitstream is, in this case, not adequate by the reasons in

Hello to all speex developers, I have question regarding payload length of narrowband speex in RTP. I were watching tcpdump of the xlite softphone and have found that it uses weird payload length namely 75 Bytes I went through various source and without success. To be clear: For 8000Hz sample in 20 ms that is 160 samples per frame. This makes 50 frames per sec. modes bit-rate 8 kbit/s

Good day, FYI, I've just sent the attached email to IETF to progress our I-Ds. There are also links to updated documents in this email. Cheers, Silvia. -------- Original Message -------- Subject: New I-Ds for Ogg technologies (Vorbis over RTP, Ogg file format, Mimetypes) Date: Sun, 12 Jan 2003 01:36:31 +1100 From: Silvia Pfeiffer <Silvia.Pfeiffer@csiro.au> Organization: CSIRO To: AVT

Good day, FYI, I've just sent the attached email to IETF to progress our I-Ds. There are also links to updated documents in this email. Cheers, Silvia. -------- Original Message -------- Subject: New I-Ds for Ogg technologies (Vorbis over RTP, Ogg file format, Mimetypes) Date: Sun, 12 Jan 2003 01:36:31 +1100 From: Silvia Pfeiffer <Silvia.Pfeiffer@csiro.au> Organization: CSIRO To: AVT

i tried asterisk ilbc codec against kphone. when the call got connected, i started to immediately get these kind of message to the console: WARNING[14350]: File codec_ilbc.c, Line 141 (ilbctolin_framein): Huh? An ilbc frame that isn't a multiple of 52 bytes long from RTP (50)? WARNING[14350]: File codec_ilbc.c, Line 141 (ilbctolin_framein): Huh? An ilbc frame that isn't a multiple of

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

http://www.xiph.org/ogg/vorbis/doc/draft-moffitt-vorbis-rtp-00.txt This is the Internet-Draft I'll be submitting tomorrow and hopefully presenting at the March IETF meeting. If you see anything major, let me know right away, I'll be submitting this in the morning. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

I'm currently implementing A rtp header info and using speex for audio. can someone tell me what the rtp payload type value is for speex. i've checked the submitted speex draft and it says its beyond its scope and i can't find anything in RFC3550 that might suggest what it is. any help would be appreciated thank you, Greg --------------------------------- Boardwalk for $500?