Browse Prior Art Database

Services Provided by IETF Transport Protocols and Congestion Control Mechanisms (RFC8095) Disclosure Number: IPCOM000249618D
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-08

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Fairhurst: AUTHOR [+5]


Internet applications make use of the services provided by a transport protocol, such as TCP (a reliable, in-order stream protocol) or UDP (an unreliable datagram protocol). We use the term "transport service" to mean the end-to-end service provided to an application by the transport layer. That service can only be provided correctly if information about the intended usage is supplied from the application. The application may determine this information at design time, compile time, or run time, and may include guidance on whether a feature is required, a preference by the application, or something in between. Examples of features of transport services are reliable delivery, ordered delivery, content privacy to in-path devices, and integrity protection.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Internet Engineering Task Force (IETF)                 G. Fairhurst, Ed. Request for Comments: 8095                        University of Aberdeen Category: Informational                                 B. Trammell, Ed. ISSN: 2070-1721                                       M. Kuehlewind, Ed.                                                               ETH Zurich                                                               March 2017

                           Services Provided by        IETF Transport Protocols and Congestion Control Mechanisms


   This document describes, surveys, and classifies the protocol    mechanisms provided by existing IETF protocols, as background for    determining a common set of transport services.  It examines the    Transmission Control Protocol (TCP), Multipath TCP, the Stream    Control Transmission Protocol (SCTP), the User Datagram Protocol    (UDP), UDP-Lite, the Datagram Congestion Control Protocol (DCCP), the    Internet Control Message Protocol (ICMP), the Real-Time Transport    Protocol (RTP), File Delivery over Unidirectional Transport /    Asynchronous Layered Coding (FLUTE/ALC) for Reliable Multicast, NACK-    Oriented Reliable Multicast (NORM), Transport Layer Security (TLS),    Datagram TLS (DTLS), and the Hypertext Transport Protocol (HTTP),    when HTTP is used as a pseudotransport.  This survey provides    background for the definition of transport services within the TAPS    working group.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Fairhurst, et al.             Informational                     [Page 1]
 RFC 8095                   Transport Services                 March 2017

 Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (