RFC 22 (rfc22) - Page 2 of 2
Host-host control message formats
Alternative Format: Original Text Document
RFC 22 Host-Host Control Message Formats October 1969 <6>Please stop transmitting over link number L. This is called the CEASE directive. <7> 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> 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 | | | |______|_______|___________|_________| | | | | 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 RFC was put into machine readable form for entry ] [ into the online RFC archives by Alison De La Cruz 12/00 ] Cerf



