ietf-nntp TLS and AUTHINFO interaction

[Jeffrey M. Vinocur]

On Mon, 17 Mar 2003, Russ Allbery wrote:

> Jeffrey M Vinocur <jeff at litech.org> writes:
> 
> > Except, um, one thing.  Suppose the server does want to indicate
> > encryption being required for some command, and the client has already
> > authenticated.
> 
> I think it can still send a 483 response in that case.  Anyone object?

That part at least makes sense to me.


> The client might try STARTTLS and then get an error (580 in this case, I
> think?), 

I was planning on lumping the already-authenticated state in with the
already-established-TLS state; in both cases STARTTLS would not appear in
list extensions, the client would be expected to know not to try it, and 
any attempt to try it would be met with 500.  The two cases seem very 
similar to me.

But on the other hand, returning 580 in this instance (to indicate 
permanent failure) does make sense as well.


-- 
Jeffrey M. Vinocur
jeff at litech.org