> > At least one implementation is required for Proposed and that
> > implementation does not need to implement all features..
> No, this is simply wrong. See RFC2026.
>
> Usually, neither implementation nor operational experience is
> required for the designation of a specification as a Proposed
> Standard. However, such experience is highly desirable, and will
> usually represent a strong argument in favor of a Proposed Standard
> designation.
>
> The IESG may require implementation and/or operational experience
> prior to granting Proposed Standard status to a specification that
> materially affects the core Internet protocols or that specifies
> behavior that may have significant operational impact on the
> Internet.
>
While you are technically correct, the reality is that the IESG is
not going to make FTP AUTH SSL or FTP AUTH TLS a Proposed Standard
without implementation experience.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
