Movatterモバイル変換
[0]ホーム
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page]
Obsoleted by:123 UNKNOWN
Updated by:80,93Errata ExistNetwork Working Group S. CrockerRequest for Comments #66 UCLA 26 August 70 3rd Level Ideas and other NoisesOn 12 August 70, I met a BBN with representatives from BBN and MIT andwe discussed third llevel protocol.Dial-up The following proposed dial-up protocol was agreed upon at themeeting.The purpose of this piece of protocol is to get a process at one site(hereafter the using site) in contact with the logger at the other site(hereafter the serving site).To initiate contact, the using process attaches a receive socket US andrequests connection to socket 1 in the serving host. The using NCP thussends 1 4 4 1 --------------------------------------------------- |RTS | US | 1 | p| --------------------------------------------------- |ALL | P | space | -------------------------------over link 1, where US is the user's receive socket, p is the link, andspace is some nominal spae allocation.The serving Host may decide to refuse contact, in which case it willrespond with the standard CLS. If it accepts contact, however, it willsend exactly an even 32 bit number over the connection and close theconnection. This even 32 bit number is the name of a receive socket inthe serving Host. This socket and the next higher numbered socket are [Page 1]
RFC 66 3rd Level Ideas and other NoiseNetwork Working Group S. CrockerRequest for Comments #66 UCLA 26 August 70reserved for contact with the user. Thus the serving NCP sends 1 4 1 ---------------------------- | STR | 1 | US| ----------------------------on link 1, followed by 4 ----------- | SS | -----------on link p. Note that SS must be even.After sending the server socket number, SS, the NCP sends 1 4 4 ------------------------------------- |CLS | 1 | US | ------------------------------------- |STR | SS+1 | US | ------------------------------------------ |RTS | SS | US+1 | q | ------------------------------------------ |ALL | q | space | ----------------------------- [Page 2]
RFC 66 3rd Level Ideas and other NoiseNetwork Working Group S. CrockerRequest for Comments #66 UCLA 26 August 70The using Host also sets up these connections by sending 1 4 4 ---------------------------------------- | CLS | US | 1 | ---------------------------------------- | STR | US+1 | SS | -------------------------------------------- | RTS | US | SS+1 | r | --------------------------------------------At this point the user should be connected to the logger at the servingsite.Standard Console We next agreed on an initial network standard console: 7-bit ASCIIin 8 bit fields with the eight bit on, transmitted in contiguousstreams. The speific codes are listed inappendix H of the IMPOperations manual, BBN report #1877. This seems to work only somehardship on PDP-10's and be fine for all others. For break or interrupt many systems use one of the standardcharacters; for those which need another kind of signal, 1 1 ------------ |INR | r | ------------sent over the control link should suffice. [ This RFC was put into machine readable form for entry ][ into the online RFC archives by Gottfried Janik 2/98 ] [Page 3]
[8]ページ先頭