similar to: Speex RTP Profile at the IETF

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

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

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

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 all, Please find below the -01 update to draft-herlein-speex-rtp-profile, as submitted to the IETF. Regards Phil <p>-------------------8<-----------------------------------8<--------------------- <p><p>Internet Engineering Task Force Greg Herlein Internet Draft Jean-Marc Valin

Looks good. Two things though: - I think the draft should be names -02 since the last one was -01 (I'm pretty sure). - The header in the current document should be changed (they say -01) Jean-Marc Le lun 01/03/2004 à 20:17, Greg Herlein a écrit : > > > > Is this the latest draft? > > > >

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

>>>>> "Greg" == Greg Herlein <gherlein@herlein.com> writes: Greg> The IETF has already assigned -02: ... to indicate it's Greg> expired. I'll ask if they want to use -02 or -03. They posted a policy statement a couple of weeks back. The expired notice is to be replaced by the next version of the draft if any is forthcoming. So it'll be -02.

Dear all, We are excited to announce that the our CELLAR working group charter for the standardization of FFV1, Matroska, and FLAC has been made available for external review. What this means is that it is now under review and available for comment to the wider IETF community. Please send any comments you might have(including statement of support)to the IESG mailing list by November 9, 2015.

Dear members of the flac-dev list, I'm writing to ask for feedback from the FLAC community regarding the possibility of standardizing the FLAC specification through the Internet Engineering Task Force. I'm working with MediaArea on the PREFORMA project which focuses on building conformance checkers for Matroska and FFV1. Since Matroska and FFV1 are not yet formally standardized, this

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

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

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

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Today at 17:40-19:40 Eastern Standard Time (22:40-00:40 UTC) the IETF will be holding a Birds of a Feather session to discuss creating a working group for developing a next generation video codec for Internet use. Remote participation is open to everyone. This would be an effort somewhat similar to what we used to create the Opus audio codec. The IETF provides an open standardization process and

Hi all, I'm writing in my capacity as co-chair of the CELLAR working group of the IETF, which is tasked with the standardization of the FLAC specification. I posted about the initial creation of the working group in 2015, and I am wondering if any of the developers on this list are also subscribed to the IETF CELLAR list ( https://mailarchive.ietf.org/arch/search/?email_list=cellar). At the

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

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>