RE: ietf-nntp Feedback on the 9/3 nntpext.

"Larry Osterman (Exchange)" <larryo@exchange.microsoft.com> Thu, 04 September 1997 20:04 UTC

Received: from cnri by ietf.org id aa16455; 4 Sep 97 16:04 EDT
Received: from announcer.academ.com (majordomo@ANNOUNCER.ACADEM.COM [198.137.249.60]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid QAA03480 for <ietf-archive@cnri.reston.va.us>; Thu, 4 Sep 1997 16:06:00 -0400 (EDT)
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.8.5) id PAA03454; Thu, 4 Sep 1997 15:01:22 -0500 (CDT)
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.8.5) with ESMTP id PAA03449 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Thu, 4 Sep 1997 15:01:21 -0500 (CDT)
Received: from doggate.exchange.microsoft.com (doggate.microsoft.com [131.107.2.63]) by academ.com (8.8.5/8.8.5) with SMTP id PAA03521 for <ietf-nntp@academ.com>; Thu, 4 Sep 1997 15:01:17 -0500 (CDT)
Received: by DOGGATE with Internet Mail Service (5.5.1664.3) id <S2PVATAC>; Thu, 4 Sep 1997 13:01:22 -0700
Message-ID: <2FBF98FC7852CF11912A0000000000010581D2EB@DINO>
From: "Larry Osterman (Exchange)" <larryo@exchange.microsoft.com>
To: ietf-nntp@academ.com, 'Brian Hernacki' <bhern@netscape.com>
Subject: RE: ietf-nntp Feedback on the 9/3 nntpext.
Date: Thu, 04 Sep 1997 13:01:18 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1664.3)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-nntp@academ.com
Precedence: bulk


	----------
	From:  Brian Hernacki [SMTP:bhern@netscape.com]
	Sent:  Thursday, September 04, 1997 10:13 AM
	To:  ietf-nntp@academ.com
	Subject:  ietf-nntp Feedback on the 9/3 nntpext.

	Here is some feedback on the 9/3 draft:

	4.
	        o The miminum timeout is required to be 10 minutes. I
don't
	think the RFC should specify a required minimum. 
	*******
	I disagree - the RFC SHOULD specify a required minimum to allow
clients to know how often they should poll the server to keep their
sessions alive.  This is consistant with the what is done for POP3 and
IMAP4.

	In particular, it's totally acceptable for a server to NOT
implement timeouts, however for a server that DOES implement timeouts,
clients need to know a minimum value below which they won't get dinged.

	******




	10.1
	        o This section specifies that the server should use the
"first
	unused number" for arriving articles. We may want to clairfy
this to say 
	"next sequential unused number".

	****
	If we change this wording, I'm concerned that clients may expect
that article numbers are monotonicly increasing, instead of strictly
increasing.  This becomes relevant if a message arrives, and is then
canceled, a client may be confused when it sees a hole in the article
id's.