[ietf-nntp] AUTHINFO draft 01

[Ken Murchison]

Clive D.W. Feather wrote:

>>>>2.2.1: we discussed briefly a separate response code meaning "invalid
>>>>base64 string". The logical code for this is 504 (it belongs in the 50x
>>>>space and this is the next unused code). There's still time to put that
>>>>in [NNTP], incidentally.
>>>
>>>I have no objections to this.  It seems like a reasonable idea.
>>
>>Done.
> 
> 
> Jeff: the productions base64 etc. are now in [NNTP]:
> 
>      base64 = *(4base64-char) [base64-terminal]                
>      base64-char = UPPER / LOWER / DIGIT / "+" / "/"
>      base64-terminal = 2base64-char "==" / 3base64-char "="    
>    
> That doesn't stop you including them yourself, but in particular it means
> you needn't worry about LOWER.

I have a question as to why the the base64 syntax and the 504 code 
belong in [NNTP] if their only use is with AUTHINFO.  Do you anticipate 
that they will be used for other commands in the future?

-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp