| ARPANET Working Group Requests for Comment, DDN Network Information Center, SRI International, Menlo Park, CA. Dynamic Host Configuration Protocol (DHCP), October 1993. RFC-1541. |
....There are two basic approaches to this problem. The first relies on a centralized server at a well known location that provides the necessary bootstrap. In this approach, the client obtains necessary rendezvous information from a server, e.g. using the Dynamic Host Configuration Protocol (DHCP) [8]. In contrast to this approach where a client pulls down service location information from a well known point, multicast communication can be exploited to push service location information out to multicast listeners. In this model, a client listens on a well known multicast address over which ....
ARPANET Working Group Requests for Comment, DDN Network Information Center, SRI International, Menlo Park, CA. Dynamic Host Configuration Protocol (DHCP), October 1993. RFC-1541.
....identified two basic approaches to this problem. The first relies on a centralized server at a well known location that provides the necessary bootstrap. In this approach, the client obtains necessaryrendezvousinformation from a server, e.g. using the Dynamic Host Configuration Protocol (DHCP) [6]. In contrast to this approach where a client pulls down service location information from a well known point, multicast communication can be exploited to push service location information out to multicast listeners. In this model, a client listens on a well known multicast address over which ....
ARPANET WORKING GROUP REQUESTS FOR COMMENT, DDN NETWORK INFORMATION CENTER. Dynamic Host Configuration Protocol (DHCP). SRI International, Menlo Park, CA, October 1993. RFC-1541.
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