search for: casner

All: My presentation to the IETF on the proposed Speex payload format did not occur. Details below. Progress continues, though, towards getting the Speex payload format approved. Greg ---------- Forwarded message ---------- Date: Fri, 21 Mar 2003 08:58:23 -0800 (PST) From: Stephen Casner <casner@acm.org> To: Greg Herlein <gherlein@herlein.com> Cc: avt@ietf.org Subject: Re: [AVT] Speex: Apologies for Missed Meeting Greg, > To those expecting my presentation yesterday on the Speex codec, > I apologize for not being there. I was caught out in the traffic > mess...

...t; -> "Because" 8 References: Your reference to RFC2119 of 1 Introduction got lost. [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [1] in 6 Security Considerations will then be [2]: [2] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A transport protocol for real-time applications," RFC 1889, January 1996. Add this one: [3] Handley, M. "Guidelines for Writers of RTP Payload Format Specifications" RFC 2736, December 1999. Cheers, Jochen...

...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 List <avt@ietf.org>, casner@acm.org, csp@isi.edu,mankin@psg.com Hello everybody, everal new I-Ds have been submitted from the Ogg community this week. The intention of our submissions is to gain IETF standards on the freely available and open media technologies that are developed in the Ogg community (http://www.xiph.org/)....

...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 List <avt@ietf.org>, casner@acm.org, csp@isi.edu,mankin@psg.com Hello everybody, everal new I-Ds have been submitted from the Ogg community this week. The intention of our submissions is to gain IETF standards on the freely available and open media technologies that are developed in the Ogg community (http://www.xiph.org/)....

...I think it will also be passed soon. The RFC and IANA registration of this mimetype will probably be published soon enough. Linus ---------- Forwarded message ---------- Date: Thu, 23 Jan 2003 20:30:41 -0800 From: Allison Mankin <mankin@psg.com> To: Silvia.Pfeiffer@csiro.au, avt@ietf.org, casner@acm.org, csp@isi.edu Cc: harald@alvestrand.no Subject: [AVT] Re: New I-Ds for Ogg technologies (Vorbis over RTP, Ogg file format, Mimetypes) Silvia, AVT WG, Chairs, We IESG passed draft-walleij-ogg-mediatype-08.txt as a Proposed Standard today. It had had a four week Last Call some time bac...

...which sources are allowed to reach it. 7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. ITU-T Recommendation G.722.1, available online from the ITU bookstore at http://www.itu.int. 3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 4. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Messa...

...urces are allowed to reach it. <p>7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. ITU-T Recommendation G.722.1, available online from the ITU bookstore at http://www.itu.int. 3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 4. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Messa...

...hentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Messa...

...hentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 8. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Messa...

...ed to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. <p>8. Normative References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 20...

...hentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 8. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Messa...

...June 2007 > > > 9. References > > 9.1. Normative References > > [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate > Requirement Levels", BCP 14, RFC 2119, March 1997. > > [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. > Jacobson, "RTP: A Transport Protocol for Real-Time > Applications", STD 64, RFC 3550, July 2003. > > [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session > Description Protocol&qu...

...ge 17] Internet-Draft Speex May 2007 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006....

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

...ed to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. <p>8. Normative References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 20...

...ed sources, but the processing cost of > the authentication itself may be too high. > > > 8. Normative References > > 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP > 9, RFC 2026, October 1996. > > 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: > A Transport Protocol for real-time applications", RFC 1889, > January 1996. > > 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail > Extensions (MIME) Part One: Format of Internet Message Bo...

On Tue, Dec 17, 2002 at 11:55:21PM -0800, Greg Herlein wrote: > If such a thing happens, discussion of the RTP profile draft > would be most welcome - please get responses back to the > list! Now, if this were finalised before the conference then we could do a demo and use it for broadcasting the lectures streams around the world... What is currently the best way of doing this? I'm

...ge 17] Internet-Draft Speex June 2007 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006....

...ge 15] Internet-Draft Speex April 2007 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", STD 64, RFC 3550, July 2003. [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session Description Protocol", RFC 4566, July 2006....

...flows in the client applications. <p>9 Acknowledgments This document is a continuation of draft-moffitt-vorbis-rtp-00.txt. The MIME type section is a continuation of draft-short-avt-rtp- vorbis-mime-00.txt Thanks to the AVT, Ogg Vorbis Communities / Xiph.org including Steve Casner, Ramon Garcia, Pascal Hennequin, Ralph Jiles, Tor-Einar Jarnbjo, Colin Law, John Lazzaro, Jack Moffitt, Colin Perkins, Barry Short, Mike Smith. <p>10 Normative References 1. The Ogg Encapsulation Format Version 0 (RFC 3533), S. Pfeiffer. 2. Key words for use in RFCs to Indica...