The Core Standards of the Internet Are Named as Humble "Requests for Comments"
In April 1969, researcher Steve Crocker authored 'RFC 1' to document host software for the early ARPANET. Fearing that formal official language might offend senior colleagues or sound imperious, Crocker titled the memo 'Request for Comments.' The humble phrase caught on, becoming the permanent naming scheme for every official technical protocol governing the modern internet.
The Accidental Rulebook of the Internet
In the late 1960s, the United States Advanced Research Projects Agency funded the construction of the ARPANET, an experimental network designed to connect disparate computer systems across research institutions. Because packet-switching network technology was largely untrod ground, researchers had to invent the underlying communication protocols from scratch. A collective of graduate students and staff from participating universities formed the Network Working Group to tackle the practical problems of machine-to-machine communication.
When the time came to write down their early technical discussions, the researchers were not working under any formal administrative mandate. They needed a way to distribute notes, raise architectural questions, and exchange technical proposals without presenting their ideas as finished doctrine. This informal documentation mechanism would ultimately become the foundation for all technical specifications governing the global internet.
The Hesitation Behind RFC 1
Steve Crocker, then a graduate student at the University of California, Los Angeles, took responsibility for writing the very first memo. He was acutely conscious of the group's informal standing. Crocker worried that senior researchers, university professors, or military program managers might view their notes as presumptive or authoritarian if they carried titles suggesting official policy.
To emphasize that the document was merely an open invitation for peer input, Crocker titled the memo 'Request for Comments.' RFC 1, titled 'Host Software,' was dated April 7, 1969. The phrase was chosen explicitly to sound humble, collaborative, and unpretentious. The working group agreed that anyone could write an RFC, that questions were just as valid as answers, and that no technical contribution was too informal to be circulated.