|
RFC Home |
Full RFC Index |
Recent RFCs |
RFC Standards |
Best Current Practice |
RFC Errata |
1 April RFC |
|
||||||
|
IETF RFC 23
Transmission of Multiple Control Messages Last modified on Thursday, May 10th, 2001 Permanent link to RFC 23 Search GitHub Wiki for RFC 23 Show other RFCs mentioning RFC 23 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. Transmission of Multiple Control Messages RFC TOTAL SIZE: 848 bytes PUBLICATION DATE: Thursday, May 10th, 2001 LEGAL RIGHTS: The IETF Trust (see BCP 78) |