Re: new C-S draft

[Henry Clark <[e-mail]>]

> The authentication type names specified in RFC1409 could be used here.

This doesn't seem like it's buying us anything.  I guess the basic 
question here is do we need a "standard" list of authentication types
specified in this document?  Not every server or client need support
all of the types...

> For security reasons, I'd always challenge even if the username is
> unknown. This way it is harder to find valid usernames by trial and
> error. (I guess I am also suggesting to get rid of error code 112
> then).

changed!

> It might be helpful to spell out what happens if the underlying
> reliable transport protocol closes the connection. I'd assume for the
> server this is equivalent to receiving an EXIT command and the server
> can release all data structures and TAG's that were associated with
> the session.

done...

If the data connection to the client closes for any reason while the server 
is in the PROCESS state, the server must immediately close its connection and
do any associated internal cleanup and return to the LOGIN state.

thanks,
henry