This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.
July 2008
·
7 Reads
This article describes recent trends and activities related to the standardization, resource management, and deployment of IPv6 (Internet protocol version 6), which is seen as an effective solution to the expected shortage of IPv4 (Internet protocol version 4) addresses.
January 2008
·
25 Reads
·
3 Citations
There are some problematic cases when using the default address selection mechanism that RFC 3484 defines. This document describes additional requirements that operate with RFC 3484 to solve the problems.
7 Reads
·
13 Citations
A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OSs. But, it has been too difficult to use operationally for several reasons. In some environments where multiple prefixes are assigned on a single physical link, the host using the default address selection rules will experience some trouble in communication. This document describes the possible problems that end hosts could encounter in an environment with multiple prefixes.
... B will use an NA to reply when B receives the NS. A obtains the MAC address of B when A receives the NA, thus the two parties can communicate [10]. The NA message and NS message used in the communication are shown in Figure 5(a) and Figure 5(b). ...
... The DNS answers with one or several addresses. The application then initiates a connection with one of the obtained addresses (through default address selection) [18,35,36]. ...
January 2008
