Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @dthompson@toot.cat
dave@dthompson@toot.cat (2026-10-19 21:52:25)
Some other reliable protocols built on UDP are 1) RUDP, made by Bell Labs for Plan9, which has a draft RFC from 1999 and 2) SCTP, notably used by WebRTC. I think I can rule out SCTP as a good fit because it has multistreaming (like QUIC) and multihoming which are both unnecessary for OCapN. RUDP seems much simpler but anything that was ever deployed seems to use something that forks from the draft spec, but perhaps it's a good starting point.
---Reply---
Tim Panton@steely_glint@chaos.social (2026-10-20 00:31:27)
@dthompson You could look at IL (also from plan9 and direct over IP but could probably run nicely over UDP or DTLS. )
Also - what are your target endpoints?
I'm playing with RTCTransport which is basically ICE+DTLS + Browser API - which might be interesting but you would have to add reliability somehow.
Reply
---Replies---
dave@dthompson@toot.cat (2026-10-20 02:11:29)
@steely_glint thanks for the pointer re: IL. something that runs on UDP is appealing because I can implement it in userspace.
I'm thinking about this for "native" applications on linux, etc. with direct access to UDP sockets and thus can take advantage of NAT hole punching tricks.
I think I'd rather build directly on UDP than add reliability to something like RTCTransport.