svn commit: r44186 - head/en_US.ISO8859-1/books/handbook/advanced-networking
Dru Lavigne
dru at FreeBSD.org
Fri Mar 7 19:59:51 UTC 2014
Author: dru
Date: Fri Mar 7 19:59:50 2014
New Revision: 44186
URL: http://svnweb.freebsd.org/changeset/doc/44186
Log:
Initial pass through IPv6 Introduction.
It needs a second pass and a mention of how FreeBSD is leading
the way with IPv6-only.
The rest of this chapter needs a tech review by someone
who knows more about IPv6 as the last two sections are
still unclear on why/when someone would do this.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Mar 7 19:36:09 2014 (r44185)
+++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Fri Mar 7 19:59:50 2014 (r44186)
@@ -4257,69 +4257,32 @@ Received 264951 bytes in 0.1 seconds</sc
</authorgroup>
</info>
- <para><acronym>IPv6</acronym>, also known as
- <acronym>IPng</acronym> <quote><acronym>IP</acronym> next
- generation</quote>, is the new version of the well known
+ <para><acronym>IPv6</acronym> is the new version of the well known
<acronym>IP</acronym> protocol, also known as
- <acronym>IPv4</acronym>. &os; includes the <link
- xlink:href="http://www.kame.net/">KAME</link>
- <acronym>IPv6</acronym> reference implementation. &os; comes
- with everything needed to use <acronym>IPv6</acronym>. This
- section focuses on getting <acronym>IPv6</acronym> configured
- and running.</para>
-
- <para>In the early 1990s, people became aware of the rapidly
- diminishing address space of <acronym>IPv4</acronym>. Given
- the expansion rate of the Internet, there were two major
- concerns:</para>
-
- <itemizedlist>
- <listitem>
- <para>Running out of addresses. For years the use of
- RFC1918 private address space (<systemitem
- class="ipaddress">10.0.0.0/8</systemitem>, <systemitem
- class="ipaddress">172.16.0.0/12</systemitem>, and
- <systemitem
- class="ipaddress">192.168.0.0/16</systemitem>) and NAT
- has slowed down the exhaustion. Even though, there are
- very few remaining IPv4 addresses. The Internet
- Assigned Numbers Authority (<acronym>IANA</acronym>) has
- issued the last of the available major blocks to the
- Regional Registries. Once each Regional Registry runs
- out, there will be no more available and switching to
- <acronym>IPv6</acronym> will be critical.</para>
- </listitem>
-
- <listitem>
- <para>Every block of IPv4 addresses allocated required
- routing information to be exchanged between many routers
- on the Internet, and these routing tables were getting
- too large to allow efficient routing.</para>
- </listitem>
- </itemizedlist>
-
- <para><acronym>IPv6</acronym> deals with these and many other
- issues by providing the following:</para>
+ <acronym>IPv4</acronym>. <acronym>IPv6</acronym> provides several advantages over
+ <acronym>IPv4</acronym> as well as many new features:</para>
<itemizedlist>
<listitem>
- <para>128 bit address space which allows for
+ <para>Its 128-bit address space allows for
340,282,366,920,938,463,463,374,607,431,768,211,456
- addresses. This means there are approximately
- 6.67 * 10^27 <acronym>IPv6</acronym> addresses per square
- meter on the planet.</para>
+ addresses. This addresses the <acronym>IPv4</acronym>
+ address shortage and eventual <acronym>IPv4</acronym>
+ address exhaustion.</para>
</listitem>
<listitem>
<para>Routers only store network aggregation addresses in
their routing tables, thus reducing the average space of a
- routing table to 8192 entries.</para>
+ routing table to 8192 entries. This addresses the scalability
+ issues associated with <acronym>IPv4</acronym>, which required every
+ allocated block of <acronym>IPv4</acronym> addresses to be
+ exchanged between Internet routers, causing
+ their routing tables to become
+ too large to allow efficient routing.</para>
</listitem>
</itemizedlist>
- <para>There are many other useful features of
- <acronym>IPv6</acronym>:</para>
-
<itemizedlist>
<listitem>
<para>Address autoconfiguration (<link
@@ -4327,16 +4290,11 @@ Received 264951 bytes in 0.1 seconds</sc
</listitem>
<listitem>
- <para>Anycast addresses (<quote>one-out-of
- many</quote>).</para>
- </listitem>
-
- <listitem>
<para>Mandatory multicast addresses.</para>
</listitem>
<listitem>
- <para><acronym>IPsec</acronym> (<acronym>IP</acronym>
+ <para>Built-in <acronym>IPsec</acronym> (<acronym>IP</acronym>
security).</para>
</listitem>
@@ -4345,7 +4303,7 @@ Received 264951 bytes in 0.1 seconds</sc
</listitem>
<listitem>
- <para>Mobile <acronym>IP</acronym>.</para>
+ <para>Support for mobile <acronym>IP</acronym>.</para>
</listitem>
<listitem>
@@ -4354,22 +4312,12 @@ Received 264951 bytes in 0.1 seconds</sc
</listitem>
</itemizedlist>
-
- <para>For more information, refer to <link
- xlink:href="http://www.kame.net">KAME.net</link></para>
-
- <para>Currently <acronym>IPv6</acronym> support for many
- applications and services is very good, though for some
- software it still needs work. For authoritative information
- about the support of <acronym>IPv6</acronym>, please consult
- the Official Documentation for the software in
- question.</para>
-
- <para>Web, <acronym>DNS</acronym> and Mail applications and
- servers have the best support for <acronym>IPv6</acronym>
- because they are the most common use case. Other applications
- may have varying degrees of <acronym>IPv6</acronym>
- support.</para>
+ <para>&os; includes the <link
+ xlink:href="http://www.kame.net/">http://www.kame.net/</link>
+ <acronym>IPv6</acronym> reference implementation and comes
+ with everything needed to use <acronym>IPv6</acronym>. This
+ section focuses on getting <acronym>IPv6</acronym> configured
+ and running.</para>
<sect2>
<title>Background on <acronym>IPv6</acronym> Addresses</title>
More information about the svn-doc-head
mailing list