API Change Proposal
Docs + Word7 pages
FreeRFC templates
3 templates
All templates
Infrastructure Change Proposal
Docs + Word8 pages
Free
Engineering RFC
Docs + Word8 pages
Free- Browse all templates
Compare RFC versions
 API Change Proposal |  Infrastructure Change Proposal |  Engineering RFC | |
|---|---|---|---|
| Format | Document | Document | Document |
| Works in | Google Docs and Word | Google Docs and Word | Google Docs and Word |
| Length | 7 pages | 8 pages | 8 pages |
| Style | Modern | Modern | Minimal |
How to choose a RFC template
Request for comments on a technical change. That is the job of the 3 templates on this page, and each one takes a different angle on it.
Read moreShow less
Compare API Change Proposal, Infrastructure Change Proposal, and Engineering RFC, all 7 to 8 pages long, then pick the closest match and replace the sample text with your own.
Questions
Which RFC template should I start with?
Start with API Change Proposal: Propose a public API change, show who it affects and how it stays compatible, and set a decision date for reviewers. If that is not the right fit, compare it with Infrastructure Change Proposal.
How many pages does a RFC need?
The templates here are 7 to 8 pages long. Cut any section you do not need; each template explains what its sections are for.
Can I make a RFC in Google Docs?
Yes. These RFC templates work in Google Docs and Microsoft Word. All 3 templates are free, with no account or email needed.