Xref: utzoo news.admin:3751 news.software.b:1692
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!think!ames!vsi1!lmb
From: lmb@vsi1.UUCP (Larry Blair)
Newsgroups: news.admin,news.software.b
Subject: Re: More article munging - who's doing this?
Message-ID: <1123@vsi1.UUCP>
Date: 20 Oct 88 16:26:20 GMT
References: <25047@tut.cis.ohio-state.edu> <1118@vsi1.UUCP> <2584@sultra.UUCP>
Reply-To: lmb@vsi1.UUCP (Larry Blair)
Organization: VICOM Systems Inc., San Jose, CA
Lines: 19

In article <2584@sultra.UUCP> dtynan@sultra.UUCP (Der Tynan) writes:
>In article <1118@vsi1.UUCP>, lmb@vsi1.UUCP (Larry Blair) writes:
>> 
>> Maybe there should be a "Crc:" field in the header.  Old news versions
>> would ignore it, but the new versions could throw away the article and
>> generate a "sendme" for the Message-ID.
>This won't work.  If the CRC is corrupt, then NOTHING in the article is OK,
>including the Message-ID.

This is not a problem because if the Message-ID is corrupted, the sendme will
be just be requesting a nonexistent article.  Not a problem.

There is a problem with sending a sendme, though.  You can only send it to
a feed that is also running the crc check, otherwise a loop will result.
A possible way to tell might be to use a different to.site group for these,
such as to.site.crc.  Only sites with crc checking create the group.

-- 
Larry Blair   ames!vsi1!lmb   lmb%vsi1.uucp@ames.arc.nasa.gov