<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] RFC 2250 Q</title></head><body>
<blockquote type="cite" cite>Content-class:
urn:content-classes:message<br>
Content-Type: multipart/alternative;<br>
<x-tab>
</x-tab>boundary="----_=_NextPart_001_01C74C50.B5ECF64E"<br>
</blockquote>
<blockquote type="cite" cite><font face="Arial"
size="-1">Does the Live555 Media server follow RFC
2250 to transport video?</font></blockquote>
<div><br></div>
<div>Yes, but note that this RFC is only for MPEG-1 or 2 Video RTP
streams. Transport of other kinds of stream - including MPEG-4,
H.263+ and H.264 - is defined using other RFCs (but we support those
also).</div>
<div><br></div>
<div>To implement RFC 2250, we use the
"MPEG1or2VideoRTPSource/Sink" classes (for Video Elementary
Streams), the "MPEG1or2AudioRTPSource/Sink" classes (for
Audio Elementary Streams), and the "SimpleRTPSource/Sink"
classes (for Transport Streams).</div>
<div><br></div>
<div>Note also the numerous demo applications that use these
classes.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>