Hello,<br><br><div><span class="gmail_quote">On 4/9/07, <b class="gmail_sendername">Dave Singer</b> <<a href="mailto:singer@apple.com">singer@apple.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div>WARNING: I have CC'd the co-authors of the RFC, as I think
they might like to see the discussion, comment on my answers, and
possibly correct me. I also have a question whether there is a
typo in the RFC...</div>
<div><br></div>
<div>* * * * *</div>
<div><br></div>
<div><br></div>
<div>Henry</div>
<div><br></div>
<div>these are all great questions. Let me see how many I can
answer.</div>
<div><br></div>
<div>Overall, the RFC was struggling with the issue that there is no
'uniform' naming of codecs; the namespace for codecs is
dependent on the container format, so products that do container
conversion have to have tables of code matches. ugh.
That's why the RFC is as it is.</div>
<div><br></div>
<div>The RFC suggests that updated information would be done with
RFCs, which is a little heavy. The RFC as written formally
applies to 3GPP files and 3GPP2 files, but the definitions are
applicable for all ISO-family files. </div>
<div><br></div>
<div>As you'll see below, 3GPP has also defined it for avc1 in
MP4-family containers, but no spec. or registration authority provides
a pointer. We might want to ask IANA whether we could add
something to the MIME registry.</div><span class="q">
<div><br></div>
<div><br></div>
<div>At 11:37 +0300 8/04/07, Henri Sivonen wrote:</div>
<blockquote type="cite"><br>
* Theora video and Vorbis audio in Ogg container.
(application/ogg; .ogg)<br>
* Dirac video and Vorbis audio in Ogg container.
(application/ogg; .ogg)<br>
* Theora video and Vorbis audio in Matroska container.
(video/x-matroska; .mkv)<br>
* Dirac video and Vorbis audio in Matroska container.
(video/x-matroska; .mkv)</blockquote>
<div><br></div></span>
<div>My understanding is that the Ogg container is 'specific' to these
codecs, and therefore the codecs parameter is not needed. But I
am not an Ogg or Matroska expert; perhaps they could chime
in?</div></div></blockquote><div><br>No. The containers are independent of the codecs put inside.<br><br>However, whether software, that supports Ogg or Matroska containers will actually be able to "play" other codecs is another issue altogether.
<br> </div>[...]<br><br><br>See ya<br></div><br clear="all"><br>-- <br> Charles Iliya Krempeaux, B.Sc.<br><br> charles @ <a href="http://reptile.ca">reptile.ca</a><br> supercanadian @ <a href="http://gmail.com">gmail.com
</a><br><br> developer weblog: <a href="http://ChangeLog.ca/">http://ChangeLog.ca/</a><br><br>