On the Usage of Transport Features Provided by IETF Transport Protocols
draft-ietf-taps-transports-usage-09

Document Type Active Internet-Draft (taps WG)
Last updated 2017-10-30 (latest revision 2017-10-26)
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Nov 2016 - Submit an Informatio... )
Document shepherd Zaheduzzaman Sarker
Shepherd write-up Show (last changed 2017-07-31)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
TAPS                                                            M. Welzl
Internet-Draft                                        University of Oslo
Intended status: Informational                                 M. Tuexen
Expires: April 29, 2018                 Muenster Univ. of Appl. Sciences
                                                              N. Khademi
                                                      University of Oslo
                                                        October 26, 2017

On the Usage of Transport Features Provided by IETF Transport Protocols
                  draft-ietf-taps-transports-usage-09

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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 29, 2018.

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

Welzl, et al.            Expires April 29, 2018                 [Page 1]
Internet-Draft             Transport Services               October 2017

   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Pass 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Primitives Provided by TCP . . . . . . . . . . . . . . . .  5
       3.1.1.  Excluded Primitives or Parameters  . . . . . . . . . .  9
     3.2.  Primitives Provided by MPTCP . . . . . . . . . . . . . . . 10
     3.3.  Primitives Provided by SCTP  . . . . . . . . . . . . . . . 11
       3.3.1.  Excluded Primitives or Parameters  . . . . . . . . . . 18
     3.4.  Primitives Provided by UDP and UDP-Lite  . . . . . . . . . 18
     3.5.  The service of LEDBAT  . . . . . . . . . . . . . . . . . . 18
   4.  Pass 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
     4.1.  CONNECTION Related Primitives  . . . . . . . . . . . . . . 20
     4.2.  DATA Transfer Related Primitives . . . . . . . . . . . . . 38
   5.  Pass 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
     5.1.  CONNECTION Related Transport Features  . . . . . . . . . . 41
     5.2.  DATA Transfer Related Transport Features . . . . . . . . . 47
       5.2.1.  Sending Data . . . . . . . . . . . . . . . . . . . . . 47
       5.2.2.  Receiving Data . . . . . . . . . . . . . . . . . . . . 48
       5.2.3.  Errors . . . . . . . . . . . . . . . . . . . . . . . . 49
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 49
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 49
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 50
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 50
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 52
   Appendix A.  Overview of RFCs used as input for pass 1 . . . . . . 53
   Appendix B.  How this document was developed . . . . . . . . . . . 54
   Appendix C.  Revision information  . . . . . . . . . . . . . . . . 55
Show full document text