Citations: Internet Name Server - Postel (ResearchIndex)

18 citations found. Retrieving documents...

Postel, J., "Internet Name Server," USC/Information Sciences Institute, IEN 116, August 1979.

Home/Search Document Not in Database Summary Related Articles Check

This paper is cited in the following contexts:

Development of the Domain Name System - Mockapetris, Dunlap (1988) (108 citations) (Correct)

....network addresses, gateways, etc. by the technology anyway, it was quite logical to want to partition the database and allow local control of local name and address spaces. A distributed naming system seemed in order. Existing distributed naming systems included the DARPA Internet s IEN116 [IEN 116] and the XEROX Grapevine [Birrell 82] and Clearinghouse systems [Oppen 83] The IEN116 services seemed excessively limited and host specific, and IEN116 did not provide much benefit to justify the costs of renovation. The XEROX system was then, and may still be, the most sophisticated name ....

Postel, Jon, "Internet Name Server", IEN 116, August 1979.

Design and Implementation of Intentional Names - Schwartz (1999) (2 citations) (Correct)

....systems. Several other network naming systems have been developed. The most commonly used naming system is the Domain Name System (DNS) whose development is detailed in [25] the most common implementation of DNS software, called BIND, is documented in [38] Other naming systems include IEN116 [32], XEROX Grapevine [6] and Active Names [36] Intentional names. There has been some prior work on making the case for intentional names [26, 19, 14] For example, the Semantic File System [17] uses intentional names for le retrieval. Descriptive names. Systems have been developed that de ....

J. B. Postel. Internet Name Server, August 1979. IEN 116.

Building Mobile Applications with the Rover Toolkit - Joseph, Tauber, Kaashoek (1996) (1 citation) (Correct)

....significant flexibility in the choice of mechanism, ranging from no control to application level locking with application specific algorithms for resolving uncoordinated updates to a single RDO. A common ad hoc approach taken by Lotus Notes [43] mail systems [47] and the Internet name service [48], among others, is to require all replicas of the data store to converge to the same value. Using convergent schemes, all connected clients eventually see the same value for the object but not necessarily all updates. Rover service proxies that provide read only data access tend to use ....

J. Postel, Internet Name Server, IEN-116, Aug. 1979.

Issues in Building Mobile-Aware Applications with the Rover Toolkit - Tauber (1996) (2 citations) (Correct)

....control. This trivial approach is appropriate for some applications. Applications can take advantage of other aspects of the Rover Toolkit without imposing a consistency control scheme. One common ad hoc approach taken by Lotus Notes [25] mail systems [37] and the Internet name service [36] among others, is to require all replicas of the data store to converge to the same values. Three techniques can be used to obtain convergence without serializing updates: append, replace with value, and commutative updates. In the first two, each update is time stamped or version vectored. ....

J. Postel. Internet Name Server. IEN-116, August 1979.

User Datagram Protocol - Postel (1980) (300 citations) Self-citation (Postel) (Correct)