Loading content
The Request for Comments (RFC) method formalizes how technical specifications, protocols and community standards are proposed, reviewed and published. It defines roles, editorial workflows, versioning and consensus mechanisms to ensure openness and traceability. RFCs are used as reference documents for interoperable open protocols.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A Request for Comments (RFC) is a written proposal that puts a technical or organizational decision up for public or team review and records the comments it receives.
Steve Crocker published an early Request for Comments as RFC 3 in 1969 on the ARPANET, establishing the name. The RFC Editor now maintains the series, which contains Internet standards, informational documents, and historical records.
Treat an RFC as a decision object with a lifecycle: document problem and context, goals and non-goals, options, preferred proposal, consequences, and open questions. A review phase gathers objections and improvements; then the proposal is decided, rejected, revised, or published with the decision linked.
A shared starting point keeps discussion focused on the actual decision.
Options become comparable through benefits, costs, risks, and consequences.
Status and feedback show whether an RFC is open, decided, revised, or published.
RFCs make consequential decisions reviewable and reduce tacit knowledge in teams. They work when audience, deadline, and decision authority are explicit; a document cannot replace participation or ownership.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.