Flent-users discussion archives
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: flent-users <flent-users@flent.org>
Subject: [Flent-users] IRTT UDP-lite support
Date: Fri, 8 Mar 2019 20:25:40 +0100	[thread overview]
Message-ID: <7BA6324E-CB04-4748-A89F-496374497F34@heistp.net> (raw)

I had a tip to consider adding UDP-lite support for IRTT so I’m first thinking through how this might be helpful and how it would work.

The short summary of UDP-lite is that it allows sending partially damaged packets, with an optional checksum for some bytes at the beginning of the packet (for example, for a packet header). It uses a different IP protocol number (136 instead of 6), so a socket either listens for regular UDP or UDP-lite. Otherwise, UDP-lite is semantically the same as UDP.

Potentially, I could add flags to the client and server to use UDP-lite (or allow specifying a separate port for UDP-lite on the same server). I would still have UDP-lite checksum the IRTT header, because if I can’t assume I have a valid header error then checking will probably get rather complicated. So if there’s damage to the header the packet would be dropped without my knowing, but if the damage occurs in the payload I’d still receive it, then I could add an optional checksum and/or length in the header to detect corruption in the body and keep a count of corrupted packets.

I’m not sure yet how well UDP-lite does through NAT.

But basically, it could be used to estimate how much corruption is occurring on the path from client to server, so we can distinguish between corruption and dropped packets. Presumably this would mainly be useful for mobile networks (not WiFi though, as I think it does it’s own checksums / error correction).


Flent-users mailing list

             reply	other threads:[~2019-03-08 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 19:25 Pete Heist [this message]
2019-03-08 20:31 ` Dave Taht
2019-03-08 21:10   ` Dave Taht
2019-03-09  9:34   ` Pete Heist
2019-03-12 13:17     ` Pete Heist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7BA6324E-CB04-4748-A89F-496374497F34@heistp.net \
    --to=pete@heistp.net \
    --cc=flent-users@flent.org \
    --subject='Re: [Flent-users] IRTT UDP-lite support' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox