From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc388.txt | 283 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 283 insertions(+) create mode 100644 doc/rfc/rfc388.txt (limited to 'doc/rfc/rfc388.txt') diff --git a/doc/rfc/rfc388.txt b/doc/rfc/rfc388.txt new file mode 100644 index 0000000..e86ad41 --- /dev/null +++ b/doc/rfc/rfc388.txt @@ -0,0 +1,283 @@ + + + + + + +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: + + + + 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, its count is + | | | assumed to be 0. + +-------+---------------+ + | | | + +-------+---------------+ + | | | + +-------+---------------+ + | . | | + . + . + |type | Count | + +-------+---------------+ + + + + + + + + + + + + + + +Cerf [Page 3] + +RFC 388 NCP Statistics August 1972 + + +Thus, the data you send will look roughly like this. + + +--------------------------------+ + word 0 | DAY/TIME | + +--------------------------------+ + word 1 | CONTROL WORD | + +--------------------------------+ + | DATA FOR | + | DESTINATION | + | 1 | + +--------------------------------+ + | DATA FOR | + | DESTINATION | + | 2 | + +--------------------------------+ + . + . + . + +--------------------------------+ + | DATA FOR | + | DESTINATION | + | N | + +--------------------------------+ + | CONTROL MESSAGE | + . DISTRIBUTION | + . | + . | + | | + word n +--------------------------------+ + + On completion of transmission of the last message, and after you + receive the RFNM for this last message, close the connection. + + In the original specification, we said that the data gathering + program would ICP to some well-known socket. We believe this to be + an unnecessary complication and instead, we will merely open a + connection on your 241 (decimal), expecting you to send data as soon + as our Allocate command is received by your NCP. Please let me know + if this cannot be done (i.e. you need the ICP). + + If you connect to UCLA-NMC socket 241, we will send you our own 24 + hour data. Anyone interested in capturing these statistics is + welcome to do so. + + + + + + + + +Cerf [Page 4] + +RFC 388 NCP Statistics August 1972 + + + Please note that these summarized statistics are for standard local + 24 hour period (e.g. local midnight to local midnight). They are not + for a sliding 24 hour period ending with the time at which statistics + were requested. Also, the data is to be collected only for open + connections on links 0, 2-71. + + The following are participating (others) are heartily invited): + UCLA-NMC, DMCG, LL-67. + + + + [This RFC was put into machine readable form for entry] + [into the online RFC archives by Helene Morin, Via Genie, 12/99] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +Cerf [Page 5] + -- cgit v1.2.3