RFC145 - Initial Connection Protocol Control Commands

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group J. Postel

Request for Comments: 145 UCLA - NMC

NIC: 6739 4 May 1971

Updates: 123

Obsoletes: 127

Initial Connection Protocol Control Commands

The following is my interpretation of the exchange between NCP's

which would be necessary to carry out the Initial Connection Protocol

of RFC#123. (This note corrects an error pointed out by Eric

Harslem of RAND).

Server NCP User NCP

__________ ________

Listen for Connection L RTS, U, L, l

A

STR, L, U, 32 ALL, l , 1, 32

A

Send 32 bits of data

in 1 message on link l

A

(value is S) Receive 32 bits of data

from link l (value is S)

A

CLS, L, U CLS, U, L

STR, S+1, U+1, B STR, U+1, S, B

s u

RTS, S, U+1, l RTS, U, S+1, l

B C

wait for connection wait for connection

ALL, l , m , b ALL, l , m , b

B B B C C C

data sent to link l data sent on link l

C B

data received on link data received on link l

B C

l , l , and l , are links, m and m are messages allocations, b

A B C B C B

and b are bit allocations, and all other symbols are defined in

C

RFC#123.

[This RFCis also available in .PS and. PDF format.]

[ This RFCwas put into machine readable form for entry ]

[ into the online RFCarchives by Lorrie Shiota]

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
 
 
© 2005- 王朝網路 版權所有 導航