Last Call: <draft-ietf-taps-transports-usage-08.txt> (On the Usage of Transport Features Provided by IETF Transport Protocols) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 31 August 2017 20:55 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-taps-transports-usage-08.txt> (On the Usage of Transport Features Provided by IETF Transport Protocols) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
CC: Zaheduzzaman.Sarker@ericsson.com, draft-ietf-taps-transports-usage@ietf.org, taps-chairs@ietf.org, Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, taps@ietf.org, spencerdawkins.ietf@gmail.com
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <150421291033.16888.1393735251987810236.idtracker@ietfa.amsl.com>
Date: Thu, 31 Aug 2017 13:55:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bCfqpDQ_miPFuBRuIq-PVDFX-tI>

The IESG has received a request from the Transport Services WG (taps) to
consider the following document: - 'On the Usage of Transport Features
Provided by IETF Transport
   Protocols'
  <draft-ietf-taps-transports-usage-08.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-09-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   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 TAPS API.  For UDP
   and UDP-Lite, the first step of the protocol analysis -- a discussion
   of relevant RFC text -- is documented in [FJ16].  XX RFC ED - PLEASE
   REPLACE [FJ16] WITH THE CORRECT RFC NUMBER XXX




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage/ballot/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-taps-transports-usage-08.t… The IESG