An RFC, or "Request for Comments" is a type of publication from the technical communities. These documents are a series of numbered memos proposing new standards, protocols, procedures, and processes. Originally, RFCs were literally "requests for comments" and were used to solicit input. Over time, the term has been retained, but many RFCs now represent established standards.

While some RFCs are purely informational, others represent consensus on best practices or standards. When an RFC describes a standard, it goes through review and approval process before being published. This ensures that the standard is technically sound and meets the companies' needs.

Purpose of RFC

• Standards Track: Specifies protocol standards and best current practices.
• Informational: Describes a topic without any standardization intent.
• Experimental: Details an experiment. It doesn't necessarily mean that it will become a standard in the future.
• Historic: Marks a previous standard that has been made obsolete or that was never standardized.

RFC structure

• Introduction: overview of the topic, setting context, and providing a brief on the subject matter.
• Motivation: reasons prompting the proposal, underlying issues with current systems, and the need for change.
• Features: specific attributes, functionalities, or characteristics of the proposed solution or product.
• Expected benefits: positive outcomes, advantages, or value-added results from implementing the proposal.
• Implementation plan: step-by-step approach, timeline, and phases for rolling out the proposal or solution.
• Concerns & risks: potential challenges, pitfalls, or negative outcomes that might arise from the proposal.
• Feedback requested: request for opinions, suggestions, and thoughts from stakeholders to refine the proposal.