diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc78.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc78.txt')
-rw-r--r-- | doc/rfc/rfc78.txt | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc78.txt b/doc/rfc/rfc78.txt new file mode 100644 index 0000000..04a3d79 --- /dev/null +++ b/doc/rfc/rfc78.txt @@ -0,0 +1,59 @@ + + + + + + +Network Working Group E. Harslem +Request for Comments: 78 J. Heafner +NIC 5199 J. White + + + NCP Status Report: UCSB/RAND + +NCP Checkout + + UCSB an RAND recently conducted UCSB console to/from RAND console + validation fo teh respective NCPs. The exercise was simply to verify + that the NCPs behaved according to Document #1 protocol. + +What was Learned + + The UCSB and RAND NCPs responded as specified in Document #1. RAND + uncovered a few minor problems with their Network Services Program + (NSP) that interfaces video graphics consoles to the NCP. The nature + of these problems were data format conversions and human factors + aspects of display presentation of status information. + +The Immediate Future + + 1. Both UCSB and RAND will be happy to participate with other sites + in verifying their NCPs. + + 2. We intend to conduct additional exercises involving data re- + configurations and file transmissions. + + + + JFH:hs + + + [ This RFC was put into machine readable form for entry ] + [ into the online RFC archives by Josh Elliott 1/98 ] + + + + + + + + + + + + + + + + [Page 1] + |