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/rfc79.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc79.txt')
-rw-r--r-- | doc/rfc/rfc79.txt | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc79.txt b/doc/rfc/rfc79.txt new file mode 100644 index 0000000..97149f5 --- /dev/null +++ b/doc/rfc/rfc79.txt @@ -0,0 +1,59 @@ + + + + + + +Network Working Group Edwin W. Meyer, Jr. +Request for Comments: 79 MIT Project MAC +NIC 5601 November 16, 1970 + + + + Logger Protocol Error + + A conflict was recently discovered between the official NCP protocol + as described in protocol document 1 and the logger protocol as + described in RFC 66 by Steve Crocker. Steve suggested that we put + out an RFC to alert the network community to this point. + + In RFC 66, it is proposed that an ALL allocate command be sent + immediately following an RTS or STR request for connection. This + conflicts with the restriction stated in Protocol Document 1 that an + ALL command can be given only for an "open" connection. + + To not be required to handle an ALL command before a connection is + established is a simplifying restriction that an NCP implementation + may take advantage of. For example, the Multics NCP is currently + designed this way. For this reason, and also because we believe that + the NCP protocol should not be changed now except for critical + reasons it is felt that the proposed logger protocol should be + modified to agree with the existing NCP protocol. + + + + + + + + + [ This RFC was put into machine readable form for entry ] + [ into the online RFC archives by Alison De La Cruz 11/00 ] + + + + + + + + + + + + + + + + +Meyer [Page 1] + |