This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
streamquery [2013/04/03 16:52] rsewikiadmin |
streamquery [2013/04/04 13:31] (current) rsewikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | For: | ||
- | 1 - Why the RFC Series | + | |
+ | - The RFC Editor recognizes that other organizations offer value and may have different | ||
+ | | ||
- | 2 - Do you anticipate your organization being a persistent entity for the next 5-10 years? | + | Against: |
+ | | ||
- | 3 - The RFC Series has some particular points of style and format that must be consistent across the streams. | ||
- | 4 - How many documents do you expect to request to publish a year? | + | ====== Questions for an organization requesting to be considered as a new Stream in the RFC Series ====== |
+ | |||
+ | - Why the RFC Series and not a different organization or publisher? | ||
+ | - Do you anticipate your organization being a persistent entity for the next 5-10 years? | ||
+ | - The RFC Series has some particular points of style and format that must be consistent across the streams. | ||
+ | | ||
====== Requirements for any group or organization to be considered as a new stream ====== | ====== 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 | + | * Open process for creation of documents |
- | * Free | + | * Free |
- | * Accept the RFC Series format and style guide | + | * Accept the RFC Series format and style guide |
- | * Organization and documentation must be Community supported, not vendor driven | + | * 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 | + | * 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 |
+ | * A document needs to exist that specifies the stream boilerplate material (see RFC 5741 as an example), including | ||
+ | * status of this memo | ||
+ | * document source (e.g., stream name to be applied to the doc header) | ||
====== Questions for the RSE, IAB, and whoever else needs to be involved in determining whether a new Stream should be created (TBD) ====== | ====== 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? | + | - What type of documents are allowed? |
====== Suggested Action Items for New Stream Creation ====== | ====== Suggested Action Items for New Stream Creation ====== | ||
- | 1. Establish a list of questions to determine suitability (see above). | + | - 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). | + | |
====== Suggestion Action Items for closing a stream ====== | ====== Suggestion Action Items for closing a stream ====== | ||
- | 1. Either side may conclude the stream if funding or quality of documents | + | 1. Either side may conclude the stream if funding or quality of documents |
====== Other actions to consider ====== | ====== Other actions to consider ====== | ||
* A new stream will need to be prepared to define their processes in an RFC. Current stream documents: | * A new stream will need to be prepared to define their processes in an RFC. Current stream documents: | ||
- | * RFC5745 | + | * [[http:// |
- | * RFC5744 | + | * [[http:// |
- | * RFC5743 | + | * [[http:// |
+ | * [[http:// | ||
====== Responses to date ====== | ====== Responses to date ====== | ||
[[refeds|REFEDs responses]] | [[refeds|REFEDs responses]] |