aboutsummaryrefslogtreecommitdiff
path: root/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml
diff options
context:
space:
mode:
Diffstat (limited to 'zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml')
-rw-r--r--zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml72
1 files changed, 30 insertions, 42 deletions
diff --git a/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml b/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml
index ac166db725..c28ffa5d1b 100644
--- a/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml
+++ b/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml
@@ -4,29 +4,23 @@
$FreeBSD$
-->
-
-<chapter id="ipv6">
+<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="ipv6">
<title>IPv6 Internals</title>
- <sect1 id="ipv6-implementation">
- <sect1info>
+ <sect1 xml:id="ipv6-implementation">
+ <info><title>IPv6/IPsec Implementation</title>
<authorgroup>
- <author>
- <firstname>Yoshinobu</firstname>
- <surname>Inoue</surname>
- <contrib>Contributed by </contrib>
- </author>
+ <author><personname><firstname>Yoshinobu</firstname><surname>Inoue</surname></personname><contrib>Contributed by </contrib></author>
</authorgroup>
- <!-- March 2000 -->
- </sect1info>
+
+ </info>
- <title>IPv6/IPsec Implementation</title>
+
<para>This section should explain IPv6 and IPsec related implementation
- internals. These functionalities are derived from <ulink
- url="http://www.kame.net/">KAME project</ulink></para>
+ internals. These functionalities are derived from <link xlink:href="http://www.kame.net/">KAME project</link></para>
- <sect2 id="ipv6details">
+ <sect2 xml:id="ipv6details">
<title>IPv6</title>
<sect3>
@@ -42,9 +36,9 @@
<para>Conformance tests have been performed on the KAME STABLE kit
at TAHI project. Results can be viewed at
- <ulink url="http://www.tahi.org/report/KAME/"></ulink>.
+ <uri xlink:href="http://www.tahi.org/report/KAME/">http://www.tahi.org/report/KAME/</uri>.
We also attended Univ. of New Hampshire IOL tests
- (<ulink url="http://www.iol.unh.edu/"></ulink>) in the
+ (<uri xlink:href="http://www.iol.unh.edu/">http://www.iol.unh.edu/</uri>) in the
past, with our past snapshots.</para>
<itemizedlist>
@@ -233,8 +227,7 @@
<itemizedlist>
<listitem>
<para>IPv4 mapped address (3.7) and special behavior of IPv6
- wildcard bind socket (3.8) are supported. See <link
- linkend="ipv6-wildcard-socket">23.5.1.12</link>
+ wildcard bind socket (3.8) are supported. See <link linkend="ipv6-wildcard-socket">23.5.1.12</link>
in this document for details.</para>
</listitem>
</itemizedlist>
@@ -308,7 +301,7 @@
</itemizedlist>
</sect3>
- <sect3 id="neighbor-discovery">
+ <sect3 xml:id="neighbor-discovery">
<title>Neighbor Discovery</title>
<para>Neighbor Discovery is fairly stable. Currently Address
@@ -367,7 +360,7 @@
we may provide sysctl knob for the variable.</para>
</sect3>
- <sect3 id="ipv6-scope-index">
+ <sect3 xml:id="ipv6-scope-index">
<title>Scope Index</title>
<para>IPv6 uses scoped addresses. Therefore, it is very important to
@@ -430,7 +423,7 @@
link and an interface, which is stronger than what specs say.</para>
</sect3>
- <sect3 id="ipv6-pnp">
+ <sect3 xml:id="ipv6-pnp">
<title>Plug and Play</title>
<para>Most of the IPv6 stateless address autoconfiguration is implemented
@@ -549,7 +542,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
</sect4>
</sect3>
- <sect3 id="gif">
+ <sect3 xml:id="gif">
<title>Generic tunnel interface</title>
<para>GIF (Generic InterFace) is a pseudo interface for configured
@@ -577,8 +570,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
routing tables to perform infinite level of tunneling.
<emphasis>Please be warned</emphasis>.</para>
- <para>gif can be configured to be ECN-friendly. See <link
- linkend="ipsec-ecn">23.5.4.5</link> for ECN-friendliness of
+ <para>gif can be configured to be ECN-friendly. See <link linkend="ipsec-ecn">23.5.4.5</link> for ECN-friendliness of
tunnels, and &man.gif.4; for how to configure.</para>
<para>If you would like to configure an IPv4-in-IPv6 tunnel with gif
@@ -587,7 +579,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
interface.</para>
</sect3>
- <sect3 id="ipv6-sas">
+ <sect3 xml:id="ipv6-sas">
<title>Source Address Selection</title>
<para>Current source selection rule is scope oriented (there are some
@@ -633,8 +625,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
<para>For instance, ::1 is selected for ff01::1,
fe80:1::200:f8ff:fe01:6317 for fe80:1::2a0:24ff:feab:839b (note
- that embedded interface index - described in <link
- linkend="ipv6-scope-index">23.5.1.3</link> - helps us
+ that embedded interface index - described in <link linkend="ipv6-scope-index">23.5.1.3</link> - helps us
choose the right source address. Those embedded indices will not
be on the wire). If the outgoing interface has multiple address for
the scope, a source is selected longest match basis (rule 3). Suppose
@@ -664,7 +655,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
address).</para>
</sect3>
- <sect3 id="ipv6-jumbo">
+ <sect3 xml:id="ipv6-jumbo">
<title>Jumbo Payload</title>
<para>The Jumbo Payload hop-by-hop option is implemented and can
@@ -782,7 +773,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
attack.)</para>
</sect3>
- <sect3 id="icmpv6">
+ <sect3 xml:id="icmpv6">
<title>ICMPv6</title>
<para>After RFC2463 was published, IETF ipngwg has decided to
@@ -853,7 +844,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
<para>Both IP and IP6 reassemble functions never call m_pullup().</para>
</sect3>
- <sect3 id="ipv6-wildcard-socket">
+ <sect3 xml:id="ipv6-wildcard-socket">
<title>IPv4 mapped address and IPv6 wildcard socket</title>
<para>RFC2553 describes IPv4 mapped address (3.7) and special behavior
@@ -1217,7 +1208,7 @@ FreeBSD 4.x configurable supported
</sect3>
</sect2>
- <sect2 id="ipsec-implementation">
+ <sect2 xml:id="ipsec-implementation">
<title>IPsec</title>
<para>IPsec is mainly organized by three components.</para>
@@ -1327,9 +1318,8 @@ FreeBSD 4.x configurable supported
<filename>rfc240[1-6].txt</filename>,
<filename>rfc241[01].txt</filename>, <filename>rfc2451.txt</filename>
and <filename>draft-mcdonald-simple-ipsec-api-01.txt</filename>
- (draft expired, but you can take from <ulink
- url="ftp://ftp.kame.net/pub/internet-drafts/">
- ftp://ftp.kame.net/pub/internet-drafts/</ulink>).
+ (draft expired, but you can take from <link xlink:href="ftp://ftp.kame.net/pub/internet-drafts/">
+ ftp://ftp.kame.net/pub/internet-drafts/</link>).
(NOTE: IKE specifications, <filename>rfc241[7-9].txt</filename> are
implemented in userland, as "racoon" IKE daemon)</para>
@@ -1475,7 +1465,7 @@ FreeBSD 4.x configurable supported
property issues only).</para>
</sect3>
- <sect3 id="ipsec-ecn">
+ <sect3 xml:id="ipsec-ecn">
<title>ECN consideration on IPsec tunnels</title>
<para>ECN-friendly IPsec tunnel is supported as described in
@@ -1489,9 +1479,8 @@ FreeBSD 4.x configurable supported
lost.</para>
<para>To make IPsec tunnel ECN-friendly, we should modify encapsulation
- and decapsulation procedure. This is described in <ulink
- url="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
- http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</ulink>,
+ and decapsulation procedure. This is described in <link xlink:href="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
+ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</link>,
chapter 3.</para>
<para>IPsec tunnel implementation can give you three behaviors, by
@@ -1554,9 +1543,8 @@ ECN allowed copy TOS bits except for ECN use inner TOS bits with some
<para>For more information, please refer to:</para>
- <para><ulink
- url="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
- http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</ulink>,
+ <para><link xlink:href="http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt">
+ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt</link>,
RFC2481 (Explicit Congestion Notification),
src/sys/netinet6/{ah,esp}_input.c</para>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-26 03:55:01 +0000