The text form of the IPv4 address is nnn.nnn.nnn.nnn, where 0<=nnn<=255, and each n is a decimal digit. Leading zeros can be omitted. Maximum number of print characters is 15, not counting a mask.
Depending on the subnet prefix, IPv6 has a more complicated architecture than IPv4.
The number of IPv6 addresses is 1028 (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 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, where each x is a hexadecimal digit, representing 4 bits. Leading zeros can be omitted. The double colon (::) can be used once in the text form of an address, to designate any number of 0 bits. For example, ::ffff:10.120.78.40 is an IPv4-mapped IPv6 address. (See RFC 3513 for details.
To view this RFC, see RFC Editor (www.rfc-editor.org/rfcsearch.html).
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.
Some IPv6 addresses have, by definition, infinite preferred and valid lifetimes; for example link-local (see address scope).
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.
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 %zid where zid is a number (usually small) or a name. The zone ID is written after the address and before the prefix. For example, 2ba::1:2:14e:9a9b:c%3/48.
Same for IPv6, and IPv6 is supported.
You must configure a newly installed system before it can communicate with other systems; that is, IP addresses and routes must be assigned.
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.
Applications also accept IP addresses and then use DNS to get host names using gethostbyaddr().
For IPv4, the domain for reverse lookups is in-addr.arpa.
The socket API gethostbyname() only supports IPv4. For IPv6, a new getaddrinfo() API is used to obtain (at application choice) IPv6 only, or IPv4 and IPv6 addresses.
For IPv6, the domain used for reverse lookups is ip6.arpa, and if not found then ip6.int (see API getnameinfo()).
Used to dynamically obtain an IP address and other configuration information. The iSeries supports a DHCP server for IPv4.
Currently, the i5/OS™ implementation of DHCP does not support IPv6.
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.
Can be started and stopped independently of each other and independently of TCP/IP using STRTCPIFC and ENDTCPIFC commands and using iSeries Navigator.
Can be started and stopped independently of each other and independently of TCP/IP using iSeries Navigator only.
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.
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.
IPv6 can be used with any Ethernet adapters and is also supported over virtual Ethernet between logical partitions.
You cannot use packet filtering with IPv6.
IPv6 packets are not forwarded.
Currently, the i5/OS implementation of PPP does not support IPv6.
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.
IPv6 has the notion of limited address scope using its architected scope designations (see address scope).
The table can be used with IPv6 without change.
Currently, the i5/OS implementation of QoS does not support IPv6.
The default route is *DFTROUTE.
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 source address selection.
A large number of well-known services are listed in the services table. Many applications use this table to determine which port to use.
Currently, the i5/OS implementation of SNMP does not support IPv6.
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 ::ffff:a.b.c.d, where a.b.c.d is the IPv4 address of the client.
The new APIs also include support for converting IPv6 addresses from text to binary and from binary to text.
See Use AF_INET6 address family for more information about sockets enhancements for IPv6.
Any IPv6 interfaces are automatically started if the AUTOSTART parameter = *YES (the default). IPv6 cannot be used or configured without IPv4. The IPv6 loopback interface, ::1, will automatically be defined and activated when IPv6 is started.
TCP, UDP, RAW.
Currently, the i5/OS implementation of VPN does not support IPv6.