Site Certification - Lincoln Labs 360/67
A short report says Lincoln Laboratory's 360/67 network software passed its checks.
Heafner, J.F., "Site Certification - Lincoln Labs 360/67", RFC 198, DOI 10.17487/RFC0198, July 1971, <https://www.rfc-editor.org/info/rfc198>.
@misc{rfc198,
series = {Request for Comments},
number = 198,
howpublished = {RFC 198},
publisher = {RFC Editor},
doi = {10.17487/RFC0198},
url = {https://www.rfc-editor.org/info/rfc198},
author = {J.F. Heafner},
title = {{Site Certification - Lincoln Labs 360/67}},
pagetotal = 1,
year = 1971,
month = jul,
} RFC text
Network Working Group J. Heafner - Rand
Request for Comments #198 20 July 1971
NIC #7149
Categories: D.4
Updates: RFC #193
Obsoletes: None
SITE CERTIFICATION - LINCOLN LABS 360/67
We have exercised Lincoln Labs Network software as follows: NCP,
ICP, ASCII Telnet (user and server), login procedure, access to CMS, and
operator and console communication. All behave according to current
specifications.
Multiple message responses, such as listing users, were very
smooth under moderate to heavy load of the /67.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Josh Elliott 1/98 ]
ISO Plain Language
On this page
§1Testing the Lincoln Laboratory Host
RFC 198 reports that Lincoln Laboratory's network software was exercised. The report names the host as the Lincoln Labs 360/67 and states that its tested components behaved according to current specifications.
This is a short report on tests of the 360/67's network software. The report says the tested components worked as specified.
§2What the Test Covered
The test covered NCP, ICP, ASCII Telnet as both a user and a server, the login procedure, access to CMS, and operator and console communication. The report also says that multiple message responses, such as listing users, were smooth under moderate to heavy load.
The test included network control, connection setup, Telnet, login, CMS access, and operator communication. It also checked multiple responses while the machine was busy.
§3Reported Result
The author states that the exercised software behaved according to the current specifications and that multiple message responses were smooth under moderate to heavy load. RFC 198 updates RFC 193 and was later obsoleted by RFC 214, according to the unit metadata.
The report records successful behavior for the tested software. It updates RFC 193 and was later replaced by RFC 214.