ietf-nntp AUTHINFO SASL protocol choices

[Charles Lindsey]

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

>> Since the extension mechanism in our draft makes provision for extensions
>> to have parameters, we may as well make use of it.

>Right.  So if we do the above, we can (and probably should) have a LENGTH
>extension with a parameter showing the server's maximum length.  Then
>clients can, if they like, simply use the server's maximum.  On the other
>hand, if a client wants the smallest maximum which allows a particular set
>of extensions to be used, that can be hardcoded by reading the
>specifications for those extensions.

Almost. What I had in mind was that if the SASL extension needed a line
length of 1024, then it MUST also implement (and report in LIST EXTENSIONS
accordingly) a LENGTH of at least that amount.

I.e., in the document, you

    A. Define a LENGTH extension with parameter 'n' (default and minimum
allowed 512) which any implementation can choose to provide as it thinks
fit.

    B. "Any extension which requires the use of a command line length in
excess of 512 MUST also support the LENGTH extension, with parameter
greater than or equal to the length it requires."

-- 
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