Ftp-WG: status of rfc 2228
Jeffrey Altman <[email protected]> Tue, 4 Nov 2003 10:43:36 -0500
| Newsgroups | gmane.ietf.ftpext |
|---|---|
| Organization | Columbia University in the City of New York |
| Message-ID | <[email protected]> |
Yes. Because it was never adopted by the FTP-WG as a working group item and the former Security AD who was supposed to handle the Last Call work never found the time AND is no longer an AD. Jeffrey Altman Alun Jones wrote: >>-----Original Message----- >>From: ftp-wg-owner [mailto:[email protected]] On >>Behalf Of Jeffrey Altman >>Sent: Tuesday, November 04, 2003 7:39 AM >> >>[email protected] wrote: >> >> >>>i was wondering if anyone knew which ftp implementations >>> >>> >>currently support the proposed security extensions. >> >> >>> >>> >>> >>There are many implementations supporting >> >> GSSAPI-Kerberos 5 >> Kerberos 4 >> Secure Remote Password >> Transport Layer Security v1 >> >> > >That reminds me - does anyone know why draft-murray-auth-ftp-ssl-12.txt is >still a draft, and hasn't been promoted to RFC status yet? > >It seems like there's been no changes to this draft in a year, it's adopted >by several implementations, and there doesn't seem to be anything other than >IETF slowness holding it up. At least, that's my perspective from the >outside - anyone got any other ideas? > >Alun. >~~~~ > >
smime.p7s
(application/x-pkcs7-signature, 3.3 KB) - not displayed