<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.xiph.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bearwin</id>
	<title>XiphWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.xiph.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bearwin"/>
	<link rel="alternate" type="text/html" href="https://wiki.xiph.org/Special:Contributions/Bearwin"/>
	<updated>2026-06-01T10:19:52Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://wiki.xiph.org/index.php?title=SpeexRTP&amp;diff=10729</id>
		<title>SpeexRTP</title>
		<link rel="alternate" type="text/html" href="https://wiki.xiph.org/index.php?title=SpeexRTP&amp;diff=10729"/>
		<updated>2009-11-24T06:23:50Z</updated>

		<summary type="html">&lt;p&gt;Bearwin: /* Speex over RTP */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Speex over RTP ===&lt;br /&gt;
&lt;br /&gt;
While [[Ogg]] is the native file format for speex data, an RTP encapsulation is a natural fit with the codec&#039;s low latency [http://www.rushessay.com essay] design.&lt;br /&gt;
&lt;br /&gt;
Fortunately, unlike [[Vorbis]] and [[Theora]], [[Speex]] has no required setup headers, so the application is easy. A [http://speex.org/drafts/draft-herlein-speex-rtp-profile-02.txt draft exists]. It just needs to be reviewed and then taken through the formal ratification process with the IETF.&lt;br /&gt;
&lt;br /&gt;
[[Category:Speex]]&lt;/div&gt;</summary>
		<author><name>Bearwin</name></author>
	</entry>
</feed>