RFCs - insufficiently free?

RFCs - insufficiently free?

Standard should be sufficient free, so that in case of inativity or some other problems (legal, patent, close development, ...) groups can always fork standard and continue the development of such standard.

A goog license would be a TeX-like license: you can modify the language, but to call TeX you should pass some test. So in case of improvement, you can use the standard implementations, with only the obligation to name your new "standard" with an other (non confusing) name

As you see, the problem is not to modify RFC 822 / 2822, but to allow you to create/develop a OPEN 4822 using existing RFC, to extend mail capabilities, without losing backward compatibility to existing "standard: