similar to: draft-herlein-speex-rtp-profile-01

Hello, What's the purpose of the 'sr' sdp parameter ? The sample rate is already given in the a=rtpmap line ? Simon Le dim 29/06/2003 à 12:12, philkerr@elec.gla.ac.uk a écrit : > 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

All: Attached please find yet another RTP profile revision (v5). You can also find the document at: http://www.herlein.com/downloads/speex/docs/ Changes: - added vbr, cng, ebw, sr optional parameters to MIME - added vbr, cng, ebw a=fmtp options for SDP use - added required document attributes for submission to IETF and IANA (format and author contact information). Note that we

> Otherwise Greg, can you send the latest version of the RTP draft so I > can put it on the site (the current one is getting old)? Attached for all to see. Greg -------------- next part -------------- Internet Engineering Task Force Greg Herlein Internet Draft Jean-Marc Valin draft-herlein-speex-rtp-profile-06

The latest revision of the draft profile for use of Speex in RTP is attached. We plan on submitting this - or a modified version of this, based on immediate feedback - to the IETF on Monday for consideration at the next meeting. Major differences in this revision are: - removed the discussion in the MIME section. It's a duplicate of the SDP discussion anyway, and may or may not match the

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

The latest revision of the draft RTP Profile is attached for review. This will be submitted to the IETF Audio-Video Transport Working Group for consideration immediately, so if you have any more comments, let us know. In addition, we will be applying for an official MIME type. Note that the AVP code and the MIME type in this latest revision have been changed from "SPX" to

Hi, We'd like to announce the first draft for the Speex RTP profile. It was written essentially by Greg Herlein, with some help from Simon Morlat and I. We'd like to get some feedback on it before it is sent to the IETF. Basically this will allow all SIP based VoIP applications using Speex to inter-operate. For those interested, there's already Simon's LinPhone (www.linphone.org)

Alfred E. Heggestad wrote: > <...> > > 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 on it also after it > has been submitted, but we would like to get the input from the Speex > community first.. > thanks for all the input. please find attached an updated version of the draft. I

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 Emanuel Gon?alves wrote: > Do not forget to add the "Copying conditions" to the RFC. > > Check

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

All: The latest draft RTP Payload Format for Speex is available via the IETF. See below for details. Greg ---------- Forwarded message ---------- Date: Tue, 09 Mar 2004 15:56:23 -0500 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-herlein-avt-rtp-speex-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. <p>

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

Here my comments: Page 3: To be compliant with this specification, implementations MUST support 8 kHz sampling rate (narrowband)" and SHOULD support 8 kbps bitrate. The sampling rate MUST be 8, 16 or 32 kHz. There is a type above after (narrowband), there is a " extra character. I don't understand what is the motivation to specify "SHOULD support 8 kbps

Ohh... Nice! This is new in 1.0.1, isn't it? It doesn't seem to be included in the reference manual yet, though. Thanks! Tom <p>Jean-Marc Valin (jean-marc.valin@hermes.usherb.ca) wrote: > > OK, this is how it works: > > The encoder calls speex_encode any number of times and then calls > speex_bits_insert_terminator before sending the bits. > > The

Hi, I have a few questions/remarks about the draft, in particular about the SDP usage of Speex (section 5): - Which samplerate should be used if you receive something like m=3Daudio 8008 RTP/AVP 97 a=3Drtpmap:97 speex/8000 a=3Dfmtp:97 sr=3D16000;ebw=3Dultra - There is an inconsistency in the description of the 'penh'parameter. According to the description,

comment inline. On Wed, 16 May 2007, Jean-Marc Valin wrote: >> Page 3: >> >> To be compliant with this specification, implementations MUST support >> 8 kHz sampling rate (narrowband)" and SHOULD support 8 kbps bitrate. >> The sampling rate MUST be 8, 16 or 32 kHz. >> >> There is a type above after (narrowband), there is a " extra

Hi, I have a question about section 3.4 of the RTP payload draft: > Speex codecs [11] are able to detect the the bitrate from the > payload and are responsible for detecting the 20 msec boundaries > between each frame. This suggests that you can encode some frames with Speex, pass the compressed bits to the decoder, and you'll get the output - without having to do external