Re: ietf-nntp Backfill

Stan Barber <sob@academ.com> Tue, 17 December 1996 05:15 UTC

Received: from cnri by ietf.org id aa18343; 17 Dec 96 0:15 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa01462; 17 Dec 96 0:15 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id XAA01558 for ietf-nntp-outgoing; Mon, 16 Dec 1996 23:13:28 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id XAA01553 for <ietf-nntp@ACADEM2.ACADEM.COM>; Mon, 16 Dec 1996 23:13:26 -0600 (CST)
Received: (from sob@localhost) by academ.com (8.8.3/8.7.1) id XAA07443; Mon, 16 Dec 1996 23:13:23 -0600 (CST)
Message-Id: <199612170513.XAA07443@academ.com>
From: Stan Barber <sob@academ.com>
Date: Mon, 16 Dec 1996 23:13:23 CST
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Nat Ballou <NatBa@microsoft.com>, ietf-nntp@academ.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: Re: ietf-nntp Backfill
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

I agree with Nat. I got the impression that most folks were basically surprised
by the issue of backfill. Erik himself said that it was always understood that
article numbers were monotonically increasing.

Unless there is a strong desire to support backfilling explicitly, I think
the new document should state that articles numbers are monitonically
increasing and that backfilling is not supported.  It certainly makes
server and client implementation simpler (I think).


-- 
Stan   | Academ Consulting Services        |internet: sob@academ.com
Olan   | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob
Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.