similar to: RTP Payload for Vorbis Audio: draft-moffitt-vorbis-rtp-00.txt

Hi Jack, > You're comments are welcome. Here they are... 3.1 RTP Header Payload Type (PT): I don't see an alternative to using a value of the dynamic range (96-127). IIRC, other ranger are reserved for fixed values assigned by IETF. "A dynamic payload type MUST be used - i.e., one in the range [96,127]." 3.2 Payload Header If you refer to RFC2119, please keep the capital

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

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 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, Apologies in advance, this email is quite long. I've prepared an updated Vorbis RTP Internet Draft, which is a continuation of draft-moffitt-vorbis-rtp-00.txt which can be found below. If this new draft gets the ok I'd like to submit this to the AVT WG later this week. There are a number of changes over the original I-D, notably the changing of the M bit function in the RTP

FYI, the Opus RTP payload format is now RFC7587: https://tools.ietf.org/html/rfc7587 Cheers, Jean-Marc -------- Forwarded Message -------- Subject: [payload] RFC 7587 on RTP Payload Format for the Opus Speech and Audio Codec Date: Tue, 30 Jun 2015 16:33:17 -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

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

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

Hi all, Please find below an I-D for the proposed registration of MIME type audio/rtp-vorbis. All comments most welcome. Barry <p>-----------8<------------- Network Working Group Barry Short Internet-Draft The Ogg Vorbis Community / OpenDrama Expires: July 7, 2003 January 7, 2003 <p>

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

On Wed, 16 May 2007, Jean-Marc Valin wrote: >>> The main idea is that Speex supports many bit-rates, but for one reason >>> or another, some modes may be left out in implementations (e.g. for RAM >>> or network reasons). What we're saying here is that you should make an >>> effoft to at least support (and offer) the 8 kbps mode to maximise >>>

FYI, -------------- next part -------------- An embedded message was scrubbed... From: Colin Perkins <csp at csperkins.org> Subject: Working group last call: draft-ietf-avt-rtp-speex-05.txt Date: Mon, 31 Mar 2008 22:25:03 +0100 Size: 2054 Url: http://lists.xiph.org/pipermail/speex-dev/attachments/20080331/289739db/attachment.eml

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

(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

On 5/31/07, Alfred E. Heggestad <aeh@db.org> wrote: > Could you let me know where to insert this statement in the xml > document? I'm no expert, but I recommend adding it in the Full Copyright Statement section. More or less like this: Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as

On 6/1/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > No, keep as is. It is definitely not public domain, since it's > BSD-licensed and "patent-free" will open futile and unnecessary > discussions (on what it's supposed to mean) at the IETF. I was under the impression that Speex, like Vorbis and FLAC had its specification under the PD, and only the

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, 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)

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