https://4sysops.com/archives/ipv6-part-2-new-features-routing/

Routing路由选择

In the last post of my IPv6 series, I outlined the main reason why you should now get started with IPv6: IPv6 will come soon to your network whether you like it or not. Network engineers have a few other reasons to offer, and this is the topic of the next two articles. The new IPv6 features are not really new because the protocol has already existed for more than 10 years. For this reason, I won’t just repeat the feature descriptions, which you can read on countless other sites, but I will outline my view about the significance of these enhancements.

Large address space

While the other new IPv6 features are all nice to have, the new large address space is certainly the main (perhaps the only) reason why IPv6 will come.An IPv4 address consists of 32 bits; the IPv4 address space, therefore, allows 232 addresses. An IPv6 address is four times as long and has 128 bits. Thus, in theory, IPv6 allows 2128 = 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. This corresponds to 655,570,793,348,866,943,898,599 (6.5×1023) addresses for every square meter of the Earth’s surface.

To be honest, I am not really impressed by these numbers. We are now entering the nano technology age, which means that we will have more and more, much smaller, communication devices than the IPv6 inventors have anticipated. Considering that a cubic meter of ideal gas contains around 1025 atoms, the number of 1023 IP addresses per square meter appears to be relatively small. I know this sounds like science fiction, but, for the inventors of IPv4, the Internet as we know it today certainly was science fiction at their time. We needed about 30 years to use up all of the IPv4 addresses. My gut tells me that the IPv6 addresses won’t last that long.

Hierarchical addressing

The Internet address classes of IPv4 allow hierarchical addressing to a certain extent. Hierarchical addressing makes routing more efficient because it reduces the size of routing tables. However, considering that the computation power of routers increased at a higher rate than the growth of the Internet, this was not really a problem.

Nevertheless, it is quite likely that the Internet will now grow at a higher rate than ever before, not only because the total population of the emerging markets (especially China and India) far exceeds the population in the developed world but also because the new type of devices (mobile phones, tablets, ebook readers, TV sets, etc.) also require IP addresses. Thus IPv6’s new hierarchical addressing capabilities are certainly important. And here the IPv6 inventors did not really scrimp. Of the 128 bits of an IPv6 address, 64 bits are used for hierarchical addressing, 48 bits for the public topology, and 16 bits for the site topology. The latter means that you can work with hierarchical addresses within your organization.

Better support for Quality of Service (QoS)

IPv4 has limited support for Quality of Service (QoS)—that is, real-time delivery of data through the Type of Service (TOS) field.

One problem of QoS in IPv4 pertains to TCP and UDP port identification, which is not possible if the IPv4 packet is encrypted.

The other problem is that QoS in IPv4 is not really standardized.

The IPv6 header has the Flow Label field, which allows QoS handling that is independent of the payload.

While this new feature is technically interesting, in practice QoS is quite problematic for traffic on the public Internet. You might have heard of the stir that the alleged Google-Verizon deal caused. Google intended to pay Verizon to prioritize their traffic.

The main question is how you decide which traffic has priority. Is it justified that you have to wait for the latest 4sysops article to show up on your screen just because some teens clogged the net with their YouTube videos? And if you pay for QoS, how can you measure that your traffic really has a higher priority? One thing is for sure, if QoS really comes, then the complexity level of the Internet will be raised again by one or two bars, which means more work for IT pros.

In the next post I will talk about IPv6 IPsec and the IPv6 LAN features.

IPv6 tutorial 2 New features: Routing的更多相关文章

  1. IPv6 tutorial 3 New features: IPsec and LAN features

    https://4sysops.com/archives/ipv6-tutorial-part-3-new-features-ipsec-and-lan-features/ In the last p ...

  2. IPv6 tutorial – Part 8: Special addresses

    https://4sysops.com/archives/ipv6-tutorial-part-8-special-addresses/ The special IPv6 addresses disc ...

  3. IPv6 tutorial – Part 6: Site-local addresses and link-local addresses

    https://4sysops.com/archives/ipv6-tutorial-part-6-site-local-addresses-and-link-local-addresses/ In ...

  4. IPv6 tutorial – Part 7: Zone ID and unique local IPv6 unicast addresses

    The zone ID is used to distinguish ambiguous link-local and site-local addresses. Unique local IPv6 ...

  5. Quartz Tutorial 11 - Miscellaneous Features of Quartz

    文章目录 Plug-Ins Quartz提供了一个接口(org.quartz.spi.SchedulerPlugin) 用于插入附加的功能. 与Quartz一同发布的,提供了各种实用功能的插件可以在o ...

  6. IPv6 tutorial 4 IPv6 address syntax

    https://4sysops.com/archives/ipv6-tutorial-part-4-ipv6-address-syntax/ Now that you know about the n ...

  7. IPv6 tutorial – Part 5: Address types and global unicast addresses

    https://4sysops.com/archives/ipv6-tutorial-part-5-address-types-and-global-unicast-addresses/ In my ...

  8. IPv6 tutorial 1 Get started now

    https://4sysops.com/archives/ipv6-part-1-get-started-now/ You’ve probably heard the news that the In ...

  9. Python Tutorial 学习(一)--Whetting Your Appetite

    Whetting Your Appetite [吊你的胃口]... 这里就直接原文奉上了... If you do much work on computers, eventually you fin ...

随机推荐

  1. 移动前端开发之viewport的深入理解(转载)

    本文为转载文章,原文网址:http://www.cnblogs.com/2050/p/3877280.html 在移动设备上进行网页的重构或开发,首先得搞明白的就是移动设备上的viewport了,只有 ...

  2. 13_ServletContext对象

    [简介] ServletContext即Servlet上下文对象,该对象表示当前的web应用环境信息,一个Web应用只会创建一个ServletContext对象. Web容器启动的时候,它会为每个We ...

  3. asp.net导出excel较为简约的代码

    ds为数据源 Response.Buffer = true; Response.AppendHeader("Content-Disposition", "attachme ...

  4. 配置Apache+Mysql+Php

    以下操作均在Debian 6.0 64bit 环境root权限下进行,如果提示权限不足请切换至root用户或者sudo,本人比较喜欢自行安装,因为安装的过程中能最小化安装而且能够知道安装了什么,然后可 ...

  5. AD,Group

    DataTable dtUser = GetEmptyDT(); Dictionary<DirectoryEntry, string> test1 = GetUserAndGroup(cl ...

  6. Beyond Compare 使用介绍

    Beyond Compare 背景 平时工作中对于源代码都是使用SVN来管理,在线状态下工作的很好,但是有时候离线状态下,对于多个版本之间的代码合并就比较麻烦.尤其是涉及到多人协作时更是如此. 所以找 ...

  7. 前端资源多个产品整站一键打包&包版本管理(二)——如何在bower的配置文件加上注释

    问题: 当一个工程里面有好几个项目,每个项目引用同一个包,但是不同的名字,例如在bower中 fancybox 跟 jquery.fancybox 是一样的,我们只需要下载其中的一个版本,而打包工作不 ...

  8. 推荐一个优秀的前端框架——Bootstrap

    Bootstrap是Twitter推出的一个开源的用于前端开发的工具包.它由Twitter的设计师Mark Otto和Jacob Thornton合作开发,是一个CSS/HTML框架.Bootstra ...

  9. OpenSessionInViewFilter与org.springframework.dao.InvalidDataAccessApiUsageException

    报错:org.springframework.dao.InvalidDataAccessApiUsageException: Write operations are not allowed in r ...

  10. PHPCMS 核心代码与 www 分离部署

    为了满足更多用户二次开发的兴趣与爱好,同时,为了更加安全.可以通过修改入口代码的包含方式来让主程序和www程序分开. 先看下面目录结构: (图1) 我们需要将 phpcms 目录和 index.php ...