[Taps] RFC 8095 on Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
rfc-editor@rfc-editor.org Tue, 07 March 2017 22:19 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 324E0129660; Tue, 7 Mar 2017 14:19:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEF0b17nHnZS; Tue, 7 Mar 2017 14:19:05 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72BDB129657; Tue, 7 Mar 2017 14:18:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0675EB819B9; Tue, 7 Mar 2017 14:18:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221838.0675EB819B9@rfc-editor.org>
Date: Tue, 07 Mar 2017 14:18:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/onCtmcRWhZWeLS4s6Svx0OpN_Fs>
Cc: drafts-update-ref@iana.org, taps@ietf.org, rfc-editor@rfc-editor.org
Subject: [Taps] RFC 8095 on Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2017 22:19:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8095
Title: Services Provided by IETF Transport
Protocols and Congestion Control Mechanisms
Author: G. Fairhurst, Ed.,
B. Trammell, Ed.,
M. Kuehlewind, Ed.
Status: Informational
Stream: IETF
Date: March 2017
Mailbox: gorry@erg.abdn.ac.uk,
ietf@trammell.ch,
mirja.kuehlewind@tik.ee.ethz.ch
Pages: 54
Characters: 126843
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-taps-transports-14.txt
URL: https://www.rfc-editor.org/info/rfc8095
DOI: 10.17487/RFC8095
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.
This document is a product of the Transport Services Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC