Mark Crispin | 20 Dec 1998 11:05

re: Revised TLS + IMAP/POP/ACAP draft-06

On Sun, 20 Dec 1998 00:31:35 -0800 (PST), Chris Newman wrote:
> Mark insisted I close all gaps in the spec allowing insecure unencrypted
> plaintext password mechanisms.

No, Mark insisted that you follow the rules established by IESG.  No more, no
less.

>  And I have done so.  Now Mark seems to be
> asking me to leave an exception for one server's non-standard behavior.

It is impossible for a standard to define the behavior of an additional
facility which is non-standard.  It is absolutely reprehensible to do this ex
post facto, but that is exactly what Chris Newman is attempting to do.

> The answer is no, I will not weaken the rules to leave an opening for an
> undocumented channel leaking unencrypted passwords.

Chris is presuming to do something that he does not have the power to do; to
decide that a server can not implement a standards-track facility if it also
has an different, independent, non-standard facility.

> No, it places a restriction on servers implementing STARTTLS which makes
> them more secure and makes them better follow the IESG/IAB security
> guidelines.

There is no IESG directive stating that Internet protocols govern non-standard
and undocumented extensions, and especially that state that an implementation
may not implement a standard command if it has a particular non-standard and
undocumented extension.

(Continue reading)


Gmane