article numbers (was Re: ietf-nntp Backfill)

Chris Newman <Chris.Newman@innosoft.com> Tue, 17 December 1996 19:35 UTC

Received: from cnri by ietf.org id aa15106; 17 Dec 96 14:35 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa20071; 17 Dec 96 14:35 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id NAA04881 for ietf-nntp-outgoing; Tue, 17 Dec 1996 13:32:48 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id NAA04875 for <ietf-nntp@ACADEM2.ACADEM.COM>; Tue, 17 Dec 1996 13:32:46 -0600 (CST)
Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by academ.com (8.8.3/8.7.1) with ESMTP id NAA19464 for <ietf-nntp@academ.com>; Tue, 17 Dec 1996 13:32:44 -0600 (CST)
Received: from eleanor.innosoft.com ("port 49386"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-8 #8694) id <01ID45KDWFSMA8C9QW@INNOSOFT.COM> for ietf-nntp@academ.com; Tue, 17 Dec 1996 11:31:47 -0800 (PST)
Date: Tue, 17 Dec 1996 11:32:34 -0800 (PST)
From: Chris Newman <Chris.Newman@innosoft.com>
Subject: article numbers (was Re: ietf-nntp Backfill)
In-reply-to: <9612131924.AA04439@sulphur.osf.org>
To: ietf-nntp@academ.com
Message-id: <Pine.SOL.3.95.961217112244.13167F-100000@eleanor.innosoft.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Fri, 13 Dec 1996, Rich Salz wrote:
> Jon Ribbens wrote a very nice note.  Article numbers should be considered
> unique resources, never to be re-used unless there is a "change in epoch"
> which requires out-of-band coordination between client and server.

Oddly enough, IMAP4 had to deal with this same problem to support
disconnected operation.  The difference is that with all the legacy
mailstores out there that do stupid things, IMAP4 has the "change in
epoch" message in-band.

I recommend making the "strictly ascending in delivery order" rule *very*
explicit, as the IMAP community had some problems with interpretations of
RFC 1730, so the wording is tighter in RFC 2060.

I also recommend considering if you want to place an explicit 32-bit limit
on article numbers.  In the case of IMAP4, there were people planning on
using 64-bit or longer article numbers (IMAP4 UIDs) until the rules were
made clear.  I suspect clients may break if the article numbers get over
32 bits.

I consider it desirable to have IMAP UIDs and NNTP article numbers 
identical, since they serve the same purpose.