24.05.2014 Views

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

AIX Version 4.3 Differences Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Anycast<br />

• Site-local<br />

– Valid only on hosts sharing a site with the source node (for<br />

example, multicasts within IBM Austin).<br />

– Prefix is ff05::/16 or ff15::/16.<br />

• Organization-local.<br />

– Valid only on hosts sharing organization with the source node<br />

(for example, multicasts to all of IBM).<br />

– Prefix is ff08::/16 or ff18::/16.<br />

• The 0 or 1 part in these prefixes indicates whether the address is<br />

permanently assigned (1) or temporarily assigned (0).<br />

An identifier for a set of interfaces (typically belonging to different<br />

nodes). An anycast address is an address that has a single sender,<br />

multiple listeners, and only one responder (normally the nearest one,<br />

according to the routing protocols' measure of distance). An example<br />

may be several Web servers listening on an anycast address. When a<br />

request is sent to the anycast address, only one responds.<br />

Anycast addresses are indistinguishable from unicast addresses. A<br />

unicast address becomes an anycast address when more than one<br />

interface is configured with that address.<br />

Note: There are no broadcast addresses in IPv6, their function being<br />

superseded by multicast addresses.<br />

7.1.3 Neighbor Discovery/Stateless Address Autoconfiguration<br />

Neighbor Discovery (ND) protocol for IPv6 is used by nodes (hosts and routers)<br />

to determine the link-layer addresses for neighbors known to reside on attached<br />

links and maintain per-destination routing tables for active connections. Hosts<br />

also use Neighbor Discovery to find neighboring routers that forward packets on<br />

their behalf and detect changed link-layer addresses. Neighbor Discovery<br />

protocol (NDP) uses the ICMPv6 protocol with a unique message types to<br />

achieve the above function. In general terms, the IPv6 Neighbor Discovery<br />

protocol corresponds to a combination of the IPv4 protocols Address Resolution<br />

Protocol (ARP), ICMP Router Discovery (RDISC), and ICMP Redirect (ICMPv4),<br />

but with many improvements over these IPv4 protocols.<br />

IPv6 defines both a stateful and stateless address autoconfiguration mechanism.<br />

Stateless autoconfiguration requires no manual configuration of hosts, minimal (if<br />

any) configuration of routers, and no additional servers. The stateless<br />

mechanism allows a host to generate its own addresses using a combination of<br />

locally available information and information advertised by routers. Routers<br />

advertise prefixes that identify the subnet(s) associated with a link, while hosts<br />

generate an interface-token that uniquely identifies an interface on a subnet. An<br />

address is formed by combining the two. In the absence of routers, a host can<br />

only generate link-local addresses. However, link-local addresses are sufficient<br />

for allowing communication among nodes attached to the same link.<br />

7.1.3.1 NDP Application Kernel Support<br />

For kernel function, a new version of the netinet kernel extension has been<br />

provided that contains code to handle both IPv4 and IPv6. New special<br />

processing handled by the kernel (or NDP applications) includes:<br />

150 <strong>AIX</strong> <strong>Version</strong> <strong>4.3</strong> <strong>Differences</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!