RFC 8304: Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)
In plain English — editorial summary, not part of the RFC
This is an informational document that describes the transport protocol interface primitives provided by the User Datagram Protocol (UDP) and the Lightweight User Datagram Protocol (UDP-Lite) transport protocols. It identifies the datagram services exposed to applications and how an application can configure and use the features offered by the Internet datagram transport service. RFC 8303 documents the usage of transport features provided by IETF transport protocols, describing the way UDP, UDP-Lite, and other transport protocols expose their services to applications and how an application can configure and use the features that make up these services. This document provides input to and context for that document, as well as offers a road map to documentation that may help users of the UDP and UDP-Lite protocols.
Document record
- Document ID
- RFC8304
- Published
- February 2018
- Authors
- G. Fairhurst; T. Jones
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8303On the Usage of Transport Features Provided by IETF Transport ProtocolsCurrent
February 2018
- RFC 8311Relaxing Restrictions on Explicit Congestion Notification (ECN) ExperimentationCurrent
January 2018
- RFC 8297An HTTP Status Code for Indicating HintsCurrent
December 2017
- RFC 8312CUBIC for Fast Long-Distance NetworksObsoleted
February 2018
- RFC 8285A General Mechanism for RTP Header ExtensionsCurrent
October 2017
- RFC 8323CoAP (Constrained Application Protocol) over TCP, TLS, and WebSocketsUpdated
February 2018
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8276File System Extended Attributes in NFSv4Current
December 2017
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?