ietf-nntp Last major open issue (48x return codes)

Charles Lindsey chl at clerew.man.ac.uk
Mon Sep 8 03:22:04 PDT 2003


In <87ekysgixj.fsf at windlord.stanford.edu> Russ Allbery <rra at stanford.edu> writes:

>For the latter question, I think reserving 48x codes to mean that a
>command is unavailable unless some authentication or privacy extension is
>invoked is the best approach.

Something like that, but are there other circumstances? Essentially it is
saying "I can't let you do that unless you jump through some hoops first"
(hopefully the accompanying text and/or the value of 'x' will tell you
which hoop).

Clearly, the obvious hoops are authentication and privacy, but could there
be others we have not thought of yet, and should the wording be broad
enought to cover them in the future?

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



More information about the ietf-nntp mailing list