This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
streamquery [2012/08/26 14:04] rsewikiadmin |
streamquery [2013/04/04 13:31] rsewikiadmin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | For: | ||
+ | - The RFC Editor recognizes that the needs of the technical research and engineering community and the associated documentation that describes the Internet are growing and changing. | ||
+ | - The RFC Editor recognizes that other organizations offer value and may have different IPR such that working through a separate stream will allow those organizations to more effectively contribute to the workings on the Internet in a more efficient manner. | ||
+ | - As the Internet evolves and changes, there is more information that should be discussed and disseminated to encourage secure, open practices; | ||
- | 1 - Why the RFC Series | + | Against: |
+ | | ||
- | 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. | + | ====== Questions for an organization requesting to be considered as a new Stream |
+ | - 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. | ||
+ | - 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 the RFC Production Center' | ||
+ | * 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? | + | |
+ | |||
+ | ====== Suggested Action Items for New Stream Creation ====== | ||
+ | |||
+ | - Establish a list of questions to determine suitability (see above). | ||
+ | - Require a new I-D from the supplicant describing their process, IPR policy, etc., for RSE and RSOC review. | ||
+ | - Work with relevant parties to determine the terms of service and cost associated with the stream. | ||
+ | |||
+ | ====== Suggestion Action Items for closing a stream ====== | ||
+ | 1. Either side may conclude the stream if funding or quality of documents runs dry | ||
+ | |||
+ | ====== Other actions to consider ====== | ||
+ | * A new stream will need to be prepared to define their processes in an RFC. Current stream documents: | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | ====== Responses to date ====== | ||
+ | [[refeds|REFEDs responses]] |