friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzai2_5.4.0.1/rzai2compipv4ipv6.htm

613 lines
48 KiB
HTML
Raw Permalink Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="reference" />
<meta name="DC.Title" content="Compare IPv4 to IPv6" />
<meta name="abstract" content="You can compare the IPv4 attributes to IPv6 attributes." />
<meta name="description" content="You can compare the IPv4 attributes to IPv6 attributes." />
<meta name="DC.Relation" scheme="URI" content="rzai2ipv6concepts.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzai2compipv4ipv6" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Compare IPv4 to IPv6</title>
</head>
<body id="rzai2compipv4ipv6"><a name="rzai2compipv4ipv6"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Compare IPv4 to IPv6</h1>
<div><p>You can compare the IPv4 attributes to IPv6 attributes.</p>
<div class="section"><img src="./delta.gif" alt="Start of change" /><p>IBM<sup>®</sup> is implementing IPv6 for the iSeries™ server over several software
releases. However, IPv6 is now product-ready.</p>
<p>You might wonder how IPv6
differs from IPv4. The following table allows you to quickly look up specific
functions and compare their usage in each Internet Protocol. Select an attribute
from this list to link to the comparison in the table.</p>
<img src="./deltaend.gif" alt="End of change" /></div>
<div class="section"> <ul><li><a href="#rzai2compipv4ipv6__compaddress">address</a></li>
<li><a href="#rzai2compipv4ipv6__compaddralloc">address allocation</a></li>
<li><a href="#rzai2compipv4ipv6__compaddrlife">address lifetime</a></li>
<li><a href="#rzai2compipv4ipv6__compaddressmask">address mask</a></li>
<li><a href="#rzai2compipv4ipv6__compaddrpref">address prefix</a></li>
<li><a href="#rzai2compipv4ipv6__comparp">Address Resolution Protocol (ARP)</a></li>
<li><a href="#rzai2compipv4ipv6__compaddrscope">address scope</a></li>
<li><a href="#rzai2compipv4ipv6__compaddrtype">address types</a></li>
<li><a href="#rzai2compipv4ipv6__compcommtrace">communications trace</a></li>
<li><a href="#rzai2compipv4ipv6__compconfig">configuration</a></li>
<li><a href="#rzai2compipv4ipv6__compdns">Domain Name System (DNS)</a></li>
<li><a href="#rzai2compipv4ipv6__compdhcp">Dynamic Host Configuration Protocol
(DHCP)</a></li>
<li><a href="#rzai2compipv4ipv6__compftp">File Transfer Protocol (FTP)</a></li>
<li><a href="#rzai2compipv4ipv6__compfragments">fragments</a></li>
<li><a href="#rzai2compipv4ipv6__comphosttable">host table</a></li>
<li><a href="#rzai2compipv4ipv6__compinterface">interface</a></li>
<li><a href="#rzai2compipv4ipv6__compicmp">Internet Control Message Protocol
(ICMP)</a></li>
<li><a href="#rzai2compipv4ipv6__compigmp">Internet Group Management Protocol
(IGMP)</a></li>
<li><a href="#rzai2compipv4ipv6__compipheader">IP header</a></li>
<li><a href="#rzai2compipv4ipv6__compipheaderopt">IP header options</a></li>
<li><a href="#rzai2compipv4ipv6__compipheaderprot">IP header protocol byte</a></li>
<li><a href="#rzai2compipv4ipv6__compipheadertos">IP header Type of Service
(TOS) byte</a></li>
<li><a href="#rzai2compipv4ipv6__compinavsupp">iSeries Navigator support</a></li>
<li><a href="#rzai2compipv4ipv6__complanconnect">LAN connection</a></li>
<li><a href="#rzai2compipv4ipv6__compl2tp">Layer 2 Tunnel Protocol (L2TP)</a></li>
<li><a href="#rzai2compipv4ipv6__comploopaddr">loopback address</a></li>
<li><a href="#rzai2compipv4ipv6__compmtu">Maximum Transmission Unit (MTU)</a></li>
<li><a href="#rzai2compipv4ipv6__compnetstat">netstat</a></li>
<li><a href="#rzai2compipv4ipv6__compnat">Network Address Translation (NAT)</a></li>
<li><a href="#rzai2compipv4ipv6__compnetworktable">network table</a></li>
<li><a href="#rzai2compipv4ipv6__compnodeinfo">node info query</a></li>
<li><a href="#rzai2compipv4ipv6__comppacketfilter">packet filtering</a></li>
<li><a href="#rzai2compipv4ipv6__comppacketforward">packet forwarding</a></li>
<li><a href="#rzai2compipv4ipv6__compping">PING</a></li>
<li><a href="#rzai2compipv4ipv6__compppp">Point-to-Point Protocol (PPP)</a></li>
<li><a href="#rzai2compipv4ipv6__compportrestrict">port restrictions</a></li>
<li><a href="#rzai2compipv4ipv6__compports">ports</a></li>
<li><a href="#rzai2compipv4ipv6__compprivpubaddr">private and public addresses</a></li>
<li><a href="#rzai2compipv4ipv6__compprotocoltable">protocol table</a></li>
<li><a href="#rzai2compipv4ipv6__compqos">quality of service (QoS)</a></li>
<li><a href="#rzai2compipv4ipv6__comprenumber">renumbering</a></li>
<li><a href="#rzai2compipv4ipv6__comproute">route</a></li>
<li><a href="#rzai2compipv4ipv6__comprip">Routing Information Protocol (RIP)</a></li>
<li><a href="#rzai2compipv4ipv6__compservicestable">services table</a></li>
<li><a href="#rzai2compipv4ipv6__compsnmp">Simple Network Management Protocol
(SNMP)</a></li>
<li><a href="#rzai2compipv4ipv6__compsocketapi">sockets API</a></li>
<li><a href="#rzai2compipv4ipv6__compsourceaddr">source address selection</a></li>
<li><a href="#rzai2compipv4ipv6__compstartstop">starting and stopping</a></li>
<li><a href="#rzai2compipv4ipv6__comptelnet">Telnet</a></li>
<li><a href="#rzai2compipv4ipv6__comptraceroute">trace route</a></li>
<li><a href="#rzai2compipv4ipv6__comptransport">transport layers</a></li>
<li><a href="#rzai2compipv4ipv6__compunspecaddr">unspecified address</a></li>
<li><a href="#rzai2compipv4ipv6__compvpn">virtual private networking (VPN)</a></li>
</ul>
</div>
<div class="tablenoborder"><!-- Link to dynamic table -->
<SCRIPT language="Javascript" type="text/javascript" src="../rzahg/iccommon.js"></SCRIPT>
<SCRIPT language="Javascript" type="text/javascript">
//<![CDATA[
//Do not split up the following string. Keep it on one line.
var textA = "<p>To easily compare and sort the data in this table, use the <a href='rzai2compipv4ipv6.xml'>interactive table<\/a>.<\/p>";
if (isIE5) {
document.writeln(textA);
}
//]]>
</SCRIPT>
<!-- End of link to dynamic table --><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="27.27272727272727%" id="d0e193">Description</th>
<th valign="top" width="32.95454545454545%" id="d0e195">IPv4</th>
<th valign="top" width="39.77272727272727%" id="d0e197">IPv6</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddress"><a name="rzai2compipv4ipv6__compaddress"><!-- --></a>address</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">32 bits long (4 bytes). Address is composed
of a network and a host portion, which depend on address class. Various address
classes are defined: A, B, C, D, or E depending on initial few bits. The
total number of IPv4 addresses is 4 294 967 296. <p>The text form of the
IPv4 address is <samp class="codeph">nnn.nnn.nnn.nnn</samp>, where 0&lt;=<samp class="codeph"><var class="varname">nnn</var></samp>&lt;=255,
and each <samp class="codeph"><var class="varname">n</var></samp> is a decimal digit. Leading
zeros can be omitted. Maximum number of print characters is 15, not counting
a mask.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">128 bits long (16 bytes). Basic architecture
is 64 bits for the network number and 64 bits for the host number. Often,
the host portion of an IPv6 address (or part of it) will be derived from a
MAC address or other interface identifier. <p>Depending on the subnet prefix,
IPv6 has a more complicated architecture than IPv4.</p>
<p>The number of IPv6
addresses is 10<sup>28</sup> (79 228 162 514 264 337 593 543 950 336) times
larger than the number of IPv4 addresses. The text form of the IPv6 address
is <samp class="codeph">xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx</samp>, where each <samp class="codeph">x</samp> is
a hexadecimal digit, representing 4 bits. Leading zeros can be omitted. The
double colon (<samp class="codeph">::</samp>) can be used once in the text form of an
address, to designate any number of 0 bits. For example, <samp class="codeph">::ffff:10.120.78.40</samp> is
an IPv4-mapped IPv6 address. (See <span><img src="./delta.gif" alt="Start of change" />RFC 3513<img src="./deltaend.gif" alt="End of change" /></span> for details. </p>
<p>To
view this RFC, see <a href="http://www.rfc-editor.org/rfcsearch.html">RFC Editor</a> <img src="www.gif" alt="Link outside Information Center" /> (www.rfc-editor.org/rfcsearch.html).</p>
<p> </p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddralloc"><a name="rzai2compipv4ipv6__compaddralloc"><!-- --></a>address allocation</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Originally, addresses were allocated by network
class. As address space is depleted, smaller allocations using Classless Inter-Domain
Routing (CIDR) are made. Allocation has not been balanced among institutions
and nations.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Allocation is in the earliest stages. The
Internet Engineering Task Force (IETF) and Internet Architecture Board (IAB)
have recommended that essentially every organization, home, or entity be allocated
a <samp class="codeph">/48</samp> subnet prefix length. This would leave 16 bits for
the organization to do subnetting. The address space is large enough to give
every person in the world their own <samp class="codeph">/48</samp> subnet prefix length.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddrlife"><a name="rzai2compipv4ipv6__compaddrlife"><!-- --></a>address lifetime</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Generally, not an applicable concept, except
for addresses assigned using DHCP.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">IPv6 addresses have two lifetimes: preferred
and valid, with the preferred lifetime always &lt;= valid. <p><img src="./delta.gif" alt="Start of change" />After
the preferred lifetime expires, the address is not to be used as a source
IP address for new connections if an equally good preferred address is available.
After the valid lifetime expires, the address is not used (recognized) as
a valid destination IP address for incoming packets or used as a source IP
address.<img src="./deltaend.gif" alt="End of change" /></p>
<p>Some IPv6 addresses have, by definition, infinite preferred
and valid lifetimes; for example link-local (see <a href="#rzai2compipv4ipv6__compaddrscope">address
scope</a>).</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddressmask"><a name="rzai2compipv4ipv6__compaddressmask"><!-- --></a>address mask</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Used to designate network from host portion.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Not used (see <a href="#rzai2compipv4ipv6__compaddrpref">address
prefix</a>).</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddrpref"><a name="rzai2compipv4ipv6__compaddrpref"><!-- --></a>address prefix</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Sometimes used to designate network from
host portion. Sometimes written as <samp class="codeph">/nn</samp> suffix on presentation
form of address.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Used to designate the subnet prefix of an
address. Written as <samp class="codeph">/nnn</samp> (up to 3 decimal digits, <samp class="codeph">0 &lt;=
nnn &lt;= 128</samp>) suffix after the print form. An example is <samp class="codeph">fe80::982:2a5c/10</samp>,
where the first 10 bits comprise the subnet prefix.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comparp"><a name="rzai2compipv4ipv6__comparp"><!-- --></a>Address Resolution Protocol (ARP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Address Resolution Protocol is used by IPv4
to find a physical address, such as the MAC or link address, associated with
an IPv4 address.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">IPv6 embeds these functions within IP itself
as part of the algorithms for stateless autoconfiguration and neighbor discovery
using Internet Control Message Protocol version 6 (ICMPv6). Hence, there is
no such thing as ARP6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddrscope"><a name="rzai2compipv4ipv6__compaddrscope"><!-- --></a>address scope</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">For unicast addresses, the concept does not
apply. There are designated private address ranges and loopback. Outside
of that, addresses are assumed to be global.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />In IPv6, address scope is
part of the architecture. Unicast addresses have two defined scopes, including
link-local and global; and multicast addresses have 14 scopes. Default address
selection for both source and destination takes scope into account.<img src="./deltaend.gif" alt="End of change" /></p>
<p>A
scope zone is an instance of a scope in a particular network. As a consequence,
IPv6 addresses sometimes must be entered or associated with a zone ID. The
syntax is <samp class="codeph">%zid</samp> where <samp class="codeph">zid</samp> is a number (usually
small) or a name. The zone ID is written after the address and before the
prefix. For example, <samp class="codeph">2ba::1:2:14e:9a9b:c%3/48</samp>.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compaddrtype"><a name="rzai2compipv4ipv6__compaddrtype"><!-- --></a>address types</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Unicast, multicast, and broadcast.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Unicast, multicast, and anycast. See <a href="rzai2ipv6addrtypes.htm#ipv6addrtypes">IPv6 address types</a> for
descriptions.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compcommtrace"><a name="rzai2compipv4ipv6__compcommtrace"><!-- --></a>communications trace</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">A tool to collect a detailed trace of TCP/IP
(and other) packets that enter and leave an iSeries server.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Same for IPv6, and IPv6
is supported.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compconfig"><a name="rzai2compipv4ipv6__compconfig"><!-- --></a>configuration</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 "><p>You must configure a newly installed system
before it can communicate with other systems; that is, IP addresses and routes
must be assigned.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Configuration is optional,
depending on functions required. IPv6 can be used with any Ethernet adapter
and can be run over the loopback interface. IPv6 interfaces are self-configuring
using IPv6 stateless autoconfiguration. You can also manually configure the
IPv6 interface. So, the system will be able to communicate with other IPv6
systems that are local and remote, depending on the type of network and whether
an IPv6 router exists.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compdns"><a name="rzai2compipv4ipv6__compdns"><!-- --></a>Domain Name System (DNS)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Applications accept host names and then use
DNS to get an IP address, using socket API <samp class="codeph">gethostbyname()</samp>.
<p>Applications also accept IP addresses and then use DNS to get host names
using <samp class="codeph">gethostbyaddr()</samp>. </p>
<p>For IPv4, the domain for reverse
lookups is <samp class="codeph">in-addr.arpa</samp>.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same for IPv6. Support for IPv6 exists using
AAAA (quad A) record type and reverse lookup (IP-to-name). An application
may elect to accept IPv6 addresses from DNS (or not) and then use IPv6 to
communicate (or not). <p></p>
<p><img src="./delta.gif" alt="Start of change" />The socket API <samp class="codeph">gethostbyname()</samp> only
supports IPv4. For IPv6, a new <samp class="codeph">getaddrinfo()</samp> API is used
to obtain (at application choice) IPv6 only, or IPv4 and IPv6 addresses.<img src="./deltaend.gif" alt="End of change" /></p>
<p>For
IPv6, the domain used for reverse lookups is <samp class="codeph">ip6.arpa</samp>, and
if not found then ip6.int (see API <a href="../apis/getnameinfo.htm">getnameinfo()</a>).</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compdhcp"><a name="rzai2compipv4ipv6__compdhcp"><!-- --></a>Dynamic Host Configuration Protocol (DHCP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 "><p>Used to dynamically obtain an IP address
and other configuration information. The iSeries supports a DHCP server for IPv4.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS™ implementation
of DHCP does not support IPv6.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compftp"><a name="rzai2compipv4ipv6__compftp"><!-- --></a>File Transfer Protocol (FTP)</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">File Transfer Protocol allows you to send and receive
files across networks.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, the i5/OS implementation of FTP does not support
IPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compfragments"><a name="rzai2compipv4ipv6__compfragments"><!-- --></a>fragments</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">When a packet is too big for the next link
over which it is to travel, it can be fragmented by the sender (host or router).</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />For IPv6, fragmentation
can only occur at the source node, and reassembly is only done at the destination
node. The fragmentation extension header is used.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comphosttable"><a name="rzai2compipv4ipv6__comphosttable"><!-- --></a>host table</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">On iSeries Navigator, a configurable table
that associates an Internet address with a host name; for example, <samp class="codeph">127.0.0.1</samp>,
loopback. This table is used by the sockets name resolver, either before
a DNS lookup or after a DNS lookup fails (determined by host name search priority).</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, this table does not support IPv6.
Customers need to configure an AAAA record in a DNS for IPv6 domain resolution.
You can run the DNS locally on the same system as the resolver, or you can
run it on a different system.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compinterface"><a name="rzai2compipv4ipv6__compinterface"><!-- --></a>interface</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">The conceptual or logical entity used by
TCP/IP to send and receive packets and always closely associated with an IPv4
address, if not named with an IPv4 address. Sometimes referred to as a logical
interface. <p>Can be started and stopped independently of each other and
independently of TCP/IP using STRTCPIFC and ENDTCPIFC commands and using iSeries Navigator.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same concept as IPv4. <p>Can be started and
stopped independently of each other and independently of TCP/IP using iSeries Navigator
only.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compicmp"><a name="rzai2compipv4ipv6__compicmp"><!-- --></a>Internet Control Message Protocol (ICMP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">ICMP is used by IPv4 to communicate network
information.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Used similarly for IPv6; however, Internet
Control Message Protocol version 6 (ICMPv6) provides some new attributes.
<p>Basic error types remain, such as destination unreachable, echo request
and reply. New types and codes are added to support neighbor discovery and
related functions.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compigmp"><a name="rzai2compipv4ipv6__compigmp"><!-- --></a>Internet Group Management Protocol (IGMP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">IGMP is used by IPv4 routers to find hosts
that want traffic for a particular multicast group, and used by IPv4 hosts
to inform IPv4 routers of existing multicast group listeners (on the host).</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Replaced by MLD (multicast listener discovery)
protocol for IPv6. Does essentially what IGMP does for IPv4, but uses ICMPv6
by adding a few MLD-specific ICMPv6 type values.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compipheader"><a name="rzai2compipv4ipv6__compipheader"><!-- --></a>IP header</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Variable length of 20-60 bytes, depending
on IP options present.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Fixed length of 40 bytes. There are no IP
header options. Generally, the IPv6 header is simpler than the IPv4 header.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compipheaderopt"><a name="rzai2compipv4ipv6__compipheaderopt"><!-- --></a>IP header options</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Various options that might accompany an IP
header (before any transport header).</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">The IPv6 header has no options. Instead,
IPv6 adds additional (optional) extension headers. The extension headers are
AH and ESP (unchanged from IPv4), hop-by-hop, routing, fragment, and destination. <span>Currently,
IPv6 supports some extension headers.</span></td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compipheaderprot"><a name="rzai2compipv4ipv6__compipheaderprot"><!-- --></a>IP header protocol byte</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">The protocol code of the transport layer
or packet payload; for example, ICMP.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">The type of header immediately following
the IPv6 header. Uses the same values as the IPv4 protocol field. But the
architectural effect is to allow a currently defined range of next headers,
and is easily extended. The next header will be a transport header, an extension
header, or ICMPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compipheadertos"><a name="rzai2compipv4ipv6__compipheadertos"><!-- --></a>IP header Type of Service (TOS)
byte</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Used by QoS and differentiated services to
designate a traffic class.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Designates the IPv6 traffic class, similarly
to IPv4. Uses different codes. Currently, IPv6 does not support TOS.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compinavsupp"><a name="rzai2compipv4ipv6__compinavsupp"><!-- --></a>iSeries Navigator support</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">iSeries Navigator provides a complete
configuration solution for TCP/IP.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same for IPv6. No CL commands are available
for IPv6 configuration.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__complanconnect"><a name="rzai2compipv4ipv6__complanconnect"><!-- --></a>LAN connection</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 "><p>Used by an IP interface to get to the
physical network. Many types exist; for example, token ring, and Ethernet.
Sometimes referred to as the physical interface, link, or line.</p>
</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />IPv6 can be used with any Ethernet adapters and is
also supported over virtual Ethernet between logical partitions.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compl2tp"><a name="rzai2compipv4ipv6__compl2tp"><!-- --></a>Layer 2 Tunnel Protocol (L2TP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">L2TP can be thought of as virtual PPP, and
works over any supported line type.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, the i5/OS implementation of L2TP does not support
IPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comploopaddr"><a name="rzai2compipv4ipv6__comploopaddr"><!-- --></a>loopback address</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">An interface with an address of <samp class="codeph">127.*.*.*</samp> (typically <samp class="codeph">127.0.0.1</samp>)
that can only be used by a node to send packets to itself. The physical interface
(line description) is named *LOOPBACK.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">The concept is the same as in IPv4. The single
loopback address is <samp class="codeph">0000:0000:0000:0000:0000:0000:0000:0001</samp> or <samp class="codeph">::1</samp> (shortened
version). The virtual physical interface is named <span><img src="./delta.gif" alt="Start of change" />*LOOPBACK<img src="./deltaend.gif" alt="End of change" /></span>.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compmtu"><a name="rzai2compipv4ipv6__compmtu"><!-- --></a>Maximum Transmission Unit (MTU)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Maximum transmission unit of a link is the
maximum number of bytes that a particular link type, such as Ethernet or modem,
supports. For IPv4, 576 is the typical minimum.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">IPv6 has an architected lower bound on MTU
of 1280 bytes. That is, IPv6 will not fragment packets below this limit. To
send IPv6 over a link with less than 1280 MTU, the link-layer must transparently
fragment and defragment the IPv6 packets.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compnetstat"><a name="rzai2compipv4ipv6__compnetstat"><!-- --></a>netstat</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">A tool to look at status of TCP/IP connections,
interfaces, or routes. Available using iSeries Navigator and 5250.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same for IPv6, and IPv6 is supported for
both 5250 and iSeries Navigator.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compnat"><a name="rzai2compipv4ipv6__compnat"><!-- --></a>Network Address Translation (NAT)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Basic firewall functions integrated into
TCP/IP, configured using iSeries Navigator.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, NAT does not support IPv6. More
generally, IPv6 does not require NAT. The expanded address space of IPv6 eliminates
the address shortage problem and enables easier renumbering.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compnetworktable"><a name="rzai2compipv4ipv6__compnetworktable"><!-- --></a>network table</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">On iSeries Navigator, a configurable table
that associates a network name with an IP address without mask. For example,
host Network14 and IP address 1.2.3.4.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, no changes are made to this table
for IPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compnodeinfo"><a name="rzai2compipv4ipv6__compnodeinfo"><!-- --></a>node info query</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Does not exist.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">A simple and convenient network tool that
should work like ping, except with content: an IPv6 node may query another
IPv6 node for the target's DNS name, IPv6 unicast address, or IPv4 address.
Currently, not supported.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comppacketfilter"><a name="rzai2compipv4ipv6__comppacketfilter"><!-- --></a>packet filtering</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">Basic firewall functions integrated into TCP/IP, configured
using iSeries Navigator.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 "><p>You cannot use packet filtering with IPv6.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comppacketforward"><a name="rzai2compipv4ipv6__comppacketforward"><!-- --></a>packet forwarding</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">The iSeries server can be configured to forward
IP packets it receives for nonlocal IP addresses. Typically, the inbound interface
and outbound interface are connected to different LANs.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p>IPv6 packets are not forwarded.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compping"><a name="rzai2compipv4ipv6__compping"><!-- --></a>PING</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">Basic TCP/IP tool to test reachability. Available using iSeries Navigator
and 5250.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 ">Same for IPv6, and IPv6 is supported, for both 5250
and iSeries Navigator.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compppp"><a name="rzai2compipv4ipv6__compppp"><!-- --></a>Point-to-Point Protocol (PPP)</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">PPP supports dialup interfaces over various modem and
line types.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS implementation of PPP does not support
IPv6.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compportrestrict"><a name="rzai2compipv4ipv6__compportrestrict"><!-- --></a>port restrictions</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">These iSeries panels allow a customer to configure
selected port number or port number ranges for TCP or UDP so that they are
only available for a specific profile.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><span><img src="./delta.gif" alt="Start of change" />Same for IPv6. Port restrictions
for IPv6 are identical to those available in IPv4. <img src="./deltaend.gif" alt="End of change" /></span></td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compports"><a name="rzai2compipv4ipv6__compports"><!-- --></a>ports</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">TCP and UDP have separate port spaces, each
identified by port numbers in the range 1-65535.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">For IPv6, ports work the same as IPv4. Because
these are in a new address family, there are now four separate port spaces.
For example, there are two TCP port 80 spaces to which an application can
bind, one in AF_INET and one in AF_INET6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compprivpubaddr"><a name="rzai2compipv4ipv6__compprivpubaddr"><!-- --></a>private and public addresses</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">All IPv4 addresses are public, except for
three address ranges that have been designated as private by IETF RFC 1918: <samp class="codeph">10.*.*.*
(10/8)</samp>, <samp class="codeph">172.16.0.0</samp> through <samp class="codeph">172.31.255.255
(172.16/12) </samp>, and <samp class="codeph">192.168.*.* (192.168/16)</samp>. Private
address domains are commonly used within organizations. Private addresses
cannot be routed across the Internet.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">IPv6 has an analogous concept, but with important
differences. <p>Addresses are public or temporary, previously termed anonymous.
See RFC 3041. Unlike IPv4 private addresses, temporary addresses can be globally
routed. The motivation is also different; IPv6 temporary addresses are meant
to shield the identity of a client when it initiates communication (a privacy
concern). Temporary addresses have a limited lifetime, and do not contain
an interface identifier that is a link (MAC) address. They are generally indistinguishable
from public addresses.</p>
<p>IPv6 has the notion of limited address scope
using its architected scope designations (see <a href="#rzai2compipv4ipv6__compaddrscope">address
scope</a>).</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compprotocoltable"><a name="rzai2compipv4ipv6__compprotocoltable"><!-- --></a>protocol table</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">On iSeries Navigator, a configurable table
that associates a protocol name with its assigned protocol number; for example,
UDP, 17. The system is shipped with a small number of entries: IP, TCP, UDP,
ICMP.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />The table can be used with
IPv6 without change.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compqos"><a name="rzai2compipv4ipv6__compqos"><!-- --></a>quality of service (QoS)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Quality of service allows you to request
packet priority and bandwidth for TCP/IP applications.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS implementation
of QoS does not support IPv6.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comprenumber"><a name="rzai2compipv4ipv6__comprenumber"><!-- --></a>renumbering</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Done by manual reconfiguration, with the
possible exception of DHCP. Generally, for a site or organization, a difficult
and troublesome process to avoid if possible.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Is an important architectural element of
IPv6, and is largely automatic, especially within the <samp class="codeph">/48</samp> prefix.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comproute"><a name="rzai2compipv4ipv6__comproute"><!-- --></a>route</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Logically, a mapping of a set of IP addresses
(might contain only one) to a physical interface and a single <span>next-hop</span> IP
address. IP packets whose destination address is defined as part of the set
are forwarded to the next hop using the line. IPv4 routes are associated with
an IPv4 interface, hence, an IPv4 address. <p>The default route is *DFTROUTE.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Conceptually, similar to
IPv4. One important difference: IPv6 routes are associated (bound) to a physical
interface (a link, such as ETH03) rather than an interface. One reason that
a route is associated with a physical interface is because source address
selection functions differently for IPv6 than for IPv4. See <a href="#rzai2compipv4ipv6__compsourceaddr">source
address selection</a>. <img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comprip"><a name="rzai2compipv4ipv6__comprip"><!-- --></a>Routing Information Protocol (RIP)</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">RIP is a routing protocol supported by the routed daemon.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 ">Currently, RIP does not support IPv6. IPv6 routing uses
static routes.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compservicestable"><a name="rzai2compipv4ipv6__compservicestable"><!-- --></a>services table</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">On the iSeries server, a configurable table
that associates a service name with a port and protocol; for example, service
name FTP-control, port 21, TCP and UDP. <p>A large number of well-known services
are listed in the services table. Many applications use this table to determine
which port to use.</p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">No changes are made to this table for IPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compsnmp"><a name="rzai2compipv4ipv6__compsnmp"><!-- --></a>Simple Network Management Protocol (SNMP)</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">SNMP is a protocol for system management.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS implementation
of SNMP does not support IPv6. <img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compsocketapi"><a name="rzai2compipv4ipv6__compsocketapi"><!-- --></a>sockets API</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">These APIs are the way applications use TCP/IP.
Applications that do not need IPv6 are not affected by sockets changes to
support IPv6.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">IPv6 enhances sockets so that applications
can now use IPv6, using a new address family: AF_INET6. <p>The enhancements
have been designed so that existing IPv4 applications are completely unaffected
by IPv6 and API changes. Applications that want to support concurrent IPv4
and IPv6 traffic, or IPv6-only traffic, are easily accommodated using IPv4-mapped
IPv6 addresses of the form <samp class="codeph">::ffff:a.b.c.d</samp>, where <samp class="codeph">a.b.c.d</samp> is
the IPv4 address of the client. </p>
<p>The new APIs also include support for
converting IPv6 addresses from text to binary and from binary to text. </p>
<p>See <a href="../rzab6/uafinet6.htm">Use AF_INET6 address
family</a> for more information about sockets enhancements for IPv6.</p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compsourceaddr"><a name="rzai2compipv4ipv6__compsourceaddr"><!-- --></a>source address selection</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">An application may designate a source IP
(typically, using sockets <samp class="codeph">bind()</samp>) . If it binds to INADDR_ANY,
a source IP is chosen based on the route.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">As with IPv4, an application can designate
a source IPv6 address using <samp class="codeph">bind()</samp>. Similarly to IPv4, it
can let the system choose an IPv6 source address by using in6addr_any. But
since IPv6 lines have many IPv6 addresses, the internal method of choosing
a source IP is different.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compstartstop"><a name="rzai2compipv4ipv6__compstartstop"><!-- --></a>starting and stopping</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Use STRTCP and ENDTCP to start or end TCP/IP.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same as IPv4. IPv4 and IPv6 are not started
or stopped independently of one another or independently of TCP/IP. That is,
you start and stop all of TCP/IP, not just IPv4 or IPv6. <p><img src="./delta.gif" alt="Start of change" />Any
IPv6 interfaces are automatically started if the AUTOSTART parameter = <samp class="codeph">*YES</samp> (the
default). IPv6 cannot be used or configured without IPv4. The IPv6 loopback
interface, <samp class="codeph">::1</samp>, will automatically be defined and activated
when IPv6 is started.<img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comptelnet"><a name="rzai2compipv4ipv6__comptelnet"><!-- --></a>Telnet</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Telnet allows you to log on and use a remote
computer as though you were connected to it directly.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 "><span><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS implementation
of Telnet does not support IPv6.<img src="./deltaend.gif" alt="End of change" /></span></td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comptraceroute"><a name="rzai2compipv4ipv6__comptraceroute"><!-- --></a>trace route</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Basic TCP/IP tool to do path determination.
Available using iSeries Navigator
and 5250.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Same for IPv6, and IPv6 is supported for
both 5250 and iSeries Navigator.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__comptransport"><a name="rzai2compipv4ipv6__comptransport"><!-- --></a>transport layers</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 "><p><img src="./delta.gif" alt="Start of change" />TCP, UDP, RAW. <img src="./deltaend.gif" alt="End of change" /></p>
</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">The same transports exist in IPv6.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compunspecaddr"><a name="rzai2compipv4ipv6__compunspecaddr"><!-- --></a>unspecified address</strong></td>
<td align="left" valign="top" width="32.95454545454545%" headers="d0e195 ">Apparently, not defined, as such. Socket
programming uses <samp class="codeph">0.0.0.0</samp> as INADDR_ANY.</td>
<td align="left" valign="top" width="39.77272727272727%" headers="d0e197 ">Defined as <samp class="codeph">::/128</samp> (128 0
bits). It is used as the source IP in some neighbor discovery packets, and
various other contexts, like sockets. Socket programming uses <samp class="codeph">::/128</samp> as <samp class="codeph">in6addr_any</samp>.</td>
</tr>
<tr><td valign="top" width="27.27272727272727%" headers="d0e193 "><strong id="rzai2compipv4ipv6__compvpn"><a name="rzai2compipv4ipv6__compvpn"><!-- --></a>virtual private networking (VPN)</strong></td>
<td valign="top" width="32.95454545454545%" headers="d0e195 ">Virtual private networking (using IPsec) allows you
to extend a secure, private network over an existing public network.</td>
<td valign="top" width="39.77272727272727%" headers="d0e197 "><p><img src="./delta.gif" alt="Start of change" />Currently, the i5/OS implementation of VPN does not support
IPv6. <img src="./deltaend.gif" alt="End of change" /></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzai2ipv6concepts.htm" title="Learn basic IPv6 concepts. If you are not sure what the differences are between IPv4 and IPv6, see detailed comparisons, such as how the IPv4 and IPv6 addresses compare to one another, or how IPv4 packet headers differ from IPv6 packet headers.">Concepts: IPv6</a></div>
</div>
</div>
</body>
</html>
Reference in New Issue Copy Permalink