RFCs - insufficiently free?

RFCs - insufficiently free?

So, I see a fairly simple solution to this problem, one that has been used in various other cases. The Internet Society can release their documents under something resembling the X license, and then trademark their name. Then they set out a policy whereby if you alter an Internet Society document you cannot use the trademark.

It then becomes easy to identify unmodified standards documents, as they will still have the trademark. At the same time, there is no restriction preventing you from modifying an RFC and attaching your own seal of approval (or none whatsoever).

     The license may require derived works to carry a
     different name or version number from the original
     software.