Skip to main content

Transport Protocol Issues of In-Network Computing Systems

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Ike Kunze , Klaus Wehrle , Dirk Trossen
Last updated 2023-07-13 (Latest revision 2021-10-25)
RFC stream (None)
Intended RFC status (None)
Additional resources This paper bases on some of the content of this draft
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Today's transport protocols offer a variety of functionality based on the notion that the network is to be treated as an unreliable communication medium. Some, like TCP, establish a reliable connection on top of the unreliable network while others, like UDP, simply transmit datagrams without a connection and without guarantees into the network. These fundamental differences in functionality have a significant impact on how COIN approaches can be designed and implemented. Furthermore, traditional transport protocols are not designed for the multi-party communication principles that underlie many COIN approaches. This document raises several questions regarding the use of transport protocols in connection with COIN.


Ike Kunze
Klaus Wehrle
Dirk Trossen

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)