RFC 388 (rfc388) - Page 1 of 5

NCP statistics

Alternative Format: Original Text Document
Next >
Network Working Group                                            V. Cerf
Request for Comments: 388                                       UCLA-NMC
Obsoletes: 323                                            23 August 1972
NIC: 11360
Network Measurement Note #8

                             NCP Statistics

   After a lapse of 5 months since RFC #323 was issued (23 March), I am
   pleased to announce that UCLA-NMC is prepared to gather your NCP
   statistics automatically on a daily basis.  The results will be
   published monthly as Network Measurement notes and as RFC's.  We will
   periodically open a connection on your local socket @241 (decimal),
   expecting you to send the following data in the format shown:

                   RFC 323 here>

      a. Total bits sent to HOST
      b. Total bits received from HOST
      c. Total messages sent to HOST
      d. Total messages received from HOST and optionally
      e. Average Round Trip delay on send connections to HOST

   The information above should be collected only for standard open
   connections (i.e. those using standard NCP protocol) and not
   measurement links or experimental NCP links, and in particular, not
   traffic on link 0).

   Another optional measurement would be to gather the distribution of
   message types over link 0 over all HOSTS (i.e. not broken down by
   HOST). This will reveal the relative utilization of control messages
   (ALLOC should be very prevalent).

   The data collected for the last 24 hour sample period should be
   available from a process listening on local socket number 241 (10).
















Cerf
Next >