From: Petter Reinholdtsen <pere@hungry.com>
Date: Wed, 12 Sep 2012 11:44:28 +0000 (+0000)
Subject: New post.
X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/dc09b6a3f42637cf183789d01eb474af7c2cdc96?ds=sidebyside

New post.
---

diff --git a/blog/data/2012-09-12-ietf-opus-codec.txt b/blog/data/2012-09-12-ietf-opus-codec.txt
new file mode 100644
index 0000000000..8573c87e4c
--- /dev/null
+++ b/blog/data/2012-09-12-ietf-opus-codec.txt
@@ -0,0 +1,23 @@
+Title: IETF standardize its first multimedia codec: Opus
+Tags: english, frikanalen, multimedia, video
+Date: 2012-09-12 13:50
+
+<p>Yesterday, IETF announced the publication of of
+<a href="http://tools.ietf.org/html/rfc6716">RFC 6716, the Definition
+of the Opus Audio Codec</a>, a low latency, variable bandwidth, codec
+intended for both VoIP, film and music.  This is the first time, as
+far as I know, that IETF have standardized a multimedia codec.  In
+<a href="http://tools.ietf.org/html/rfc3533">RFC 3533</a>, IETF
+standardized the OGG container format, and it has proven to be a great
+royalty free container for audio, video and movies.  I hope IETF will
+continue to standardize more royalty free codeces, after ISO and MPEG
+have proven incapable of securing everyone equal rights to publish
+multimedia content on the Internet.</p>
+
+<p>IETF require two interoperating independent implementations to
+ratify a standard, and have so far ensured to only standardize royalty
+free specifications.  Both are key factors to allow everyone (rich and
+poor), to compete on equal terms on the Internet.</p>
+
+<p>Visit the <a href="http://opus-codec.org/">Opus project page</a> if
+you want to learn more about the solution.</p>