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

The information below is for an old version of the document
Document Type Active Internet-Draft (taps WG)
Last updated 2016-01-08
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TAPS                                                            M. Welzl
Internet-Draft                                        University of Oslo
Intended status: Informational                                 M. Tuexen
Expires: July 11, 2016                  Muenster Univ. of Appl. Sciences
                                                              N. Khademi
                                                      University of Oslo
                                                         January 8, 2016

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

Abstract

   This document describes how transport protocols expose services to
   applications and how an application can configure and use the
   features of a transport service.

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 July 11, 2016.

Copyright Notice

   Copyright (c) 2016 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
   (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

Welzl, et al.             Expires July 11, 2016                 [Page 1]
Internet-Draft             Transport Services               January 2016

   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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Primitives Provided by TCP . . . . . . . . . . . . . . . .  5
       3.1.1.  Excluded Primitives  . . . . . . . . . . . . . . . . .  7
     3.2.  Primitives Provided by SCTP  . . . . . . . . . . . . . . .  8
       3.2.1.  Excluded Primitives  . . . . . . . . . . . . . . . . . 11
   4.  Pass 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1.  CONNECTION Related Primitives  . . . . . . . . . . . . . . 12
     4.2.  DATA Transfer Related Primitives . . . . . . . . . . . . . 16
   5.  Pass 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
     5.1.  CONNECTION Related Transport Service Features  . . . . . . 18
     5.2.  DATA Transfer Related Transport Service Features . . . . . 20
       5.2.1.  Sending Data . . . . . . . . . . . . . . . . . . . . . 20
       5.2.2.  Receiving Data . . . . . . . . . . . . . . . . . . . . 21
       5.2.3.  Errors . . . . . . . . . . . . . . . . . . . . . . . . 22
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 22
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 22
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 22
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 23
   Appendix A.  Overview of RFCs used as input for pass 1 . . . . . . 24
   Appendix B.  How to contribute . . . . . . . . . . . . . . . . . . 24
   Appendix C.  Revision information  . . . . . . . . . . . . . . . . 26
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26

Welzl, et al.             Expires July 11, 2016                 [Page 2]
Internet-Draft             Transport Services               January 2016

1.  Terminology

   Transport Service Feature:  a specific end-to-end feature that a
      transport service provides to its clients.  Examples include
      confidentiality, reliable delivery, ordered delivery, message-
      versus-stream orientation, etc.
   Transport Service:  a set of transport service features, without an
      association to any given framing protocol, which provides a
      complete service to an application.
   Transport Protocol:  an implementation that provides one or more
Show full document text