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).
Therefore, some RFCs supersede others; the superseded RFCs are said to be deprecated, obsolete, or obsoleted by the superseding RFC. Together, the serialized RFCs compose a continuous historical record of the evolution of Internet standards and practices. The RFC process is documented in RFC 2026 (The Internet Standards Process, Revision 3). [23]
iMails can carry international typesets and have small multi-media content attachments, a process standardized in RFC 2045 through 2049. Collectively, these RFCs have come to be called Multipurpose Internet Mail Extensions (MIME).
RFC 1437 – The Extension of MIME Content-Types to a new Medium (April Fools' Day RFC) RFC 1524 – A User Agent Configuration Mechanism for Multimedia Mail Format Information; RFC 2045 – MIME Part One: Format of Internet Message Bodies; RFC 2046 – MIME Part Two: Media Types; RFC 2049 – MIME Part Five: Conformance Criteria and Examples
[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 ...
And Legobot will then advertise the RfC by copying the markup of the initial statement [2] to a subpage of Wikipedia:Requests for comment (this page), posting the RfC in the corresponding lists of active RfCs. Whilst Legobot normally runs once an hour, it may take it up to a day to list an RfC, so be patient.
It is specified in a series of requests for comments: RFC 2045, RFC 2046, RFC 2047, RFC 4288, RFC 4289 and RFC 2049. The integration with SMTP email is specified in RFC 1521 and RFC 1522 . Although the MIME formalism was designed mainly for SMTP, its content types are also important in other communication protocols .
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.