<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - IETF - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ IETF Articles feed</description>
    <item>
      <title>Article: Colliding Communities, Cloud Native, and Telecommunications Standards</title>
      <link>https://www.infoq.com/articles/cloud-native-telecom-standards/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=IETF-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/cloud-native-telecom-standards/en/headerimage/generatedHeaderImage-1670275668650.jpg"/&gt;&lt;p&gt;What happens when an ecosystem driven from the bottom up collides with a community characterized by top-down development? The 5g broadband cellular network standard by the 3rd Generation Partnership Project (3GPP), the Network Function Virtualization (NFV) standard by the European Telecommunications Standards Institute (ETSI), and the Service Function Chain RFC (request for comments) are examples.&lt;/p&gt; &lt;i&gt;By W. Watson&lt;/i&gt;</description>
      <category>TCP</category>
      <category>HTTP</category>
      <category>Standardization</category>
      <category>Cloud Native Computing Foundation</category>
      <category>Protocol</category>
      <category>IETF</category>
      <category>Cloud Native Architecture</category>
      <category>Cloud</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 07 Dec 2022 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/cloud-native-telecom-standards/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=IETF-articles</guid>
      <dc:creator>W. Watson</dc:creator>
      <dc:date>2022-12-07T09:00:00Z</dc:date>
      <dc:identifier>/articles/cloud-native-telecom-standards/en</dc:identifier>
    </item>
  </channel>
</rss>
