Browse Prior Art Database

NCP statistics (RFC0388)

IP.com Disclosure Number: IPCOM000004899D
Original Publication Date: 1972-Aug-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 5 page(s) / 5K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Cerf: AUTHOR

Related Documents

10.17487/RFC0388: DOI

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 57% of the total text.

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:

<duplicate pages 3-5 of 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 [Page 1]

RFC 388 NCP Statistics August 1972

16 16 +----------+------------+ word 0 | Day # | Time | +----------+------------+ | | 1 - 365 (6 on leap year) |______ | Time in minutes at which sample was started. Ranges from 0 (midnight) to 1439.

8 8 +--------+------+-------+----------+ word 1 | Source | Byte | N | Format | | Host | Size | | | +--------+------+-------+----------+ | | | |__________ _______| | | | | | number of HOST | Network Host | related entries +---+---+---+---+---+---+ number | in message | | | C | R | B | M | | +---+---+---+---+---+---+ number of bits per | | | | byte in byte statistics ____ ____| | | message | ___| | statistics | | byte control | statistics message distribution | average round-trip time

Cerf [Page 2]

RFC 388 NCP Statistics August 1972

The remaining words of the message depend on Format byte setting:

<-------32---------> / +---------------------+ | | Foreign HOST # | always present |-+---------------------+ | | messages received | if FORMAT bit M set | +---------------------+ | | Bytes received | if FORMAT bit B set N of | +---------------------+ these | | message sent | if FORMAT bit M set entries | +---------------------+ | | Bytes sent | if FORMAT bit B set | +---------------------+ \ | Average delay | if FORMAT bit R set +---------------------+ This is average RFNM delay in milliseconds 8 24 +-------+---------------+ | type | Count | if FORMAT bit C set these +-------+---------------+ are link 0 control message | | | distributions for the +-------+---------------+ sample period, cumulative | | | overall HOSTs. If a type is +-------+---------------+ not present,...

Processing...
Loading...