Lawrence Rosen wrote:
Todd Glassey wrote:RFC's ARE NOT standards - they are Requests for Comments<snip> Call them what you will. They are still joint works of the IETF Trust written and published collectively under the process described by Steve Crocker. Nothing is an RFC until the IETF says it is. The rest of your email is irrelevant to my point..
Larry - Irrelevant? no - just tangential.As to the issue of the RFC publication rights - the fact that RFC2026 gave away the RFC control process means that the IETF no longer owns control of those or the process nor does the Trust. This ISN'T rocket science - its simple contract analysis.
The IETF's publishing its own process documents and releasing/re-licensing to the public under an Any and All uses constraint gave way their control so now all anyone has to do is publish a Document in any derivative format of the template they want and to call it an RFC. In fact counsel - the matter is that the IETF gave all of its processes away years ago so anyone can publish an IETF standard.
/Larry------------------------------------------------------------------------No virus found in this incoming message.Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date: 04/15/09 19:52:00