Logger Protocol error
A note identifying a conflict between the logger proposal and the NCP protocol.
Meyer, E., "Logger Protocol error", RFC 79, DOI 10.17487/RFC0079, November 1970, <https://www.rfc-editor.org/info/rfc79>.
@misc{rfc79,
series = {Request for Comments},
number = 79,
howpublished = {RFC 79},
publisher = {RFC Editor},
doi = {10.17487/RFC0079},
url = {https://www.rfc-editor.org/info/rfc79},
author = {E. Meyer},
title = {{Logger Protocol error}},
pagetotal = 1,
year = 1970,
month = nov,
} RFC text
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 ]
ISO Plain Language
On this page
§1The Connection-Setup Conflict
The note identifies a conflict between the official NCP protocol in Protocol Document 1 and the logger protocol described in RFC 66. RFC 66 proposes sending an ALL allocation command immediately after an RTS or STR connection request.
Protocol Document 1 restricts the ALL command to a connection that is already open.
The logger proposal sends ALL while a connection is still being set up. The NCP rules described in Protocol Document 1 allow ALL only after the connection is open.
§1Why the Restriction Helps Implementers
The note says that not having to handle ALL before a connection is established is a simplifying restriction for an NCP implementation. It gives the Multics NCP as an example of an implementation designed with this restriction.
Changing the NCP protocol would affect implementations that rely on the existing rule.
Implementations can be simpler if they handle ALL only after a connection is open. The note says the Multics NCP was designed with that restriction.
§1Change the Logger Proposal
The author argues that the logger protocol should be modified to agree with the existing NCP protocol. He also says the NCP protocol should not be changed at that time except for critical reasons.
The recommended fix is to change the logger proposal so it follows the existing NCP rule. The note does not recommend changing the NCP protocol for this issue.