Modified Files:

Linux+IPv6-HOWTO.lyx : some fixes and extensions
This commit is contained in:
pbldp 2002-11-19 21:39:33 +00:00
parent 0ee5d0df1c
commit f9a52d2055
1 changed files with 206 additions and 52 deletions

View File

@ -51,6 +51,15 @@ on>
<revhistory>
\layout SGML
<revision> <revnumber>Release 0.34</revnumber> <date>2002-11-19</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.33</revnumber> <date>2002-11-18</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.31</revnumber> <date>2002-09-29</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
@ -324,25 +324,15 @@ Translations
Translations always have to contain the URL, version number and copyright
of the original document (but yours, too).
Pls.
don't translate the original changelog, this is not very useful.
Looks like the the document's change frequency is mostly less than once
per month.
Since version 0.27 it looks like that most of the content contributed by
me has been written.
\layout Subsection
To German
\layout Standard
A German translation is planned by me (German is my native language), but
it won't happen until the document's change frequency is less than once
per month, and I get enough free time to do it (which is currently very
improbably).
If you have more free time than me, please feel free to take over the translati
on!
\layout Subsection
To other languages
\layout Standard
Normally, please wait until the document's change frequency is less than
once per month.
Since version 0.27 it looks like that most of the content is written.
To language
\layout Subsubsection
Chinese
@ -364,6 +354,14 @@ Since 2002-08-16 a Polish translation was started and is still in progress
by Lukasz Jokiel <Lukasz dot Jokiel at klonex dot com dot pl>.
Taken source: CVS-version 1.29 of LyX file, which was source for howto version
0.27.
\layout Subsubsection
German
\layout Standard
Since 2002-11-10 a German translation was started and is still in progress
by Georg Käfer <gkaefer at salzburg dot co dot at>.
Taken source: version 0.32 of howto.
\layout Section
Technical
@ -511,8 +509,7 @@ Latest
\series bold
version
\series default
was 3.2.1 released 14.
July
was 3.2.1 released July, 14
\series bold
1997
\series default
@ -612,22 +609,33 @@ Peter Bieringer
).
\layout Section
Used terms
Used terms, glossar and shortcuts
\layout Subsection
Network related
\layout Description
Link A link is a layer 2 network packet transport medium, examples are Ethernet,
Token Ring, PPP, SLIP, ATM, ISDN, Frame Relay,...
Base10 Well known decimal number system, represent any value with digit
0-9.
\layout Description
Node A node is a host or a router.
Base16 Usually used in lower and higher programming languages, known also
as hexadecimal number system, represent any value with digit 0-9 and char
A-F (case insensitive).
\layout Description
Host Generally a single homed host on a link.
Normally it has only one active network interface, e.g.
Ethernet or (not and) PPP.
Base85 Representation of a value with 85 different digits/chars, this can
lead to shorter strings but never seen in the wild.
\layout Description
Bit Smallest storage unit, on/true (1) or off/false (0)
\layout Description
Byte Mostly a collection of 8 (but not really a must - see older computer
systems) bits
\layout Description
Device Network device, see also NIC
\layout Description
Dual\SpecialChar ~
@ -637,16 +645,113 @@ host A dual homed host is a node with two network (physical or
between the interfaces.
\layout Description
Link A link is a layer 2 network packet transport medium, examples are Ethernet,
Token Ring, PPP, SLIP, ATM, ISDN, Frame Relay,...
\layout Description
Host Generally a single homed host on a link.
Normally it has only one active network interface, e.g.
Ethernet or (not and) PPP.
\layout Description
Interface Mostly same as
\begin_inset Quotes sld
\end_inset
device
\begin_inset Quotes srd
\end_inset
, see also NIC
\layout Description
IP\SpecialChar ~
Header Header of an IP packet (each network packet has a header, kind
of is depending on network layer)
\layout Description
Node A node is a host or a router.
\layout Description
Octets A collection of 8 real bits, today also similar to
\begin_inset Quotes sld
\end_inset
byte
\begin_inset Quotes srd
\end_inset
.
\layout Description
Port Information for the TCP/UDP dispatcher (layer 4) to transport information
to upper layers
\layout Description
Protocol Each network layer contains mostly a protocol field to make life
easier on dispatching transported information to upper layer, seen in layer
2 (MAC) and 3 (IP)
\layout Description
Router A router is a node with two or more network (physical or virtual)
interfaces, capable of forwarding packets between the interfaces.
\layout Description
Socket An IP socket is defined by source and destination IP addresses and
Portsand(binding)
\layout Description
Stack Network related a collection of layers
\layout Description
Subnetmask IP networks uses bit masks to separate local networks from remote
ones
\layout Description
Tunnel A tunnel is typically a point-to-point connection over which packets
are exchanged which carry the data of another protocol, e.g.
an IPv6-in-IPv4 tunnel.
\layout Subsubsection
\begin_inset LatexCommand \label{Glossar}
\end_inset
Shortcuts
\layout Description
API Application Programming Interface
\layout Description
BSD Berkeley Software Distribution
\layout Description
ASIC Application Specified Integrated Circuit
\layout Description
CAN-Bus Controller Area Network Bus (physical bus system)
\layout Description
KAME Project - a joint effort of six companies in Japan to provide a free
IPv6 and IPsec (for both IPv4 and IPv6) stack for BSD variants to the world
\begin_inset LatexCommand \url[www.kame.net]{http://www.kame.net/}
\end_inset
\layout Description
NIC Network Interface Card
\layout Description
RFC Request For Comments - set of technical and organizational notes about
the Internet
\layout Description
USAGI UniverSAl playGround for Ipv6 Project - works to deliver the production
quality IPv6 protocol stack for the Linux system.
\layout Subsection
Document related
@ -772,7 +877,7 @@ Linux operating system compatible hardware
Surely you wish to experiment with real hardware, and not only read this
HOWTO to fall asleep here and there.
:)
;-7)
\layout Chapter
@ -1276,7 +1381,17 @@ For example, the IPv4 address 1.2.3.4 looks like this:
IPv4-compatible IPv6 address
\layout Standard
Also for sockets, in this case it is for a dual purpose and looks like:
Used for automatic tunneling (
\begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc1993.html}
\end_inset
), which is being replaced by
\begin_inset LatexCommand \ref[6to4 tunneling]{tunneling-6to4}
\end_inset
.
\layout Code
0:0:0:0:0:0:a.b.c.d/96
@ -1286,15 +1401,6 @@ or in compressed format
\layout Code
::a.b.c.d/96
\layout Standard
These addresses are also used by automatic tunneling, which is being replaced
by
\begin_inset LatexCommand \ref[6to4 tunneling]{tunneling-6to4}
\end_inset
.
\layout Section
Network part, also known as prefix
@ -1767,7 +1873,7 @@ Note: Anycast addresses cannot be used as source addresses, they are only
Subnet-router anycast address
\layout Standard
A simple example for an anycast addresses is the subnet-router anycast address.
A simple example for an anycast address is the subnet-router anycast address.
Assuming that a node has the following global assigned IPv6 address:
\layout Code
@ -1829,7 +1935,7 @@ using the
design for EUI-48 identifiers.
\layout Subsubsection
Privacy problem with automatically computed and solution
Privacy problem with automatically computed addresses and a solution
\layout Standard
\align left
Because the "automatically computed" host part is globally unique (except
@ -1889,8 +1995,16 @@ In the early design phase it was planned to use a fully hierarchical routing
approach to reduce the size of the routing tables maximally.
The reasoning behind this approach were the number of current IPv4 routing
entries in core routers (> 104 thousand in May 2001), reducing the need
of memory in hardware routers (ASIC driven) to hold the routing table and
increase speed (fewer entries hopefully result in faster lookups).
of memory in hardware routers (ASIC
\begin_inset Quotes sld
\end_inset
Application Specified Integrated Circuit
\begin_inset Quotes srd
\end_inset
driven) to hold the routing table and increase speed (fewer entries hopefully
result in faster lookups).
\layout Standard
\align left
Todays view is that routing will be mostly hierarchically designed for networks
@ -1929,7 +2043,7 @@ Network:
3ffe:ffff:0100:0000:0000:0000:0000:0000
\layout Itemize
Net-mask:
Netmask:
\layout Code
ffff:ffff:ffff:0000:0000:0000:0000:0000
@ -8994,6 +9108,34 @@ Kap.2.3.1.4.
\newline
Kurz angerissen werden: RFC1825 - Security Association Konzept RFC1826 -
IP authentication Header RFC1827 - IP Encapsulation Security Payload
\layout Itemize
IPv6.
Das neue Internet- Protokoll.
Technik, Anwendung, Migration
\begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/389864149X}
\end_inset
\newline
Hans Peter Dittler
\newline
2.
akt.
und erweiterte Auflage 2002 dpunkt.verlag, ISBN 3-89864-149-X
\layout Itemize
Das neue Internetprotokoll IPv6
\begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/3446216855}
\end_inset
\newline
Herbert Wiese
\newline
2002 Carl Hanser Verlag, ISBN 3446216855
\layout Subsection
Articles, Books, Online Reviews (mixed)
@ -11025,6 +11167,18 @@ Versions x.y.z are work-in-progress and only published as LyX file on CVS.
Releases 0.x
\layout Description
0.34 2002-11-19/PB: Add information about German translation (work in progress),
some fixes, create a small shortcut explanation list, extend
\begin_inset Quotes sld
\end_inset
used terms
\begin_inset Quotes srd
\end_inset
and add two German books
\layout Description
0.33 2002-11-18/PB: Fix broken RFC-URLs, add parameter ttl on 6to4 tunnel
setup example
\layout Description
@ -11319,7 +11473,7 @@ send mail
Georg Käfer <gkaefer at salzburg dot co dot at>: For detection of no proper
PDF creation (fixed now by LDP maintainer Greg Ferguson), input for German
books, big list of URLs and some other suggestions
books, big list of URLs and some more suggestions and corrections.
\layout Itemize
Frank Dinies <FrankDinies at web dot de>: For a bugfix on IPv6 address explanati