Search results
Results from the WOW.Com Content Network
This is a partial list of RFCs (request for comments memoranda). A 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).
[nb 1] He was instrumental in forming a Network Working Group (NWG) in 1969 and was the instigator of the Request for Comment (RFC) series, [6] authoring the first RFC [7] and many more. [8] Crocker led other graduate students, including Jon Postel and Vint Cerf, in designing a host-host protocol known as the Network Control Program (NCP).
Although written by Steve Crocker, the RFC had emerged from an early working group discussion between Steve Crocker, Steve Carr, and Jeff Rulifson. In RFC 3, which first defined the RFC series, Crocker started attributing the RFC series to the Network Working Group. Rather than being a formal committee, it was a loose association of researchers ...
Crocker was the author of RFC 822, which was published in 1982 to define the format of Internet mail messages, [5] and he was the first listed author of the earlier RFC 733 on which it was based in 1977. [6]
Dalal co-authored the first Transmission Control Program specification, with Vint Cerf and Carl Sunshine between 1973 and 1974. [133] [142] It was published as RFC 675 (Specification of Internet Transmission Control Program) in December 1974. [143] It first used the term internet as a shorthand for internetworking, and later RFCs repeated this ...
When an RFC becomes an Internet Standard (STD), it is assigned an STD number but retains its RFC number. When an Internet Standard is updated, its number is unchanged but refers to a different RFC or set of RFCs. For example, in 2007 RFC 3700 was an Internet Standard (STD 1) and in May 2008 it was replaced with RFC 5000.
Almost every April Fools' Day (1 April) since 1989, the Internet RFC Editor has published one or more humorous Request for Comments (RFC) documents, following in the path blazed by the June 1973 RFC 527 called ARPAWOCKY, a parody of Lewis Carroll's nonsense poem "Jabberwocky". The following list also includes humorous RFCs published on other dates.
Since 1992, a new document was written to specify the evolution of the basic protocol towards its next full version. It supported both the simple request method of the 0.9 version and the full GET request that included the client HTTP version. This was the first of the many unofficial HTTP/1.0 drafts that preceded the final work on HTTP/1.0. [3]