[NNTP] [2505] CAPABILITIES indication of features not
currentlyavailable
Ruud H.G. van Tol
rvtol at isolution.nl
Thu Dec 2 07:06:48 PST 2004
Clive D.W. Feather wrote:
> I would like you to think about SASL methods that are unavailable
> before encryption. Consider a client that can only do SASL PLAIN (or
> some other method that requires TLS in place). At present, it has no
> way to find out whether or not it's worth going through the effort of
> doing TLS; the only way to see whether PLAIN is going to appear is to
> actually try it. Now
> we're trying to get *away* from the suck-it-and-see school of protocol
> design. So I would suggest that the SASL capability should indicate
> what will be available once a privacy layer is in place. This could
> be via specific flags:
Is it also useful to indicate what is *not* available?
I first read your '-PLAIN' as 'minus PLAIN', meaning 'PLAIN is not
supported'.
--
Grtz, Ruud
More information about the ietf-nntp
mailing list