<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>IPv6 | 面条的草稿箱</title><description>无原创，纯转发</description><link>http://drafts.miantiao.me</link><item><title>互联网往事：为何我们从 IPv4 直接跳到了 IPv6？我们都熟悉 IPv4 和 IPv6，但你是否好奇过 IPv5 去了哪里？实际上，IPv5 确实存在过，它也被称为互联网流协议 (ST)，是一个诞生于上世纪 70 年代末的实验性协议，专为实时数据流传输 (例如早期的网络电话) 而设计.它与 IPv4 一样使用 32 位地址，但并非其替代品，更像是一个功能扩展. 然而，随着宽带技术的崛起，网络带宽和延迟问题得到了有效解决，使得 IPv5 的专门设计显得多余.因此，这个协议最终被历史所尘封. 为了避免版本号上的混淆，当 IPv4 的下一代协议正式推出时，便直接命名为 IPv6.原文链接：</title><link>http://drafts.miantiao.me/posts/35</link><guid isPermaLink="true">http://drafts.miantiao.me/posts/35</guid><pubDate>Mon, 24 Nov 2025 05:00:29 GMT</pubDate><content:encoded>&lt;b&gt;互联网往事：为何我们从 IPv4 直接跳到了 &lt;/b&gt;&lt;mark class=&quot;highlight&quot;&gt;&lt;b&gt;IPv6&lt;/b&gt;&lt;/mark&gt;&lt;b&gt;？&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;我们都熟悉 IPv4 和 &lt;mark class=&quot;highlight&quot;&gt;IPv6&lt;/mark&gt;，但你是否好奇过 IPv5 去了哪里？&lt;br /&gt;&lt;br /&gt;实际上，IPv5 确实存在过，它也被称为互联网流协议 (ST)，是一个诞生于上世纪 70 年代末的实验性协议，专为实时数据流传输 (例如早期的网络电话) 而设计.&lt;br /&gt;&lt;br /&gt;它与 IPv4 一样使用 32 位地址，但并非其替代品，更像是一个功能扩展. 然而，随着宽带技术的崛起，网络带宽和延迟问题得到了有效解决，使得 IPv5 的专门设计显得多余.&lt;br /&gt;&lt;br /&gt;因此，这个协议最终被历史所尘封. 为了避免版本号上的混淆，当 IPv4 的下一代协议正式推出时，便直接命名为 &lt;mark class=&quot;highlight&quot;&gt;IPv6&lt;/mark&gt;.&lt;br /&gt;&lt;br /&gt;原文链接：&lt;a href=&quot;https://www.tomshardware.com/networking/ipv5-and-the-internet-stream-protocol-a-data-streaming-experiment-rendered-unnecessary-by-broadband&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;https://www.tomshardware.com/networking/ipv5-and-the-internet-stream-protocol-a-data-streaming-experiment-rendered-unnecessary-by-broadband&quot;&gt;https://www.tomshardware.com/networking/ipv5-and-the-internet-stream-protocol-a-data-streaming-experiment-rendered-unnecessary-by-broadband&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;/search/result?q=%23IPv5&quot; title=&quot;#IPv5&quot;&gt;#IPv5&lt;/a&gt; &lt;a href=&quot;/search/result?q=%23IPv6&quot; title=&quot;#IPv6&quot;&gt;#IPv6&lt;/a&gt; &lt;a href=&quot;/search/result?q=%23%E7%BD%91%E7%BB%9C%E5%8D%8F%E8%AE%AE&quot; title=&quot;#网络协议&quot;&gt;#网络协议&lt;/a&gt; &lt;a href=&quot;/search/result?q=%23%E4%BA%92%E8%81%94%E7%BD%91%E5%8E%86%E5%8F%B2&quot; title=&quot;#互联网历史&quot;&gt;#互联网历史&lt;/a&gt;&lt;a class=&quot;tgme_widget_message_link_preview&quot; href=&quot;https://www.tomshardware.com/networking/ipv5-and-the-internet-stream-protocol-a-data-streaming-experiment-rendered-unnecessary-by-broadband&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;IPv5 wasn&apos;t a general purpose Internet Protocol like IPv4 or IPv6, and was never ratified as such, but it would give birth to the first VOIP hardware.&quot;&gt;
  
  &lt;div class=&quot;link_preview_site_name accent_color&quot;&gt;Tom&apos;s Hardware&lt;/div&gt;
  &lt;img class=&quot;link_preview_image&quot; alt=&quot;The industry skipped from IPv4 to IPv6, leaving IPv5 and the Internet Stream Protocol to the annals of history — a data streaming…&quot; src=&quot;https://drafts.miantiao.me/static/https://cdn4.telesco.pe/file/t6kMAQ-c-LzkB4my_Nnn4NWCjmnVNb71zJ5k3Tmfis3EX_oPiQXR0rIJ3hRBCfOVi3oL_Rp3GDBkTU7KD9A1SurQr4BB9h0T5pgFE87sZKrzb6kCcmu79MsJxaGYVrrPdz0MEENOkDzOSUpZaKJUizsLKBGHhjOy5S0C-yDa5O4DVjUB0v_Xz97Wmq_JLW4tusSMYxmCpmgcBhPS3kvQ6L9atVZzmXMSmmBLpuJr8g5Qhkf4u98WD25xbXVRJBGxt7Lukcl1mfDimCGwiytN5Az04KSL8xTn2MqcTg_6EoYYRXz-AATCt0G-qPGqTMOPZaojWrvONnuhKIbcgZU7Wg.jpg&quot; width=&quot;1200&quot; height=&quot;630&quot; loading=&quot;eager&quot; /&gt;
  &lt;div class=&quot;link_preview_title&quot;&gt;The industry skipped from IPv4 to &lt;mark class=&quot;highlight&quot;&gt;IPv6&lt;/mark&gt;, leaving IPv5 and the Internet Stream Protocol to the annals of history — a data streaming…&lt;/div&gt;
  &lt;div class=&quot;link_preview_description&quot;&gt;IPv5 wasn&apos;t a general purpose Internet Protocol like IPv4 or &lt;mark class=&quot;highlight&quot;&gt;IPv6&lt;/mark&gt;, and was never ratified as such, but it would give birth to the first VOIP hardware.&lt;/div&gt;
&lt;/a&gt;</content:encoded></item></channel></rss>