RFC-0001. Request for Comments§
Talking does not scale. Words are extremely imparmanent. The core values of an RFC are concisely expressed in RFC-3:
The content of a note may be any thought, suggestion, etc. related to the software or other aspect of the network. Notes are encouraged to be timely rather than polished. Philosophical positions without examples or other specifics, specific suggestions or implementation techniques without introductory or background explication, and explicit questions without any attempted answers are all acceptable. The minimum length for a note is one sentence.
These standards (or lack of them) are stated explicitly for two reasons.
There is a tendency to view a written statement as ipso facto authoritative, and we hope to promote the exchange and discussion of considerably less than authoritative ideas.
There is a natural hesitancy to publish something unpolished, and we hope to ease this inhibition.
We also aim to explicitly capture policies, patterns, processes and whatever else follows. An RFC is only required when a relatively stable procedure or idea for something is being established and requires a well-defined specification.
TLDR§
In the context of <usecase> facing <concern> we decided to <option> to achieve <quality> accepting <tradeoff>.