Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!deimos.cis.ksu.edu!ksuvax1.cis.ksu.edu!tar
From: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Newsgroups: news.software.b
Subject: Re: Supersedes problems with rapid-fire articles
Message-ID: <3246@deimos.cis.ksu.edu>
Date: 30 Aug 89 07:06:46 GMT
References: <5200@looking.on.ca> <536@logicon.arpa>
Sender: news@deimos.cis.ksu.edu
Reply-To: tar@ksuvax1.cis.ksu.edu (Tim Ramsey)
Organization: Kansas State University, Dept of Computing & Information Sciences
Lines: 35

In article <536@logicon.arpa> Makey@LOGICON.ARPA (Jeff Makey) writes:

[ ... ]

>Few cancel messages, or few "real" articles?  The real articles might
>not make it very far, but the cancel messages would be fully
>propagated unless you used something like the Supersedes header to
>cancel *them*.

This shouldn't happen.  The cancel messages shouldn't make it past
the site *beyond* the last site the article made it to.

Wow, that last paragraph was confusing.  Let me quote RFC 1036:

3.1.  Cancel

                     cancel <Message-ID>


    If a message with the given Message-ID is present on the local
    system, the message is cancelled.  This mechanism allows a user to
    cancel a message after the message has been distributed over the
    network.

    If the system is unable to cancel the message as requested, it
    should not forward the cancellation request to its neighbor systems.

Just some unsolicited nit-picking,

Tim
--
 - VAX it to me at -              Dept. of Computing and Information Sciences
BITNET:   tar@KSUVAX1                       Kansas State University
Internet: tar@ksuvax1.cis.ksu.edu             Manhattan, KS 66506
UUCP:  ...!{rutgers,texbell}!ksuvax1!tar        (913) 532-6350