From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Educate colleges on tcp vs udp
Date: Thu, 27 May 2021 15:17:41 -0700 [thread overview]
Message-ID: <167c73ae-19b0-1b9d-0d89-44a903dfafbd@sewingwitch.com> (raw)
In-Reply-To: <20210527074250.E8D8740605C@ip-64-139-1-69.sjc.megapath.net>
On 5/27/2021 12:42 AM, Hal Murray wrote:
> TCP is for things like FTP and web browsing - transferring large chunks of
> data. UDP is for simple things like NTP or DNS. TCP is generally implemented
> in the kernel. UDP retransmissions are generally implemented by user code.
UDP is also for unicast where late is just as bad as never. I've got an
IoT sensor that unicasts readings to a PC that uses UDP in a 2-host network.
Compare to FireWire's isochronous connections that send unicast packets
at a regular rate, intended for streaming media and commonly used for
cameras.
next prev parent reply other threads:[~2021-05-27 22:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 7:42 Hal Murray
2021-05-27 12:15 ` Jonathan Morton
2021-05-27 22:17 ` Kenneth Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 6:01 Taraldsen Erik
2021-05-23 10:23 ` Jonathan Morton
2021-05-23 18:47 ` Erik Auerswald
2021-05-23 21:02 ` Jonathan Morton
2021-05-23 21:42 ` Erik Auerswald
2021-05-26 22:44 ` Mark Andrews
2021-05-27 3:11 ` Erik Auerswald
2021-05-24 18:51 ` Erik Auerswald
2021-05-25 6:38 ` Taraldsen Erik
2021-05-26 18:09 ` Dave Taht
2021-05-27 6:32 ` Taraldsen Erik
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167c73ae-19b0-1b9d-0d89-44a903dfafbd@sewingwitch.com \
--to=shiva@sewingwitch.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox