P. Mockapetris. Domain names: Implementation and specification. Technical Report RFC 883, Network Information Center, SRI International, September 1983.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....under the assumption that directories at the global level can be implemented using known name server technology. Perhaps the most advanced work of that kind to date has been Lampson s design [1, 16] an outgrowth of the work on Grapevine [2, 27] and the Clearinghouse [22] The Domain Name service [19, 20] of the DARPA Internet is a more limited system in the same class. 21 Additional work in this area is surveyed in Terry s thesis [30] These global name services are typically used to map from names to unique identifiers for hosts, mailboxes, or services. As mentioned previously, the ....

P. Mockapetris. Domain names: Implementation and specification. Technical Report RFC 883, Network Information Center, SRI International, September 1983.

....1 components. Moreover, a naming system must provide trustworthy service even though parts of the system may belong to many autonomous and mutually suspicious groups different departments, corporations, and even countries. Some progress on this large scale design problem has been reported [2, 13, 16, 19, 22]; however, the performance of these systems appears inadequate for file naming at best, it is adequate for naming hosts, mailboxes, and other relatively infrequently accessed objects. Name lookup operations are a significant factor in system performance. For instance, Leffler et al. 17] ....

....under the assumption that directories at the global level can be implemented using known name server technology. Perhaps the most advanced work of that kind to date has been Lampson s design [1, 16] an outgrowth of the work on Grapevine [2, 27] and the Clearinghouse [22] The Domain Name service [19, 20] of the DARPA Internet is a more limited system in the same class. 21 Additional work in this area is surveyed in Terry s thesis [30] These global name services are typically used to map from names to unique identifiers for hosts, mailboxes, or services. As mentioned previously, the ....

P. Mockapetris. Domain names: Concepts and facilities. Technical Report RFC 882, Network Information Center, SRI International, September 1983.

....in important respects. Decentralized naming explores the ideas of multicast for fault tolerance and caching with on use consistency for efficiency, not considered in the Lampson design. 2.4 Other Related Work 2.4. 1 Domain Naming The Domain Name service recently adopted in the DARPA Internet [30,31] is a simpler system in the same class as Grapevine and the Lampson design. The design is simplified by assuming that updates are infrequent enough to be handled manually by human administrators the name service interface does not define any way for a client program to request the addition or ....

P. Mockapetris. Domain Names: Implementation and Specification. Technical Report RFC 883, Network Information Center, SRI International, September 1983.

....directories near the root of the tree can be expected to have substantially different usage characteristics from those near the leaves. Extrapolating from the behavior seen in smaller hierarchical naming systems, such as the UNIX [34] file system and the DARPA Internet Domain Naming service [30], I expect the directories in a large scale system to fall into several broad usage classes, with the following characteristics. Directories near the root are of global interest; that is, the entries they contain are accessed by nearly all client hosts. They must therefore be very highly ....

....in important respects. Decentralized naming explores the ideas of multicast for fault tolerance and caching with on use consistency for efficiency, not considered in the Lampson design. 2.4 Other Related Work 2.4. 1 Domain Naming The Domain Name service recently adopted in the DARPA Internet [30,31] is a simpler system in the same class as Grapevine and the Lampson design. The design is simplified by assuming that updates are infrequent enough to be handled manually by human administrators the name service interface does not define any way for a client program to request the addition or ....

P. Mockapetris. Domain Names: Concepts and Facilities. Technical Report RFC 882, Network Information Center, SRI International, September 1983.

....form YYYYMMDD where YYYY represents the year, MM represents the month of the year (01 through 12) and DD represents the day of the month (01 through 31) For example, June 24, 1996 is represented as 19960624. hemail addressi is as described in RFC 822[11] hdns namei is as described in RFC 1034[22]. hpersoni is either a full name of a person or a uniquely assigned NIC handle. Its syntax has the following form: firstname [ initials ] lastname nic handle e.g. John E Doe JED31 Alaettinoglu et al. Expires October 23, 1997 [Page 5] Internet Draft RPSL April 23, 1997 A NIC ....

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comment RFC-1034, Network Information Center, November 1987.

....information services are easily parallelized, since (by protocol design) the individual transactions are completely independent. Successful parallelization means avoiding any unnecessary resource bottlenecks, such as network interfaces. Current practice in implementing the Domain Name System [11] (DNS) helps solve this problem. When a single server name is bound to several distinct hosts with equal preference values, DNS servers return the bindings in random order; this causes DNS clients (which generally try the bindings in the order returned) to spread their connections among the server ....

P. Mockapetris. Domain Names - Concepts and Facilities. RFC 1034, Network Information Center, SRI International, November, 1987.

....and their corresponding IP address. If the IP address of this domain is found in the cache of the local name server, the IP address is returned to the client. If not, the local name server presents itself as a client, formats a message, finds the best servers to ask, sends the message to port 53 [Mockapetris 87] at these name servers, and waits for a reply. If a timeout occurs, a failure message will be sent back to the client. CHAPTER 2. BACKGROUND 22 Almost every wide area TCP connection, whether it be SMTP, Telnet, or FTP, begins with two or three DNS requests. This might not generate wide area ....

P. Mockapetris, Domain Names -- Implementation and Specification) , RFC 1035, Network Information Center, SRI International, Menlo Park, California, 1987.

....form YYYYMMDD where YYYY represents the year, MM represents the month of the year (01 through 12) and DD represents the day of the month (01 through 31) For example, June 24, 1996 is represented as 19960624. hemail addressi is as described in RFC 822[8] hdns namei is as described in RFC 1034[16]. hnic handlei is a uniquely assigned identifier[13] used by routing, address allocation, and other registries to unambiguously refer to contact information. person and role classes map NIC handles to actual person names, and contact information. hfree formi is a sequence of ASCII characters. ....

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comment RFC-1034, Network Information Center, November 1987.

....i for i t is a viewserver id, x 0 is a top level viewserver id, x t is the id of u, and x i is a parent of x i 1 . A node may have many addresses since the parent child relationship is many to many. If a source wants a domain level source route to a destination, it first queries the name servers [14] to obtain a set of addresses for the destination 9 . Then, it queries viewservers to obtain an accumulated view containing both its domain and the destination s domain. Nodes can reach the viewservers in their domains using the intra domain routing protocol of the domain. Otherwise, we assume ....

P. V. Mockapetris. Domain names - concepts and facilities. Request for Comment RFC-1034, Network Information Center, November 1987.

....of hosts, with a Clearinghouse like registration service available as a facade through which services in other clusters can be located. Other examples of systems in this class include the registration service of Grapevine [2,21] and the Domain Name service recently adopted in the DARPA Internet [14,15]. 6.2 Network File Systems Another class of naming system arises in distributed systems that are built by tying together a number of instances of existing centralized systems. Some recent examples include the Newcastle Connection [3] and Sun Microsystems Network File System [20] an older ....

P. Mockapetris. Domain Names: Implementation and Specification. Technical Report RFC 883, Network Information Center, SRI International, September 1983.

....of hosts, with a Clearinghouse like registration service available as a facade through which services in other clusters can be located. Other examples of systems in this class include the registration service of Grapevine [2,21] and the Domain Name service recently adopted in the DARPA Internet [14,15]. 6.2 Network File Systems Another class of naming system arises in distributed systems that are built by tying together a number of instances of existing centralized systems. Some recent examples include the Newcastle Connection [3] and Sun Microsystems Network File System [20] an older ....

P. Mockapetris. Domain Names: Concepts and Facilities. Technical Report RFC 882, Network Information Center, SRI International, September 1983.

....and completely insecure. We do not allow these services to cross our screening router, and we do not run the corresponding servers on our trusted systems. 3.5.5. Name service Name service (translation between host names and addresses) in the Internet is provided by the Domain Name System (DNS) [9, 10]. DNS is a distributed, hierarchically organized system in which each organization runs a set of DNS servers for its subtree of the name space. Because it is useful for insiders to be able to translate names for outside hosts, and vice versa, we allow DNS lookup packets to transit the screening ....

Paul V. Mockapetris. Domain names - implementation and specification. RFC 1035, Network Information Center, SRI International, November, 1987.

....and completely insecure. We do not allow these services to cross our screening router, and we do not run the corresponding servers on our trusted systems. 3.5.5. Name service Name service (translation between host names and addresses) in the Internet is provided by the Domain Name System (DNS) [9, 10]. DNS is a distributed, hierarchically organized system in which each organization runs a set of DNS servers for its subtree of the name space. Because it is useful for insiders to be able to translate names for outside hosts, and vice versa, we allow DNS lookup packets to transit the screening ....

Paul V. Mockapetris. Domain names - concepts and facilities. RFC 1034, Network Information Center, SRI International, November, 1987.

No context found.

P. Mockapetris. Domain names --- implementation and specification. Internet Request for Comment 1035, Network Information Center, November 1987.

No context found.

P. Mockapetris. Domain names --- concept and facilities. Internet Request for Comment 1034, Network Information Center, November 1987.

No context found.

P. Mockapetris, Domain Names - Concepts and facilities, Network Information Center, Request for Comments, RFC 1034, Nov. 87, 55 P.

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