Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0079

Logger Protocol error

Pages: 1
Unclassified

ToP   noToC   RFC0079 - Page 1
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  ]