RFC Complete Reference

RFC (Request For Comments)  Complete Reference is an FREE Encylopedia of RFC pages that you can search your needed RFCs in there !!

In computer network engineering, a Request for Comments (RFC) is a memorandum published by the Internet Engineering Task Force (IETF) describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems.

Through the Internet Society, engineers and computer scientists may publish discourse in the form of an RFC, either for peer review or simply to convey new concepts, information, or (occasionally) engineering humor. The IETF adopts some of the proposals published as RFCs as Internet standards.

RFC production and evolution

The RFC Editor assigns each RFC a unique serial number. Once assigned a number and published, an RFC is never rescinded or modified; if the document requires amendments, the authors publish a revised document. Therefore, some RFCs supersede others; the superseded RFCs are said to be deprecated, obsolete, or even obsoleted (sic). Together, the serialized RFCs compose a continuous historical record of the evolution of Internet standards and practices.

Note that the term RFC is not unique to this series. Several other organizations have published documents using the term RFC. However, the IETF RFCs are by far the best-known RFC series on the Internet.

The RFC production process differs from the standardization process of formal standards organizations such as ISO. Internet technology experts may submit an Internet Draft without support from an external institution. Standards-track RFCs are published with approval from the IETF, and are usually produced by experts participating in working groups, which first publish an Internet Draft. This approach facilitates initial rounds of peer review before documents mature into RFCs.

The RFC tradition of pragmatic, experience-driven, after-the-fact standards authorship accomplished by individuals or small working groups has important advantages over the more formal, committee-driven process typical of ISO and national standards bodies.

Emblematic of some of these advantages is the existence of a flourishing tradition of joke RFCs. Typically at least one is published each year, usually on April Fools’ Day.

Most RFCs use a common set of terms such as “MUST” and “NOT RECOMMENDED” (as defined by RFC 2119), Augmented Backus–Naur Form (ABNF) (as defined by RFC 5234) as a metalanguage, and simple text-based formatting, in order to keep the RFCs consistent and easy to understand.[1]

For more details about RFCs and the RFC process, see RFC 2026, “The Internet Standards Process, Revision 3″

Snapshots : 1 2 3 4

Download From  :  Rapidshare OR    Megaupload

File Type : CHM

File Size : 60 Mb

Author : Mahdi Talebi

Author Weblog : WWW.MTIT.Blogfa.com

Author Mail :  mahdi.afshin@gmail.com