similar to: Fwd: [codec] WG Review: Internet Wideband Audio Codec (codec)

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.

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

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

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 folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

Hi folks, here's a press release (yes, sorry, sorry) regarding what's going on with Xiph at the current IETF meeting. Every time we're asked 'why haven't you standardized any of your codecs through the IETF?' we explain that we've been trying for coming up on ten years. This release is about the latest step. If we (along with the other companies supporting

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, some good news from IETF :) /alfred -------------- next part -------------- An embedded message was scrubbed... From: The IESG <iesg-secretary at ietf.org> Subject: [AVT] Protocol Action: 'RTP Payload Format for the Speex Codec' to Proposed Standard Date: Mon, 18 May 2009 06:26:11 -0700 (PDT) Size: 3867 Url:

-------- Original-Nachricht -------- Betreff: [87all] IETF 87 Technical Plenary Experiment Datum: Mon, 22 Jul 2013 13:15:23 -0700 Von: IAB Chair <mailto:iab-chair at ietf.org> <iab-chair at ietf.org> Antwort an: ietf at ietf.org An: 87all at ietf.org The OPUS codec, defined in RFC 6716, can scale from low bit-rate narrowband speech to very high quality stereo

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

FYI, the Ogg Opus encapsulation is now RFC 7845: https://tools.ietf.org/html/rfc7845 -------- Forwarded Message -------- Subject: [codec] RFC 7845 on Ogg Encapsulation for the Opus Audio Codec Date: Fri, 29 Apr 2016 19:47:28 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org CC: drafts-update-ref at iana.org, codec at ietf.org, rfc-editor at

After much bureucracy in the IETF hierarchies and sort of chaos-like organization, it seems I have got the matter so far that a four-week last call will be issued so that application/ogg finally becomes a standard. Don't jump of joy just yet, but I have feelings that it actually may happen now. :-) The "last call" is not yet issued! (They started discussing adding this MIME-type in

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)

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

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

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

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

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