SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol
draft-ietf-tsvwg-sctp-sack-immediately-03

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2013-08-26 (latest revision 2013-04-08)
Replaces draft-tuexen-tsvwg-sctp-sack-immediately
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Gorry Fairhurst
Shepherd write-up Show (last changed 2013-07-26)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                          M. Tuexen
Internet-Draft                                              I. Ruengeler
Updates: 4960 (if approved)             Muenster Univ. of Appl. Sciences
Intended status: Standards Track                           R. R. Stewart
Expires: October 10, 2013                                 Adara Networks
                                                          April 08, 2013

SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol
             draft-ietf-tsvwg-sctp-sack-immediately-03.txt

Abstract

   This document updates RFC 4960 by defining a method for the sender of
   a DATA chunk to indicate that the corresponding SACK chunk should be
   sent back immediately and not be delayed.  It is done by specifying a
   bit in the DATA chunk header, called the I-bit, which can get set
   either by the SCTP implementation or by the application using an SCTP
   stack.  Since unknown flags in chunk headers are ignored by SCTP
   implementations, this extension does not introduce any
   interoperability problems.

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 October 10, 2013.

Copyright Notice

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

Tuexen, et al.          Expires October 10, 2013                [Page 1]
Internet-Draft              SACK-IMMEDIATELY                  April 2013

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  The I-bit in the DATA Chunk Header  . . . . . . . . . . . . .   3
   4.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Triggering at the Application Level . . . . . . . . . . .   3
     4.2.  Triggering at the SCTP Level  . . . . . . . . . . . . . .   4
   5.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Sender Side Considerations  . . . . . . . . . . . . . . .   4
     5.2.  Receiver Side Considerations  . . . . . . . . . . . . . .   5
   6.  Interoperability Considerations . . . . . . . . . . . . . . .   5
   7.  Socket API Considerations . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   According to [RFC4960] the receiver of a DATA chunk should use
   delayed SACKs.  This delaying is completely controlled by the
   receiver of the DATA chunk and remains the default behavior.

   In specific situations the delaying of SACKs results in reduced
   performance of the protocol.  If such a situation can be detected by
   the receiver, the corresponding SACK can be sent immediately.  For
   example, [RFC4960] recommends the immediate sending if the receiver
   has detected message loss or message duplication.  However, if the
   situation can only be detected by the sender of the DATA chunk,
   [RFC4960] provides no method of avoiding a delay in sending the SACK.

   This document describes a simple extension of the SCTP DATA chunk by
   defining a new flag, the I-bit.  The sender of a DATA chunk indicates
Show full document text