[ietf-nntp] AUTHINFO draft 01
Clive D.W. Feather
clive at demon.net
Mon Jul 5 02:45:22 PDT 2004
>>> 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.
--
Clive D.W. Feather | Work: <clive at demon.net> | Tel: +44 20 8495 6138
Internet Expert | Home: <clive at davros.org> | Fax: +44 870 051 9937
Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc | |
More information about the ietf-nntp
mailing list