Composing an RFC is a very formalised process. How to write an RFC is described in RFC 2223. RFC 2119 sets out what significance is attached to certain terms, such as “must” or “must not”. This aims to avoid any misinterpretations. How to put character strings together is also clearly defined. If an RFC ends up being published, it can no longer be amended. It can only be replaced by an updated RFC.
Every Request for Comments is attributed a certain status. An RFC is “informational” if it contains information or an idea for the online community. An “experimental” RFC is for the purposes of experimentation, or represents the initial stages of an eventual standard. Other possible statuses include “draft” standard (for evaluation), “proposed” standard (a proposal for a standard), “standard” (an official standard) or “historic” (no longer used). RFCs with the status “required” must be complied with immediately, and “recommended” or “suggested” RFCs are simply recommendations. The use of “elective” RFCs is at the discretion of the individual user.