RFC 3828: The Lightweight User Datagram Protocol (UDP-Lite)
In plain English — editorial summary, not part of the RFC
This document describes the Lightweight User Datagram Protocol (UDP-Lite), which is similar to the User Datagram Protocol (UDP) (RFC 768), but can also serve applications in error-prone network environments that prefer to have partially damaged payloads delivered rather than discarded. If this feature is not used, UDP-Lite is semantically identical to UDP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3828
- Published
- July 2004
- Authors
- L-A. Larzon; M. Degermark; S. Pink; L-E. Jonsson; G. Fairhurst
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 6335
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5097MIB for the UDP-Lite protocolCurrent
January 2008
- RFC 8095Services Provided by IETF Transport Protocols and Congestion Control MechanismsCurrent
March 2017
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
- RFC 3782The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted
April 2004
- RFC 3758Stream Control Transmission Protocol (SCTP) Partial Reliability ExtensionCurrent
May 2004
- RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent
March 2004
- RFC 3708Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious RetransmissionsCurrent
February 2004
- RFC 3649HighSpeed TCP for Large Congestion WindowsCurrent
December 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?