SESK: Stuff Everyone Should Know · sesk.info/aplus-udp-delivery
Which protocol, defined in RFC 768, does not guarantee delivery of its datagrams?
UDP (User Datagram Protocol) does not guarantee delivery.
- UDP ✔
- TCP
- HTTPS
Why: RFC 768 says UDP is transaction oriented and delivery and duplicate protection are not guaranteed. That makes it light and fast, so it suits things like live voice and DNS lookups.
Huh, didn't know that: RFC 768, which defines UDP, is dated 28 August 1980.
Knock, knock. Who's there? [Extremely long pause] Java.
Like this card?
References
Answer: UDP. RFC 768 says UDP is transaction oriented and delivery and duplicate protection are not guaranteed. That makes it light and fast, so it suits things like live voice and DNS lookups.
- RFC 768: User Datagram Protocol www.rfc-editor.org/rfc/rfc768
The protocol is transaction oriented, and delivery and duplicate protection are not guaranteed.
Checked 2026-10-10.
Think this answer is wrong? Tap "Challenge this answer" on the card in the game and tell us why.
More stuff everyone should know
That's stuff everyone should know.