RFC 8923: A Minimal Set of Transport Services for End Systems
In plain English — editorial summary, not part of the RFC
This document recommends a minimal set of Transport Services offered by end systems and gives guidance on choosing among the available mechanisms and protocols. It is based on the set of transport features in RFC 8303.
Document record
- Document ID
- RFC8923
- Published
- October 2020
- Authors
- M. Welzl; S. Gjessing
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 44
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8095Services Provided by IETF Transport Protocols and Congestion Control MechanismsCurrent
March 2017
- RFC 8922A Survey of the Interaction between Security Protocols and Transport ServicesCurrent
October 2020
- RFC 8941Structured Field Values for HTTPObsoleted
February 2021
- RFC 8942HTTP Client HintsCurrent
February 2021
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 8888RTP Control Protocol (RTCP) Feedback for Congestion ControlCurrent
January 2021
- RFC 8961Requirements for Time-Based Loss DetectionCurrent
November 2020
- RFC 8881Network File System (NFS) Version 4 Minor Version 1 ProtocolCurrent
August 2020
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?