mirror of https://github.com/tLDP/LDP
Modified Files:
Linux+IPv6-HOWTO.lyx : Fix broken RFC URLs
This commit is contained in:
pbldp
parent
0d40fd3ce4
commit
b2c6eb3a6b
|
|
@ -51,6 +51,15 @@ on>
|
|||
<revhistory>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.33</revnumber> <date>2002-11-18</date> <authorini
|
||||
tials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
||||
\end_inset
|
||||
|
||||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.32</revnumber> <date>2002-11-03</date> <authorini
|
||||
tials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
|
@ -69,15 +78,6 @@ tials>PB</authorinitials> <revremark>See
|
|||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.30</revnumber> <date>2002-09-27</date> <authorini
|
||||
tials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
||||
\end_inset
|
||||
|
||||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
</revhistory>
|
||||
\layout Abstract
|
||||
|
||||
|
|
@ -797,7 +797,7 @@ IPv6 is a new layer 3 transport protocol (see
|
|||
\color default
|
||||
) which will supersede IPv4 (also known as IP).
|
||||
IPv4 was designed long time ago (
|
||||
\begin_inset LatexCommand \url[RFC 760]{http://rfc.net/rfc760.html}
|
||||
\begin_inset LatexCommand \url[RFC 760 / Internet Protocol]{http://www.faqs.org/rfcs/rfc760.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1028,7 +1028,7 @@ There is also a so-called
|
|||
compact
|
||||
\emph default
|
||||
(base85 coded) representation defined
|
||||
\begin_inset LatexCommand \url[RFC 1924 / A Compact Representation of IPv6 Addresses]{http://rfc.net/rfc1924.html}
|
||||
\begin_inset LatexCommand \url[RFC 1924 / A Compact Representation of IPv6 Addresses]{http://www.faqs.org/rfcs/rfc1924.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1068,7 +1068,7 @@ On any IP header, the first 4 bits are reserved for protocol version.
|
|||
\layout Itemize
|
||||
\align left
|
||||
5: is reserved for the Stream Protocol (STP,
|
||||
\begin_inset LatexCommand \url[RFC 1819]{http://rfc.net/rfc1819.html}
|
||||
\begin_inset LatexCommand \url[RFC 1819 / Internet Stream Protocol Version 2]{http://www.faqs.org/rfcs/rfc1819.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1303,7 +1303,7 @@ Network part, also known as prefix
|
|||
Designers defined some address types and left a lot of scope for future
|
||||
definitions as currently unknown requirements arise.
|
||||
|
||||
\begin_inset LatexCommand \url[RFC 2373 [July 1998] / IP Version 6 Addressing Architecture]{http://rfc.net/rfc2373.html}
|
||||
\begin_inset LatexCommand \url[RFC 2373 [July 1998] / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1398,7 +1398,7 @@ Site local address type
|
|||
\layout Standard
|
||||
\align left
|
||||
These are addresses similar to the
|
||||
\begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://rfc.net/rfc1918.html}
|
||||
\begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1478,7 +1478,7 @@ Global address type "(Aggregatable) global unicast"
|
|||
\align left
|
||||
Today, there is one global address type defined (the first design, called
|
||||
"provider based," was thrown away some years ago
|
||||
\begin_inset LatexCommand \url[RFC 1884 / IP Version 6 Addressing Architecture [obsolete]]{http://rfc.net/rfc1884.html}
|
||||
\begin_inset LatexCommand \url[RFC 1884 / IP Version 6 Addressing Architecture [obsolete]]{http://www.faqs.org/rfcs/rfc1884.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1572,12 +1572,12 @@ You can still apply for one of these prefixes, see here
|
|||
\layout Standard
|
||||
\align left
|
||||
These addresses, designed for a special tunneling mechanism [
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://rfc.net/rfc3056.html}
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
and
|
||||
\begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://rfc.net/rfc2893.html}
|
||||
\begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1695,7 +1695,7 @@ Multicast types
|
|||
\layout Standard
|
||||
|
||||
There are many types already defined/reserved (see
|
||||
\begin_inset LatexCommand \url[RFC 2373 / IP Version 6 Addressing Architecture]{http://rfc.net/rfc2373.html}
|
||||
\begin_inset LatexCommand \url[RFC 2373 / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1839,7 +1839,7 @@ Because the "automatically computed" host part is globally unique (except
|
|||
\align left
|
||||
This is a known problem, and a solution was defined: privacy extension,
|
||||
defined in
|
||||
\begin_inset LatexCommand \url[RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6]{http://rfc.net/rfc3041.html}
|
||||
\begin_inset LatexCommand \url[RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6]{http://www.faqs.org/rfcs/rfc3041.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -1905,7 +1905,7 @@ Prefix lengths (also known as "netmasks")
|
|||
Similar to IPv4, the routable network path for routing to take place.
|
||||
Because standard netmask notation for 128 bits doesn't look nice, designers
|
||||
employed the IPv4 Classless Inter Domain Routing (CIDR,
|
||||
\begin_inset LatexCommand \url[RFC 1519 / Classless Inter-Domain Routing]{http://rfc.net/rfc1519.html}
|
||||
\begin_inset LatexCommand \url[RFC 1519 / Classless Inter-Domain Routing]{http://www.faqs.org/rfcs/rfc1519.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -2183,7 +2183,7 @@ IPv6 capable links
|
|||
\layout Itemize
|
||||
|
||||
Serial Line IP (SLIP,
|
||||
\begin_inset LatexCommand \url[RFC 1055]{http://rfc.net/rfc1055.html}
|
||||
\begin_inset LatexCommand \url[RFC 1055 / SLIP]{http://www.faqs.org/rfcs/rfc1055.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -3949,7 +3949,7 @@ Static point-to-point tunneling: 6bone
|
|||
A point-to-point tunnel is a dedicated tunnel to an endpoint, which knows
|
||||
about your IPv6 network (for backward routing) and the IPv4 address of
|
||||
your tunnel endpoint and defined in
|
||||
\begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://rfc.net/rfc2893.html}
|
||||
\begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -3984,7 +3984,7 @@ Automatic tunneling occurs, when a node directly connects another node gotten
|
|||
\layout Standard
|
||||
|
||||
6to4 tunneling (
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://rfc.net/rfc3056.html}
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -4001,7 +4001,7 @@ Generation of 6to4 prefix
|
|||
\layout Standard
|
||||
|
||||
The 6to4 address is defined like following (schema is taken from
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://rfc.net/rfc3056.html}
|
||||
\begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -4683,7 +4683,7 @@ This will be filled in the future.
|
|||
\layout Standard
|
||||
|
||||
More information in the meantime:
|
||||
\begin_inset LatexCommand \url[RFC 2473 / Generic Packet Tunneling in IPv6 Specification]{http://rfc.net/rfc2473.html}
|
||||
\begin_inset LatexCommand \url[RFC 2473 / Generic Packet Tunneling in IPv6 Specification]{http://www.faqs.org/rfcs/rfc2473.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -6716,7 +6716,7 @@ IPv6 firewalling is important, especially if using IPv6 on internal networks
|
|||
with global IPv6 addresses.
|
||||
Because unlike at IPv4 networks where in common internal hosts are protected
|
||||
automatically using private IPv4 addresses like
|
||||
\begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://rfc.net/rfc1918.html}
|
||||
\begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -8153,7 +8153,7 @@ For IPv6 new types and root zones for reverse lookups are defined:
|
|||
\layout Itemize
|
||||
|
||||
AAAA and reverse IP6.INT: specified in
|
||||
\begin_inset LatexCommand \url[RFC 1886 / DNS Extensions to support IP version 6]{http://rfc.net/rfc1886.html}
|
||||
\begin_inset LatexCommand \url[RFC 1886 / DNS Extensions to support IP version 6]{http://www.faqs.org/rfcs/rfc1886.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -8161,7 +8161,7 @@ AAAA and reverse IP6.INT: specified in
|
|||
\layout Itemize
|
||||
|
||||
A6, DNAME (DEPRICATED NOW!) and reverse IP6.ARPA: specified in
|
||||
\begin_inset LatexCommand \url[RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering]{http://rfc.net/rfc2874.html}
|
||||
\begin_inset LatexCommand \url[RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering]{http://www.faqs.org/rfcs/rfc2874.html}
|
||||
|
||||
\end_inset
|
||||
|
||||
|
|
@ -11024,6 +11024,9 @@ Versions x.y.z are work-in-progress and only published as LyX file on CVS.
|
|||
Releases 0.x
|
||||
\layout Description
|
||||
|
||||
0.33 2002-11-18/PB: Fix broken RFC-URLs
|
||||
\layout Description
|
||||
|
||||
0.32 2002-11-03/PB: Add information about Chinese translation
|
||||
\layout Description
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue