diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc23.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc23.txt')
-rw-r--r-- | doc/rfc/rfc23.txt | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/rfc/rfc23.txt b/doc/rfc/rfc23.txt new file mode 100644 index 0000000..4b56a0e --- /dev/null +++ b/doc/rfc/rfc23.txt @@ -0,0 +1,22 @@ +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. |