Request for Comments
“RFC” stands for Request for Comments, and this name (used since 1969, before the IETF existed) expresses something important: the Internet is a constantly changing technical system, and any document that we write today may need to be updated tomorrow. …
How do I submit an IETF RFC?
To post an Internet-Draft, use the Internet-Draft Submission Tool. If you are unable to use the tool, then send your draft to [email protected] For an independent submission, the author should send an email message to the Independent Submissions Editor: [email protected]
What is IETF RFC BCP?
BCP was introduced in RFC-1818. Each RFC number refers to a specific version of a document Standard Track, but the BCP number refers to the most recent revision of the document. Thus, citations often reference both the BCP number and the RFC number. Example citations for BCPs are: BCP 38, RFC 2827.
How many IETF RFCs are there?
8,500 RFCs
Today there are over 8,500 RFCs whose publication is managed through a formal process by the RFC Editor team.
Can anyone write an RFC?
Writing an RFC should be entirely voluntary. There is always the option of going straight to a pull request.
How do I get an RFC published?
Anyone can write an Internet-Draft and independently submit it to the RFC Editor for possible publication as an RFC (Informational or Experimental category only). It will be published after review, and perhaps revision, for technical competence, relevance, and adequate writing.
What is BCP 38?
BCP38 is RFC2827: Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing. So this site is documentation that explains these attacks, and education that tells network operators how to configure their networks to prevent them.
What RFC 2026?
Abstract of RFC 2026 This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process.
What does RFC 349 and RFC 1700 have in common?
The similarities between RFC 349 and RFC 1700 are both offer application port, protocol, socket, and link.
Does the Diameter Credit-Control Application comply with RFC 4006?
The Diameter Credit- Control application as defined in this document obsoletes RFC 4006, and it must be supported by all new Diameter Credit-Control application implementations. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).
What is RFC 4023 encapsulating MPLS in IP or GRE?
RFC 4023 Encapsulating MPLS in IP or GRE March 2005 More precisely, an implementation of an MPLS-in-GRE decapsulator MUST be able to process packets correctly without these optional fields. It MAY be able to process packets correctly with these optional fields.
Does the GRE header contain the RFC 1701 header fields?
As a result, the GRE header will never contain the Key, Sequence Number or Routing fields specified in RFC 1701 . There are, however, existing implementations of RFC 1701. The following sections describe correct interoperation with such implementations. 5.1.
What is the GRE version number for PPTP?
GRE Version Numbers This document specifies GRE version number 0. GRE version number 1 is used by PPTP [ RFC2637 ]. Additional GRE version numbers are assigned by IETF Consensus as defined in RFC 2434 [ RFC2434 ]. 7.2. Protocol Types GRE uses an ETHER Type for the Protocol Type.
