The RFC Editor -- “How to Write an RFC” A Tutorial.
A Request for Comments (RFC) is a numbered document, which includes appraisals, descriptions and definitions of online protocols, concepts, methods and programmes. RFCs are administered by the IETF (Internet Engineering Task Force). A large part of the standards used online are published in RFCs.
RFC Editing Process. The RFC Editor maintains a list of documents in the editorial process. Since documents are processed in roughly FIFO order, this list is called the publication queue. Each document in the queue is assigned to a state that tracks its progress. The state diagram shows the overall publication process.
Overlapping concurrent read and write operations to the same data may cause the read to return a mixture of before-write and after-write data. Overlapping write operations can be worse, as the result could be a mixture of data from the two write operations; data corruption can occur if the underlying storage is striped and the operations complete in different orders on different stripes.
Newcomers to PHP core development should read The Mysterious PHP RFC Process and How You Can Change the Web before starting the RFC process. If you don't have the skills to fully implement your RFC and no-one volunteers to code it, there is little chance your RFC will be successful. To learn about PHP core development see References about Maintaining and Extending PHP.
RFC author — one or more community members who write an RFC and are committed to championing it through the process. RFC sponsor — a maintainer who sponsors the RFC and will shepherd it through the RFC review process. review committee — a group of maintainers who have the responsibility of recommending the adoption of the RFC.
Requirements Analysis Document. Purpose. The results of the requirements elicitation and the analysis activities are documented in the Requirements Analysis Document (RAD). This document completely describes the system in terms of functional and nonfunctional requirements and serves as a contractual basis between the customer and the developer.
The Status field gives the document's current status (see RFC 2026 and RFC 6410). The Stream field gives the document's stream (see RFC 4844), followed by Area and WG when relevant. The DOI field gives the Digital Object Identifier. See the RFC Editor Web page for more information. RFC Index.