The above change (if approved etc) would make it harder to include any source code in IETF documents. Agree, yes/no?
No! it means that if you want to attach a license to source code in an RFC, you do so external to the RFC.
Oh, I see. It sounds like a good idea in theory.
However, it would make it impossible to use code licensed under many software licenses in IETF documents. I'm not sure if that was what you intended?
If the code originates in the RFC and is added to an open source package afterwards, it will be a matter of choosing a sensible OSS license. (Where my definition of "sensible" means "has no problem with adding code from another source".) Theoretically, doing it the other way round would perhaps violate an OSS license, but I feel confident it would be considered fair use and would never get anybody in trouble.
Brian
_______________________________________________ Ipr-wg mailing list Ipr-wg at ietf.org https://www1.ietf.org/mailman/listinfo/ipr-wg