| S. Cheshire, B. Aboba, and E. Guttman. Dynamic Configuration of IPv4 Link-Local Addresses (RFC 3927), May 2005. http://ietf.org/rfc/rfc3927.txt. |
....Interface binding does little good if the user must manually configure IP address and netmask. To enable transparent network access, interface IP configuration (assigning IP addresses and netmasks to interfaces) must also be automatic. Link local (LL) addresses, in either IPv6 [9] or IPv4 [4], provide autoconfiguration. Unfortunately, addresses with scope restricted to a single link provide little support for persistent communication. These transient addresses cannot be used as endpoints for a transport layer connection, or that connection will fail upon moving. There is no method to ....
....counterpart. B. IP Autoconfiguration A network interface must be configured with an IP address and subnet mask before IP can use it. In traditional IP, providing a unique address to each interface is a problem in its own right, requiring either administrative configuration or protocol solutions [4], 6] 7] 21] These heavy weight solutions require significant setup time to allocate an interface address, and create another problem when considering mobility: a transport flow cannot outlive the IP addresses used to identify its endpoints. If those addresses are transient, ....
S. Cheshire, B. Aboba, and E. Guttman. Dynamic configuration of IPv4 link-local addresses. Internet Draft (Work in Progress) draft-ietf-zeroconf-ipv4-linklocal07. txt, Internet Engineering Task Force, August 2002.
....of possible MANET topologies. All MANET nodes are not guaranteed to be reachable from each other through at most one intermediate node. Hence, link level broadcasts are not guaranteed to reach all MANET nodes. As a result, duplicate address detection (DAD) as described in the Zeroconf solutions [10] is not feasible. As per the Zeroconf charter (at the time of submitting this manuscript) topologies like MANETs are out of the scope of the working group. B. PMWRS Solution A solution, similar to that of Zeroconf, was proposed by Perkins, Malinen, Wakikawa, Royer and Sun in an Internet ....
....This protocol is tied to the underlying routing protocol as it specifies the routes to be used by its messages. This impacts the ability of the protocol to operate effectively in the presence of pro active routing protocols. 2. It uses the 169.254 16 IP address block. However, as stated in [10], this address block is registered with IANA for link local unique addressing. Any router receiving a packet with an address from this block in the source or destination field(s) should discard the packet. So, even after nodes are successfully configured with these addresses, they will be unable ....
[Article contains additional citation context not shown here]
S. Cheshire and B. Aboba, "Dynamic Configuration of IPv4 LinkLocal Addresses, draft-ietf.zeroconf-ipv4-linklocal-03.txt (expires December 22, 2001.
....must deal with. Hopefully, best known methods develop along with deployment experience. 6] In fact, they are not setting any real security requirements in their requirement paper. IETF ZeroConf WG has also published a draft of one protocol, Dynamic Configuration of IPv4 link local addresses [8]. In that paper they only say that the mechanisms the protocol uses are insecure. 5.3 Security requirements according to my own visions of different situations I described before Security requirements on the open networks Readily configured computers: When readily configured computers are ....
....into this rule is an empty computer, where is no pre configured secrecies to authenticate the machine. 6 Some examples of what has been done 6.1 IETF, Dynamic Configuration of IPv4 link local addresses This is an example of Zero Configuration protocol as the IETF is defining this concept. [8] Technical overview: 7 HUT TML 2000 Tik 110.501 Seminar on Network Security If a host without IP address is connected to a network and it does not get a valuable address in a more sophisticated way; such as with DHCP, it has the possibility to get a link local address from 196.254 16 address ....
[Article contains additional citation context not shown here]
S. Cheshire. Dynamic Configuration of IPv4 link-local addresses, draft-ietfzeroconf -ipv4-linklocal-00.txt. http://www.ietf.org/internet-drafts/draft-ietf-zeroconfipv4 -linklocal-00.txt, 8th October 2000. A work in progress.
No context found.
Stuart Cheshire, Bernard Aboba, and Erik Guttman. Dynamic Configuration of IPv4 Link-Local Addresses, 2002. IETF Internet Draft, http://files.zeroconf.org/ draft-ietf-zeroconf-ipv4-linklocal.txt.
No context found.
S. Cheshire, B. Aboba, and E. Guttman. Dynamic Configuration of IPv4 Link-Local Addresses (RFC 3927), May 2005. http://ietf.org/rfc/rfc3927.txt.
No context found.
S. Cheshire, B. Adoba. Dynamic configuration of IPv4 link-local addresses. Internet-draft, 2001. http://www.ietf.org/internet-drafts/ draft-ietf-zeroconf-ipv4-linklocal-04.txt
No context found.
S. Cheshire, B. Adoba, and E. Guttman. Dynamic configuration of IPv4 link-local addresses. http://www.ietf.org/internet-drafts/- draft-ietf-zeroconf-ipv4-linklocal07. txt, August 2002. DRAFT.
No context found.
S. Cheshire and B. Aboba. Dynamic configuration of IPv4 link-local addresses. Internet Draft, Internet Engineering Task Force, April 2002. URL http://www.ietf.org/internet-drafts/ draft-ietf-zeroconf-ipv4-linklocal-%05.txt. Work in progress.
No context found.
Stuart Cheshire and Bernard Adoba. Dynamic configuration of IPv4 link-local addresses. http://www.ietf.org/internet-drafts/draftietf -zeroconf-ipv4-linklocal-04.txt, July 2001. DRAFT.
No context found.
S. Cheshire, B. Aboba and E. Guttman. Dynamic Configuration of IPv4 Link-Local Addresses. Internet-Draft, August 2002. draft-ietf-zeroconf-ipv4-linklocal-07.txt - Workin -progress.
No context found.
S. Cheshire and B. Aboba. Dynamic Configuration of IPv4 Link-Local Addresses. IETF Internet Draft, draft-ietf-zeroconf-ipv4-linklocal04. txt, July 2001. (Work in Progress).
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC