[Taps] RFC 8303 on On the Usage of Transport Features Provided by IETF Transport Protocols
rfc-editor@rfc-editor.org Thu, 08 February 2018 07:06 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 859A112D862; Wed, 7 Feb 2018 23:06:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 EGFpIZEnoBjH; Wed, 7 Feb 2018 23:06:01 -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 F22AB1200E5; Wed, 7 Feb 2018 23:06:00 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0976EB80D98; Wed, 7 Feb 2018 23:05:52 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, taps@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180208070552.0976EB80D98@rfc-editor.org>
Date: Wed, 07 Feb 2018 23:05:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/EkeYEl3EZDa2Wg05BN6WordOzEs>
Subject: [Taps] RFC 8303 on On the Usage of Transport Features Provided by IETF Transport Protocols
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <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: Thu, 08 Feb 2018 07:06:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8303
Title: On the Usage of Transport
Features Provided by IETF Transport Protocols
Author: M. Welzl,
M. Tuexen,
N. Khademi
Status: Informational
Stream: IETF
Date: February 2018
Mailbox: michawe@ifi.uio.no,
tuexen@fh-muenster.de,
naeemk@ifi.uio.no
Pages: 56
Characters: 117774
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-taps-transports-usage-09.txt
URL: https://www.rfc-editor.org/info/rfc8303
DOI: 10.17487/RFC8303
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.
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