Re: ietf-nntp Comments on the draft
Ben Polk <bpolk@netscape.com> Wed, 02 October 1996 21:58 UTC
Received: from cnri by ietf.org id aa10374; 2 Oct 96 17:58 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa23072;
2 Oct 96 17:58 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
QAA25985 for ietf-nntp-outgoing; Wed, 2 Oct 1996 16:54:57 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to
owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id QAA25981 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 16:54:55 -0500
Received: from hedgehog.mcom.com (h-207-1-136-17.netscape.com [207.1.136.17])
by academ.com (8.7.6/8.7.1) with ESMTP id QAA02364;
Wed, 2 Oct 1996 16:54:51 -0500 (CDT)
Received: from bpolk.mcom.com ([207.1.137.51]) by hedgehog.mcom.com
(Netscape Mail Server v1.1) with SMTP id AAA16973;
Wed, 2 Oct 1996 14:54:16 -0700
X-Sender: bpolk@pdmail2.mcom.com
X-Mailer: Windows Eudora Pro Version 2.1.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Stan Barber <sob@academ.com>, ietf-nntp@academ.com
From: Ben Polk <bpolk@netscape.com>
Subject: Re: ietf-nntp Comments on the draft
Date: Wed, 2 Oct 1996 14:54:16 -0700
Message-ID: <19961002215416.AAA16973@bpolk.mcom.com>
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
At 10:04 AM 10/2/96 CDT, Stan Barber wrote: >I didn't include any examples. I do intend to include some, but I want to >know if they should be in a section all on their own (like RFC 977) or >mixed in with each command to show how it is used. What do people think? >Also, what about the format? Should the one used in RFC 977 be used here? I liked the format in 977. I think putting them together in the end is better because you can show collections of commands as they are actually used. >I used the tactic from RFC 977 concerning ARTICLE, STAT, HEAD, and BODY. >Should I change that so that each is discussed individually? I don't have a problem with the way it is now. >I also didn't include a section that lists all the keywords and all the >response codes together. Is that useful? It would be good to have an authoritative list of response codes. >I thought about including more information about how the "current group pointer" >and "current article pointer" work to make it easier for first time >implementors to implement NNTP. Is that useful? Or, should that be something >in another document? Is it ambiguous? I haven't heard about problems in this regard due to broken server implementations, so I'd guess adding more language here isn't needed.
- ietf-nntp Comments on the draft Stan Barber
- Re: ietf-nntp Comments on the draft Ben Polk
- Re: ietf-nntp Comments on the draft chris (c.) lewis
- Re: ietf-nntp Comments on the draft Stan Barber
- Re: ietf-nntp Comments on the draft chris (c.) lewis
- Re: ietf-nntp Comments on the draft Stan Barber