Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!sri-unix!malis@BBNCCS.ARPA
From: malis@BBNCCS.ARPA
Newsgroups: net.unix-wizards
Subject: Re: 4.2 RFNM count problem
Message-ID: <11809@sri-arpa.UUCP>
Date: Sat, 27-Oct-84 15:49:50 EST
Article-I.D.: sri-arpa.11809
Posted: Sat Oct 27 15:49:50 1984
Date-Received: Mon, 29-Oct-84 03:20:09 EST
Lines: 24

From:  Andrew Malis <malis@BBNCCS.ARPA>

Art and Ron,

The IMP always resets its RFNM counters under any of the
following circumstances:

1. The IMP was restarted by the NOC.

2. The host flapped or dropped its ready line to the IMP.

3. The host went tardy to the IMP, and then recovered.

All of these conditions cause the IMP to send NOPs and an
Interface Reset to the host, which the host can use as a signal
that RFNM counters have been reset.  So, the code in Ron's
message should do the trick, given that "hostreset()" does the
right thing.

Section 3.2 of BBN Report 1822 accurately discusses the second
and third cases that I list above, but does neglect to mention
that the RFNM counters are reset.

Andy