License for RFCs

[Maniues]

It looks like RFCs are not licensed under any license. I propose to consult this case with RFCs authors and add a standard license such as Ruby/MIT or CC-BY license.

[flavorjones]

@Maniues Can you explain a bit more about the problem you're hoping to solve by introducing licenses? Is there a specific example of code or prose in an existing RFC that you want to share or use or modify or distribute?

[Maniues]

Licenses are important in Open Source projects. Many of them whose use RFCs (or similar system) apply license to them to be available for all and be distributed with specification of language (e.g., PEP for Python are in Public Domain) or documentation.

Another reasons:

• RFCs build the history of technology (distributing them -> license required)
• RFCs can be used in another programming languages (with modification of verbatim text -> license required)
• With license, RFCs can be used legally in another issues, discussions, in implementation code (citations)
• With license, RFCs can be used legally in another RFCs

[flavorjones]

Is there a specific example of code or prose in an existing RFC that you want to share or use or modify or distribute that you cannot or will not because of license ambiguity? If so, we can use it as an opportunity to discuss a concrete solution to unblock you.