ietf-nntp DEBUG command (9xx)
Stan O. Barber
sob at verio.net
Fri Jul 28 11:31:23 PDT 2000
Chin Chee-Kai wrote:
> On Fri, 28 Jul 2000, Stan O. Barber wrote:
> >>[The DEBUG command was intended to clarify RFC977, which is part of the charter.
> >>We can dispose of this command, but if we do, then we are left with the lack of
> >>clarity on what
> >>happens when a client sees an X9X response during a session.]
> Hmmm, the DEBUG command seems to introduce more issues than
> clarifications as I've described earlier at length. There
> are other alternatives and discussions on clarifying the
> x9x and x8x messages spaces without using DEBUG command.
Based on this and other comment from you, then I would take it that you are in
the group that says that X9X should never be presented by a server under normal
The question is still open (unless I missed it) on what a client should do
should a server present these results and that server is understood to be in
"normal circumstances" mode by the client. Should the client ignore these
responses or treat them as protocol errors? I would suggest the latter, but
again, I am open to other possibilities as long as we can get some consensus.
Stan | PGP Key ID: 55CB6421 | Opinions expressed are only mine.
Olan | Phone: +1-713-793-0222 | Email: sob at academ.com
Barber | Fax: +1-713-793-0221 | http://www.academ.com/~sob
More information about the ietf-nntp