ietf-nntp Section 11.5 - NEWNEWS
Russ Allbery
rra at stanford.edu
Mon Jul 24 17:33:28 PDT 2000
David Riley <David.Riley at software.com> writes:
> On Mon, Jul 24, 2000 at 04:06:43PM -0500, Stan O. Barber wrote:
>> [Though, we did leave out SLAVE in the new document, but that was based
>> on the fact that there was no implementation of SLAVE that seemed to
>> clarify how it might be used.]
> Also, what happened with CHECK/TAKETHIS? Again, both are the norm for
> transit of all articles between servers. I think that both of these
> commands should be documented.
They're part of a separate draft.
> I remember reading AUTHINFO wasn't included since the IETF does not
> approve of any protocols with cleartext passwords? Is this the case?
> Again, AUTHINFO USER and AUTHINFO PASS are the norm and I think they
> should be documented in the draft.
This is a very long argument that you should probably read in the
archives; there are IETF review reasons why, if we include USER and PASS,
we *have* to also include some comprehensive solution like SASL, there
aren't any existing deployed implementations of the latter that I'm aware
of (although I know people are working on them), and there's a whole
muddle with response codes that really needs to be hashed out.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the ietf-nntp
mailing list