ietf-nntp AUTHINFO SASL protocol choices

[Charles Lindsey]

In <Pine.LNX.4.33.0203141432350.2129-100000 at marduk.litech.org> "Jeffrey M. Vinocur" <jeff at litech.org> writes:


>On Thu, 14 Mar 2002, Charles Lindsey wrote:

>> OK, just to confirm my understanding, the LIST EXTENSIONS command might
>> return:
>>
>> 	202 Extensions supported:
>> 	OVER
>> 	HDR
>> 	COMMANDLEN 998
>> 	SASL 400
>> 	.
>>
>> where COMMANDLEN defaults to (and MUST be >= than) 512
>> and SASL * <base 64 factor> + <margin> MUST be <= COMMANDLEN

>Hmm.  This is not what I had in mind, although it might work.  The way
>ESMTP does it (to my understanding) the line lengths are documented in
>each extension's specification, and thus the code can continue to have the
>limit set at compile time, based on what exxtensions it supports.

Well you could certainly specify it like that in the NNTP extension
mechanism defined in our draft.

But I think the effect is the same. You would compile the NNTP server with
limits for both COMMANDLEN and SASL set at compile time (but satisfying
that constraint), causing the LIST EXTENSION command to respond as I
indicated. Presumably you would choose the SASL limit in accordance with
whatever SASL algorithms you had decided to support (or have I totally
misunderstood SASL?).

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl at clw.cs.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5