RFC 8303: On the Usage of Transport Features Provided by IETF Transport Protocols
In plain English — editorial summary, not part of the RFC
This document describes how the transport protocols Transmission Control Protocol (TCP), MultiPath TCP (MPTCP), Stream Control Transmission Protocol (SCTP), User Datagram Protocol (UDP), and Lightweight User Datagram Protocol (UDP-Lite) expose services to applications and how an application can configure and use the features that make up these services. It also discusses the service provided by the Low Extra Delay Background Transport (LEDBAT) congestion control mechanism. The description results in a set of transport abstractions that can be exported in a transport services (TAPS) API.
Document record
- Document ID
- RFC8303
- Published
- February 2018
- Authors
- M. Welzl; M. Tuexen; N. Khademi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 56
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8304Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)Current
February 2018
- RFC 8297An HTTP Status Code for Indicating HintsCurrent
December 2017
- RFC 8311Relaxing Restrictions on Explicit Congestion Notification (ECN) ExperimentationCurrent
January 2018
- 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?