RFC 760

RFC 760

RFC 760 is a standards-track document from the Internet Engineering Task Force series that specified an early method for host name lookup and address service mappings. Authored in January 1981, it provided guidelines for translating human-readable host identifiers into numerical addresses for networked systems and influenced subsequent protocols and infrastructure efforts. The memo sits among contemporaneous documents that shaped the ARPANET transition to the Internet and informed later work by organizations such as the Internet Engineering Task Force and the Defense Advanced Research Projects Agency.

Background and Purpose

RFC 760 emerged during a period of rapid development in packet-switched networking led by projects like ARPANET and institutions such as Stanford University and MIT. At the time, researchers at University of California, Berkeley, RAND Corporation, and Bolt Beranek and Newman were addressing practical issues in host identification across heterogeneous networks including networks operated by SRI International and Boeing. The document aimed to formalize procedures to map mnemonic host names—used by administrators and developers associated with groups like BBN and USC Information Sciences Institute—to network addresses used by routing systems developed at Xerox PARC and other research centers. RFC 760’s purpose also intersected with contemporaneous standards work at ISO and influenced discussions within the Internet Architecture Board about name resolution consistency for projects funded by DARPA.

Technical Specifications

The technical content of RFC 760 defined a file-based approach and behavioral expectations for converting alphanumeric host identifiers into numerical addresses understood by stacks implementing the Transmission Control Protocol and the Internet Protocol. It described record formats, lookup algorithms, and fallback behaviors for systems interacting with services developed at Bell Labs and AT&T research groups. The memo specified syntactic elements drawn from earlier specifications by authors affiliated with University College London and Carnegie Mellon University, and took into account networking practices from National Physical Laboratory research. RFC 760 detailed methods for representing canonical names, aliasing patterns, and addressing edge cases that systems at NASA Ames Research Center and academic labs had encountered. The document also referenced operational interactions with directory efforts at RAND and the evolving namespace discussions in committees involving ITU delegates.

Implementation and Deployment

Implementations of the specification informed stacks created by teams at Berkeley Software Distribution projects and by vendors such as DEC and Sun Microsystems. Early adopters included campus networks at University of Illinois and commercial research sites like IBM Research labs and Hewlett-Packard facilities. Deployment often involved updates to resolver libraries, system utilities maintained by groups at Columbia University and Yale University, and integration into existing middleware from Xerox and Hewlett-Packard Laboratories. Administrators at Los Alamos National Laboratory and Sandia National Laboratories adapted the approach to local conventions, while network operators at Bolt Beranek and Newman and ERSATZ-affiliated labs coordinated exchange of host tables. The practical rollout highlighted interoperability concerns that paralleled work being carried out in contemporaneous standards meetings at IETF sessions and regional networking workshops sponsored by NSF.

Security and Operational Considerations

RFC 760 addressed operational robustness, advising on validation and administrative controls to prevent misconfiguration across sites such as NASA centers and academic consortia like the CERN-linked research groups. The memo acknowledged threats from accidental misassignment and administrative errors, which were matters of concern at repositories maintained by institutions including Lawrence Berkeley National Laboratory and Argonne National Laboratory. While not a security protocol per se, RFC 760’s recommendations bore on later security models developed by researchers at MITRE and influenced threat analyses carried out in follow-on work by teams at SRI International and RAND Corporation. Operational guidance included suggestions for administrative delegation, consistency checks inspired by practices at Xerox PARC, and coordination policies resembling those later formalized by entities such as the Internet Assigned Numbers Authority.

Historical Impact and Legacy

Though eventually superseded by distributed, query-based mechanisms and databases championed by groups including Paul Mockapetris and Jon Postel, RFC 760 contributed foundational thinking to the evolution of name-address mapping. Its influence can be traced through the emergence of systems developed at University of Southern California, the Berkeley community’s resolver code, and standardization efforts that led to directory frameworks adopted by IETF working groups. The memo is part of the lineage connecting early ARPANET operational practice with modern infrastructure managed by organizations like ICANN and IANA, and it remains a historical touchstone cited in analyses by scholars at Stanford and Harvard studying the institutional evolution of internet architecture. RFC 760’s legacy also surfaces in archival collections preserved by Computer History Museum and in retrospectives authored by pioneers associated with BBN, Bolt Beranek and Newman, and the Internet Society.

Category:Internet standards