Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc388.txt.pdf Дата изменения: Wed Mar 27 23:46:31 2002 Дата индексирования: Tue Oct 2 16:25:07 2012 Кодировка:

Network Working Group Request for Comments: 388 Obsoletes: 323 NIC: 11360 Network Measurement Note #8 NCP Statistics

V. Cerf UCLA-NMC 23 August 1972

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. b. c. d. e. Total bits sent to HOST Total bits received from HOST Total messages sent to HOST Total messages received from HOST and optionally 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 message HOST). (ALLOC optional measurement would be to gather the distribution of types over link 0 over all HOSTS (i.e. not broken down by This will reveal the relative utilization of control messages 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 # | |-+---------------------+ | | messages received | | +---------------------+ || Bytes received | N of | +---------------------+ these || message sent | entries | +---------------------+ || Bytes sent | | +---------------------+ \| Average delay | +---------------------+

always present if FORMAT bit M set if FORMAT bit B set if FORMAT bit M set if FORMAT bit B set if FORMAT bit R set This is average RFNM delay in milliseconds

8 24 +-------+---------------+ | type | Count | +-------+---------------+ | | | +-------+---------------+ | | | +-------+---------------+ | | | +-------+---------------+ | | | +-------+---------------+ | | | +-------+---------------+ |. | | . . |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.

Cerf

[Page 3]


RFC 388

NCP Statistics

August 1972

Thus, the data you send will look roughly like this. +--------------------------------+ | DAY/TIME | +--------------------------------+ | CONTROL WORD | +--------------------------------+ | DATA FOR | | DESTINATION | | 1 | +--------------------------------+ | DATA FOR | | DESTINATION | | 2 | +--------------------------------+ . . . +--------------------------------+ | DATA FOR | | DESTINATION | | N | +--------------------------------+ | CONTROL MESSAGE | . DISTRIBUTION | . | . | | | +--------------------------------+

word 0 word 1

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 program would ICP to some well-known socket. We an unnecessary complication and instead, we will connection on your 241 (decimal), expecting you as our Allocate command is received by your NCP. if this cannot be done (i.e. you need the ICP). data gathering believe this to be merely open a to send data as soon Please let me know

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]