RFC 9868: Transport Options for UDP
In plain English — editorial summary, not part of the RFC
Transport protocols are extended through the use of transport header options. This document updates RFC 768 (UDP) by indicating the location, syntax, and semantics for UDP transport layer options within the surplus area after the end of the UDP user data but before the end of the IP datagram.
Document record
- Document ID
- RFC9868
- Published
- October 2025
- Authors
- J. Touch; C. Heard
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 51
- Also known as
- —
- Updates:
- RFC 768
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9869Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP OptionsCurrent
October 2025
- RFC 9875HTTP Cache GroupsCurrent
October 2025
- RFC 9876Updates to the IANA Registration Procedures for Constrained Application Protocol (CoAP) Content-FormatsCurrent
November 2025
- RFC 9842Compression Dictionary TransportCurrent
September 2025
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
- RFC 9828RTP Payload Format for JPEG 2000 Streaming with Sub-Codestream LatencyCurrent
August 2025
- RFC 9808Content Delivery Network Interconnection (CDNI) Capacity Capability Advertisement ExtensionsCurrent
July 2025
- RFC 9931Security Considerations for Optimistic Protocol Transitions in HTTP/1.1Current
March 2026
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?