zerotier/sequential-exchange
0
0
Fork 0
mirror of https://github.com/zerotier/sequential-exchange.git synced 2026-05-22 16:28:28 -07:00
Code Issues Packages Projects Releases Wiki Activity

updated readme

Browse Source
This commit is contained in:
Monica Moniot
2024-01-29 15:11:00 -05:00
parent 7db3b49df9
commit d7dca150f1
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6 -1
View File
@@ -28,8 +28,13 @@ features that slow down runtime regardless of whether or not they are used.
A lot of this overhead owes to TCPs sizeable complexity.
That being said SEQEX does lack many of TCP's additional features, such as a dynamic resend timer,
keep-alives, and fragmentation. This can be both a pro and a con, as it means there is a
keep-alives, fragmentation and rate-limiting. This can be both a pro and a con, as it means there is a
lot of efficiency to be gained if these features are not needed or are implemented at a
different protocol layer.
TCP is also ossified into the infrasctructure of the internet.
There are many hardware accelerated implementations of TCP that are faster than this implementation of SEQEX.
Many routers, firewalls and other middleboxes grant it access priviledges not granted to UDP.
Though it is increasingly common for middleboxes to modify TCP traffic owing to TCP's lack of encryption.
Neither SEQEX nor TCP are cryptographically secure.