Skip to content

Commit

Permalink
Merge pull request #1175 from ietf-tapswg/1140-connectionless-protocols
Browse files Browse the repository at this point in the history
Resolves #1140 Handling connectionless protocols
  • Loading branch information
tfpauly authored Jun 3, 2023
2 parents 9761fa6 + c9147d8 commit 54ff3b4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion draft-ietf-taps-impl.md
Original file line number Diff line number Diff line change
Expand Up @@ -488,7 +488,7 @@ be any "establishment" message (like a TCP SYN).

While protocols that use an explicit handshake to validate a connection to a peer can be used for racing multiple establishment attempts in parallel, connectionless protocols such as raw UDP do not offer a way to validate the presence of a peer or the usability of a Connection without application feedback. An implementation should consider such a Protocol Stack to be established as soon as the Transport Services system has selected a path on which to send data.

However, this can cause a problem if a specific peer is not reachable over the network using the connectionless protocol, or data cannot be exchanged with the peer for any other reason. To mitigate this, an application can use a Message Framer ({{message-framers}}) on top of a connectionless protocol to only mark a specific connection attempt as ready when some data has been received, or after some application-level handshake has been performed.
However, this can cause a problem if a specific peer is not reachable over the network using the connectionless protocol, or data cannot be exchanged with the peer for any other reason. To handle the lack of an explicit handshake in the underlying protocol, an application can use a Message Framer ({{message-framers}}) on top of a connectionless protocol to only mark a specific connection attempt as ready when some data has been received, or after some application-level handshake has been performed by the Message Framer.

## Implementing Listeners {#listen}

Expand Down

0 comments on commit 54ff3b4

Please sign in to comment.