RFC145 - Initial Connection Protocol Control Commands

时间:2005-02-10 来源: 作者: 点击:
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 necessa
  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]
------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容