Transmission of Multiple Control Messages
RFC 23

Document Type RFC - Unknown (October 1969; No errata)
Last updated 2014-05-06
Stream Legacy
Formats plain text html pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 23 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           G. Gregg
Request for Comments: 23                                            UCSB
                                                         16 October 1969

                TRANSMISSION OF MULTIPLE CONTROL MESSAGES

The network program at a site must be prepared to send or receive more
than one control message in a single control communication.

During the time that the control link is blocked awaiting RFNM, it is
possible that a number of control messages to a particular remote host
will accumulate.  When the link is unblocked, these should all be sent
in a single communication for greatest efficiency.

For receiving, it will be necessary to have a loop which returns to
decode and take action on successive control messages until the control
communication is exhausted.