Re: ietf-nntp Issue: reinstatement
Jon Ribbens <jon@oaktree.co.uk> Sun, 29 December 1996 00:33 UTC
Received: from cnri by ietf.org id aa11203; 28 Dec 96 19:33 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa16295;
28 Dec 96 19:33 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.4/8.7.3) id
SAA05099 for ietf-nntp-outgoing; Sat, 28 Dec 1996 18:30:35 -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.4/8.7.3) with ESMTP id SAA05094 for
<ietf-nntp@ACADEM2.ACADEM.COM>; Sat, 28 Dec 1996 18:30:32 -0600 (CST)
Received: from black.oaktree.co.uk (root@black.oaktree.co.uk
[194.217.216.129]) by academ.com (8.8.4/8.7.1) with ESMTP id SAA02482 for
<ietf-nntp@academ.com>; Sat, 28 Dec 1996 18:30:28 -0600 (CST)
Received: (from jon@localhost)
by black.oaktree.co.uk (8.7.5/8.7.3) id AAA28589;
Sun, 29 Dec 1996 00:30:25 GMT
From: Jon Ribbens <jon@oaktree.co.uk>
Message-Id: <199612290030.AAA28589@black.oaktree.co.uk>
Subject: Re: ietf-nntp Issue: reinstatement
To: "Clive D.W. Feather" <clive@demon.net>
Date: Sun, 29 Dec 1996 00:30:24 +0000 (GMT)
Cc: ietf-nntp@academ.com
In-Reply-To: <851805333.28095.0@office.demon.net> from "Clive D.W. Feather" at
Dec 28, 96 08:35:32 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
Clive D.W. Feather wrote: > Jon Ribbens: > > There's a lot of wording taken up with this eventuality. I don't > > see the need to document it. > > If it's allowed, then we need to include enough wording to describe the > implications, even if it's rare. If it's forbidden, we should say so, so that > client authors can rely on the fact. My impression is that it just doesn't matter. If you don't mention it, then nothing bad will happen. I don't think it is necessary for news clients to notice the reinstated article - it's there if they specifically go looking for it, but it doesn't matter if the software doesn't notice it as a new article. Since the worst that can happen if the news software doesn't cope with the reinstatement is just that - the article isn't noticed - why bother mentioning it? > > Even if you do want > > this stuff in, I don't see a need for the condition that the article > > number MUST be no less than the first article number. > > Without that condition, the low water mark might decrease. Everyone was > against that. The only bad thing that might happen here is that some software might think the article numbers have been reset. I suppose it's best to keep this condition. Cheers Jon ____ \ // Jon Ribbens // 10MB virtual-hosted // www.oaktree.co.uk \// jon@oaktree.co.uk // web space for 49UKP //
- ietf-nntp Issue: reinstatement Clive D.W. Feather
- Re: ietf-nntp Issue: reinstatement Jon Ribbens
- Re: ietf-nntp Issue: reinstatement Chris Hall
- Re: ietf-nntp Issue: reinstatement USENET news manager
- Re: ietf-nntp Issue: reinstatement Chris Hall