Movatterモバイル変換

Network Working Group                                        A. McKenzieRequest for Comments #93                                             BBNUpdates RFC's 66, 80                                        January 1971Initial Connection Protocol        A review of the Initial Connection Protocol (ICP) firstdescribed in RFC #66 and restated in RFC #80 has revealed an area ofambiguity, which in turn reflects an ambiguity in the Host-HostProtocol Document No. 1.  This is the definition of the message sentover the connection from "Server socket #1".  In both referencedRFC's, the message is defined as "exactly an even 32 bit number".  Itis not clear, however, whether this 32 bit number is meant to followan eight-bit "message data type" code or not, stemming from the factthat the Host-Host Protocol makes provision for such codes but doesnot seem to absolutely demand them.        Only one implementation of an ICP has been documented in theNWG literature - that at UCSB (RFC #74).  The implementers of this ICPhave apparently interpreted the Host-Host Protocol as demanding amessage data type code, and therefore do transmit a code of zero.        Steve Crocker indicates (private communication) that the Host-Host Protocol was intended to require a message data type code.  Wetherefore recommend that RFC numbers 66 and 80 be amended to show thatthe "even 32 bit number" is preceded by a message data type code ofzero (zero is the only code currently defined).       [ This RFC was put into machine readable form for entry ]        [ into the online RFC archives by James Thompson 4/97 ]                                                                [Page 1]