Search results
Results from the WOW.Com Content Network
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 ...
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).
Crocker was the author of RFC 822, which was published in 1982 to define the format of Internet mail messages, [7] and he was the first listed author of the earlier RFC 733 on which it was based in 1977. [8]
[79] [80] This practice of publishing April Fool's Day RFCs is specifically acknowledged in the instructions memo for RFC authors, with a tongue-in-cheek note saying: "Note that in past years the RFC Editor has sometimes published serious documents with April 1 dates. Readers who cannot distinguish satire by reading the text may have a future ...
He also created the Request for Comments (RFC) series, [92] authoring the very first RFC and many more. [93] He was instrumental in creating the ARPA Network Working Group, the forerunner of the modern Internet Engineering Task Force. In 1972, Crocker moved to the Advanced Research Projects Agency (ARPA) to become a program manager.
#Before starting the process, make sure that all relevant suggestions have been tried. Insert an {} template tag at the top of the new talk page section, directly below the section header. Don't add two {} tags in the same edit. If you want to start two RfCs on the same page, then read § Multiple simultaneous RfCs on one page first.
If an RFC is part of a proposal that is on the Standards Track, then at the first stage, the standard is proposed and subsequently organizations decide whether to implement this Proposed Standard. After the criteria in RFC 6410 is met (two separate implementations, widespread use, no errata etc.), [12] the RFC can advance to Internet Standard.
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]