Bob Hinden replied to Mykyta:
If you think RFC20206 is wrong, then propose changes to it and see if
people agree with the changes. Until it is changed, IMHO you should
not propose actions based on what you as an individual think is
incorrect. There needs to be a community consensus that RFC2026 is
wrong before any action should be taken.
RFC 2026 says: "A specification that has been superseded by a more
recent specification or is for any other reason considered to be
obsolete is assigned to the 'Historic' level."
My concern (which may not be quite the same as Mykyta's) is how
aggressive some people might be in declaring a specification like FTP to
be superseded or obsolete. "Inappropriate for high-security uses" does
not by any means imply "inappropriate for all uses."
--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf