RFC 1123

RFC 1123
Title	RFC 1123
Author	David D. Clark
Published	October 1989
Status	Best Current Practice
Series	Request for Comments
Number	1123

RFC 1123

RFC 1123 is a standards-track document that supplements earlier Internet engineering guidance by specifying host requirements for Internet protocols. It clarifies operational expectations for ARPANET, DARPA, University of California, Berkeley, Stanford Research Institute, and other institutions involved in early packet switching research, and it provides practical prescriptions used by implementers at Bell Labs, AT&T, IBM, Digital Equipment Corporation, and academic sites such as MIT and Carnegie Mellon University.

Introduction

RFC 1123, authored under the auspices of organizations including Internet Engineering Task Force, Internet Architecture Board, and contributors from BBN Technologies and Xerox PARC, presents host requirements complementary to protocol definitions found in related specifications. It addresses interoperability concerns that affected deployments linking nodes at University College London, University of California, Los Angeles, NASA Ames Research Center, and international sites like University of Cambridge and CERN. The document sits alongside foundational standards from Robert Kahn, Vint Cerf, Jon Postel, and other pioneers associated with the TCP/IP protocol suite.

Background and Context

Drafted in the late 1980s, RFC 1123 emerged from operational experience accumulated in networks developed by ARPA, NSFNET, MILNET, and research projects at SRI International. The text synthesizes lessons from implementations by vendors such as Sun Microsystems, Hewlett-Packard, Siemens, and NEC and from academic protocol testing at Princeton University, University of Illinois Urbana-Champaign, and Columbia University. Influences include prior documents like the foundational RFC 793, RFC 791, and community discussions in venues such as IETF meetings, IAB workshops, and conferences including SIGCOMM and USENIX. The operational issues reflect interactions with services like Telnet, SMTP, FTP, and routing systems such as BGP and OSPF.

Content and Technical Specifications

RFC 1123 refines requirements for host behavior in areas including addressing, name resolution, and transport-layer interactions. It specifies handling of IPv4 semantics established in RFC 791 while anticipating transition scenarios involving IPng efforts and later IPv6 work promoted by groups at Internet Society and ICANN-related research. The document prescribes specifics for TCP connection management related to retransmission timers derived from algorithms discussed by Van Jacobson and measurements from MAE-East and MAE-West. It details interactions with DNS as implemented by teams at Paul Mockapetris-affiliated projects, and it addresses character handling in protocols used by DECnet and legacy systems from X.25 networks. Sections cover error reporting, diagnostics reflected in tools like ping and traceroute, and security considerations that later informed work by CERT Coordination Center and researchers at SRI CERT. The specification influenced implementation choices in stacks produced by Microsoft, Novell, Cisco Systems, and research stacks maintained at Bellcore.

Impact and Adoption

RFC 1123 rapidly became a touchstone for vendors, administrators, and standards bodies such as ISO and ITU-T when aligning protocol behavior across heterogeneous equipment. Implementers at Cisco Systems incorporated guidance into router firmware used in backbone deployments linking MAE-East, SprintNet, and commercial carriers. Academic networks at Stanford University, Princeton University, and Brown University adopted the recommendations for host configuration and diagnostics. The document informed interoperability testing platforms used at NIST and regulatory discussions involving Federal Communications Commission and international regulators in OECD forums. The guidance also filtered into curriculum and training at Carnegie Mellon University and Georgia Institute of Technology for networking courses that taught TCP/IP internals derived from practical requirements in the text.

Revisions and Related RFCs

RFC 1123 functions in tandem with companion documents and successors from the RFC series, complementing earlier protocol definitions like RFC 821 and RFC 959 and interacting with later operational updates including revisions that addressed evolving address needs tied to IPv6 and security updates advocated by IETF Security Area participants. Subsequent RFCs and Best Current Practice documents produced by working groups such as IETF OPSAWG and IETF MARTINI communities referenced RFC 1123 when clarifying host requirements, and the document was cited in discussions involving standards from W3C and implementation considerations raised by IEEE 802 working groups. Authors and editors from institutions including MITRE Corporation, Sun Labs, and Bell Labs Research contributed to the lineage of related specifications.

Legacy and Historical Significance

RFC 1123 remains a historically significant bridge between protocol specification and operational practice, influencing vendors and research labs from Bell Labs to Xerox PARC and shaping practices in operational networks like NSFNET and early commercial Internet backbones. Its practical orientation informed later education at Massachusetts Institute of Technology, deployment strategies at Cisco Systems and Juniper Networks, and security modeling at Carnegie Mellon University's Software Engineering Institute. The document's emphasis on implementability and interoperability contributed to the maturation of the Internet, affecting governance discussions in bodies such as ICANN and Internet Society and echoing in historical treatments by historians at Computer History Museum and analysts at RAND Corporation.

Category:Internet standards