![]() Sandy Ginoza joined USC/ISI in 1999 to work on RFC editing, and Alice Hagens in 2005. federal government, the Internet Society, acting on behalf of the IETF, contracted with the Networking Division of the University of Southern California (USC) Information Sciences Institute (ISI) to assume the editorship and publishing responsibilities under the direction of the IAB. On his death in 1998, his obituary was published as RFC 2468.įollowing the expiration of the original ARPANET contract with the U.S. From 1969 until 1998, Jon Postel served as the RFC editor. Feinler to distribute the RFCs along with other network information. The ARC became the first network information center ( InterNIC), which was managed by Elizabeth J. The Augmentation Research Center (ARC) at Stanford Research Institute, directed by Douglas Engelbart, is another of the four first of what were ARPANET nodes and the source of early RFCs. Many of the subsequent RFCs of the 1970s also came from UCLA, because UCLA is one of the first of what were Interface Message Processors (IMPs) on ARPANET. In effect, it included anyone who wanted to join the meetings and discussions about the project. Rather than being a formal committee, it was a loose association of researchers interested in the ARPANET project. In RFC 3, which first defined the RFC series, Crocker started attributing the RFC series to the Network Working Group. Although written by Steve Crocker, the RFC had emerged from an early working group discussion between Steve Crocker, Steve Carr, and Jeff Rulifson. ![]() RFC 1, titled "Host Software", was written by Steve Crocker of the University of California, Los Angeles (UCLA), and published on April 7, 1969. In December 1969, researchers began distributing new RFCs via the newly operational ARPANET. This less formal style is now typical of Internet Draft documents, the precursor step before being approved as an RFC. The RFC leaves questions open and is written in a less formal style. ![]() Unlike the modern RFCs, many of the early RFCs were actual Requests for Comments and were titled as such to avoid sounding too declarative and to encourage discussion. The authors of the first RFCs typewrote their work and circulated hard copies among the ARPA researchers. Today, it is the official publication channel for the Internet Engineering Task Force (IETF), the Internet Architecture Board (IAB), and – to some extent – the global community of computer network researchers in general. The inception of the RFC format occurred in 1969 as part of the seminal ARPANET project. Federal government work, such as the National Highway Traffic Safety Administration. ![]() Outside of the Internet community, other documents also called requests for comments have been published in U.S. According to Crocker, the documents "shape the Internet's inner workings and have played a significant role in its success", but are not widely known outside the community. RFCs have since become official documents of Internet specifications, communications protocols, procedures, and events. The RFC system was invented by Steve Crocker in 1969 to help record unofficial notes on the development of ARPANET. However, many RFCs are informational or experimental in nature and are not standards. The IETF adopts some of the proposals published as RFCs as Internet Standards. It is submitted either for peer review or to convey new concepts, information, or, occasionally, engineering humor. An RFC is authored by individuals or groups of engineers and computer scientists in the form of a memorandum describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. For the Wikipedia process, see Wikipedia:Requests for comment.Ī Request for Comments ( RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF).
0 Comments
Leave a Reply. |