Formation of Network Measurement Group (NMG) (RFC0323)
Original Publication Date: 1972-Mar-23
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
On March 17, 1972, at MIT project MAC, the following group met to discuss plans to perform measurement experiments on the ARPANET:
Network Working Group Vint Cerf
Request for Comments: 323 UCLA-NMC
NIC: 9630 March 23, 1972
Formation of Network Measurement Group (NMG)
On March 17, 1972, at MIT project MAC, the following group met to
discuss plans to perform measurement experiments on the ARPANET:
A. Bhushan - MIT/DMCG
V. Cerf - UCLA/NMC, Chairman, NMG
S. Crocker - ARPA/IPT
J. Forgie - LL/TX-2
R. Metcalfe - MIT/HARV/DMCG
M. Padlipsky - MIT/MULTICS
J. Postel - UCLA/NMC
J. Winett - LL/67
The purpose of the meeting was to discuss existing and planned
measurements of network and HOST behavior.
1. Measurement Link #'s
It was agreed (after a ridiculously long discussion) to allocate
links 159-191 for network measurement only (see RFC #317). It was
further agreed that these links would be allocated in the following
159-174 HOST DISCARD; co-operating HOSTS receiving messages on
these links will throw them away without generating an
175-190 To be allocated as needed by V. Cerf - UCLA/NMC.
191 To be used by IMPs to send measurement traffic
obtained from IMP statistics packages.
It should be apparent that HOSTs wishing to co-operate in the support
of a HOST discard service should modify their NCP's to throw away all
messages received on links 159-174 without sending an error back to
the source HOST (no connection will be open on these links).
2. Process Discard
Although it was not mentioned at the meeting, C. Kline at UCLA has
suggested a PROCESS DISCARD also with some well known socket number.
The purpose of this discard routine would be to help us study
Process-Process behavior of the network.
It would be convenient if all co-operating HOSTs could write a
Process Discard program which would simply wait for ICP on some
standard socket number. Until a complete survey is made of well-
known socket numbers at each HOST, no socket number will be proposed
(see RFC #322).
3. NCP Statistics
At the meeting it was apparent that several sites have already
instrumented their NCP's out of curiosity. In particular, Joel
Winett, Lincoln Labs (360/67), has instrumented all connections
originated by local TELNET users. He gathers statistics per
connection such as: