This is an old revision of the document!
Table of Contents
Questions for an organization requesting to be considered as a new Stream in to the RFC Series
1 - Why the RFC Series and not a different organization or publisher? What are you hoping to achieve by publishing RFCs as opposed to self-publishing?
2 - Do you anticipate your organization being a persistent entity for the next 5-10 years?
3 - The RFC Series has some particular points of style and format that must be consistent across the streams. Today that means ASCII only, fixed line and page lengths, and a fairly common document structure (Abstract, Introduction, Headers, Footers, etc.) Is your organization willing to accept those constraints and participate in the discussions regarding potential changes to those constraints? Do you have any format requirements of your own, such as a UTF-8 character set or inclusion of graphics or HTML-style links?
4 - How many documents do you expect to request to publish a year?
Requirements for any group or organization to be considered as a new stream
* Organization and documents must focus on improving technology or best practices for the Internet * Open process for creation of documents * Free * Accept the RFC Series format and style guide * Organization and documentation must be Community supported, not vendor driven * Documents need to be of a quality such that the RFC Editor can edit them in a reasonable fashion (If there are enough documents that would require weeks of editing, beyond what is in our current SLA with the IETF, then that's a problem)
Questions for the RSE, IAB, and whoever else needs to be involved in determining whether a new Stream should be created (TBD)
1. What type of documents are allowed? Informational? BCP? Standard? etc.
Suggested Action Items for New Stream Creation
1. Establish a list of questions to determine suitability (see above). 2. Require a new I-D from the supplicant describing their process, IPR policy, etc., for RSE and RSOC review. 3. Create a contract & SLA based on expected number of documents (example: will require funding for at least 15 documents a year, no refund if not that many, will require additional funds if more). Overall, the SoW model must be similar to that of our other streams.
Suggestion Action Items for closing a stream
1. Either side may conclude the stream if funding or quality of documents run dry
Other actions to consider
- A new stream will need to be prepared to define their processes in an RFC. Current stream documents:
- RFC5745 “Procedures for Rights Handling in the RFC IAB Stream”
- RFC5744 “Procedures for Rights Handling in the RFC Independent Submission Stream”
- RFC5743 “Definition of an Internet Research Task Force (IRTF) Document Stream”
Responses to date
