similar to: Update on IETF RFC

Good day, FYI, I've just sent the attached email to IETF to progress our I-Ds. There are also links to updated documents in 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

Good day, FYI, I've just sent the attached email to IETF to progress our I-Ds. There are also links to updated documents in 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

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

The IETF passed the application/ogg MIME type some days ago. I couldn't bring you the news earlier because of the MS SQL worm that has been wreaking havoc all over my local networks. The IETF wants some clarifications in Silivias draft for the Ogg stream format, but apart from that I think it will also be passed soon. The RFC and IANA registration of this mimetype will probably be published

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>

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 all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

Hi all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

Hmm, I know what you mean. I've actually taken these sentences out of Monty's specifications. The first one refers to the page size of max. ~64 kByte and the second one to the logical subdivision of packets into segments of 255 Byte size. I'm not sure how to rephrase that properly though. Maybe it's good as it stands: that it is recommended to have 4-8 kByte size, but expected more

Hmm, I know what you mean. I've actually taken these sentences out of Monty's specifications. The first one refers to the page size of max. ~64 kByte and the second one to the logical subdivision of packets into segments of 255 Byte size. I'm not sure how to rephrase that properly though. Maybe it's good as it stands: that it is recommended to have 4-8 kByte size, but expected more

The transport type application/ogg may now be used in applications. The IANA has assigned it in their namespace, so start adding it at will. See mail below. Linus ---------- Forwarded message ---------- Date: Mon, 10 Feb 2003 12:23:47 -0800 From: IANA <iana@iana.org> To: triad@df.lth.se Cc: Allison Mankin <mankin@psg.com>, Scott Bradner <sob@harvard.edu> Subject: RFC-to-be:

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

On Fri, 27 Feb 2009, Jean-Marc Valin wrote: > Hi Aymeric, > > Yes, I'm receiving the emails but haven't had enough time to look into > the details yet. I've seen you responded to many comments, so what are > the ones for which we still need to respond? Summary is there: https://datatracker.ietf.org/idtracker/ballot/2837/ As I understand: we need to change

[pardon me if this retreads some ground, but I'm just getting up to speed on this issue] so am I to understand -- application/ogg is for downloading, and will invoke an app that supposedly can parse *any* ogg file -- audio/vorbis is for streaming -- but this is narrowly defined as vorbis audio only. Presumably the thinking is that a streaming application is likely to be less

This is my previous conversation with Colin Perkins at IETF regarding audio/vorbis. For interested parties. Last two paragraphs are the most interesting ones. Linus -----Vidarebefordrat meddelande----- From: Colin Perkins <csp@isi.edu> To: Linus Walleij <triad@df.lth.se> Subject: Re: Regarding non-streaming Ogg Date: 20 Jun 2001 16:17:34 -0400 --> Linus Walleij writes:

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

Hi Jean-Marc, Alfred and Greg, Are you receiving the mails from IETF about draft-ietf-avt-rtp-speex The mails are not coming from AVT mailing list, but I think we are all 3 part of a minimal list (draft-ietf-avt-rtp-speex at tools.ietf.org) dedicated to latest discussion about the draft. I have answered some questions, but there are small changes and adaptation still required to the ietf