岁月联盟 · 中国技术网 本站主页 | 安全认证 | 用户服务 | 技术论坛
新闻快报 | 新手学堂 | 黑客特区 | 程序语言 | 数 据 库 | 防 火 墙 | 路由交换 | 系统集成 | 服 务 器 | 存储备份 | 考试认证
Windows | Linux | Java | 协议分析 | 问题解答 | 进程大全 | 网页设计 | 多 媒 体 | 图库资料 | 软件下载 | 站内下载
  您现在的位置: 岁月联盟 >> 协议 >> RFC专题 >> 英文RFC文档 >> 协议分析正文
RFC22 - Host-host control message formats
作者:未知 文章来源:本站整理 点击数: 更新时间:2006-11-19 16:49:37

Network Working Group Vint Cerf
Request for Comments: 22 UCLA
October 17, 1969

Host-Host Control Message Formats

NWG/RFC11 has been modified at UCLA; and will be republished. In
the meantime, it seems important to report a new control message
format which does not use 7-bit ASCII character mode of transmission.

All Host-Host control messages consist of sequences of 8-bit bytes of
the form:

<control byte> <parameter byte l> ... <parameter byte n>

It is reasonable to transmit more than one control message in any
given packet, although this is not mandatory.

Presently, 9 control messages have been defined by UCLA these are
given in the table below along with their parameters. The
interpretation is given from the point of view of the transmitting
host. ("L" or "Li" mean Link#, and are binary values.)

Control byte Parameter Interpretation

<0> <L> Please establish primary connection;
our output link # is L

<1> <L,> <L2> Please establish auxiliary connection
parallel to our primary output link L.
The auxiliary output link is L2.

<2> <L1> <L2> DK primary. Your primary output link
to us was L; our primary output link
to you is L2.

<3> <L1> <L2> OK auxiliary. Your auxiliary output
link is Li, our auxiliary output link
is L2.

<4> <L> Not OK primary. We cannot establish a
primary connection. Your primary
output link number was L.

<5> <Li> <L2> Not OK auxiliary. We cannot establish
an auxiliary connection. Your primary
output link no was L2.

<6> <L> Please stop transmitting over link
number L. This is called the CEASE
directive.

<7> <L> We are CLOSING our output link number
L. You may get this message before
the last message arrives over this
link since control messages are higher
priority than regular data messages.

<8> <L> UNCEASE: that is, you may resume
transmitting over output link number
L.

Each control message is embedded in the appropriate message structure
e.g.:

<-------------32 bits --------------->
| HEADER |
|____________________________________|
| | | | |
| mark | l | <L1> | <L2> |
|______|_______|___________|_________|
| | |
| checksum | Padding |
|_________________|__________________|
typical control message (please
establish auxiliary link #L2
parallel to our primary link #l)

The header for all HOST-HOST control messages is given below:

0 3 4 7 8 9 10 14 LINK# 24 31
_______________________________________________________________
| | | | | |////////////////|
| FLAGS | TYPE | H | SITE | 00000001 |////////////////|
|_______|______|_____|_______|_______________|________________|

where FLAGS - 0000
TYPE - 0000 (regular message)
H - host #(0-3) at SITE (usually 0 for single HOST sites)
SITE - Site #
LINK# - 00000001 (HOST-HOST control link)

[ This RFCwas put into machine readable form for entry ]
[ into the online RFCarchives by Alison De La Cruz 12/00 ]

 


  • 上一个协议分析:
  • 下一个协议分析:
  •  
    热门文章
    推荐文章
    关于我们 | 发展历程 | 网站地图 | 广告服务 | 招贤纳士 | 战略合作 | 友情链接 | 著作声明 | 联系我们
    Copyright © 2002-2007 SYUE All rights reserved.
    E_mail:Admin@Syue.Com 皖ICP备05004589号
    未经授权禁止转载、摘编、复制或建立镜像.如有违反,追究法律责任.
    天龙八部私服 传世私服 传奇世界私服 天龙八部私服 bet365 天龙八部私服 热血江湖私服 英雄合击传奇私服 热血江湖私服 bet365 bet365