Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-08.txt

"t.petch" <ietfc@btconnect.com> Wed, 01 December 2010 10:14 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB33E3A6A5E for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 02:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.195
X-Spam-Level:
X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, SARE_SUB_6CONS_WORD=0.356]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QoVt1PQ5xveF for <tsvwg@core3.amsl.com>; Wed, 1 Dec 2010 02:14:58 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by core3.amsl.com (Postfix) with ESMTP id 876423A69C5 for <tsvwg@ietf.org>; Wed, 1 Dec 2010 02:14:56 -0800 (PST)
Received: from host81-156-71-67.range81-156.btcentralplus.com (HELO pc6) ([81.156.71.67]) by c2beaomr06.btconnect.com with SMTP id BCN80260; Wed, 01 Dec 2010 10:16:04 +0000 (GMT)
Message-ID: <005501cb9138$122c99a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
References: <20101129173002.3461.46301.idtracker@localhost>
Subject: Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-08.txt
Date: Wed, 01 Dec 2010 10:13:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4CF62064.008D, actions=TAG
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4CF62067.03D8, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 10:14:59 -0000

Um; I was expecting perhaps a little more on race conditions.

I had a more complex race condition in mind, which will work, I have
convinced myself of that, provided everyone expects it to:-)

A appl requests a reset of streams 2 and 3
A sends Incoming SSN Reset Request Parameter for streams 2 and 3 and starts
timer
A receives Outgoing SSN Reset Request Parameter for streams 1 and 2 with zero
Stream Reset Request Sequence Number
A sends ACK and  has a think about what to do .....
 - waits for Outgoing SSN Reset Request Parameter for streams 2 and 3?
 - resets streams 1 and 2?
 - raises an event for streams 1 and 2?

Meanwhile,
B appl requests a reset of streams 1 and 2
B sends Outgoing SSN Reset Request Parameter for streams 1 and 2 and starts
timer
B receives Incoming SSN Reset Request Parameter for streams 2 and 3
B has timer running so must wait

Therefore
A must reset streams 1 and 2 and send Stream Reset Response Parameter to let B
proceed
B receives Stream Reset Response Parameter and stops timer
B can and must now send Outgoing SSN Reset Request Parameter for streams 2 and 3
with non-zero Stream Reset Request Sequence Number and starts timer
A receives Outgoing SSN Reset Request Parameter for streams 2 and 3 with
non-zero Stream Reset Request Sequence Number and stops timer
A resets streams 2 and 3 and sends Stream Reset Response Parameter
B receives Stream Reset Response Parameter and stops timer

A appl and B appl both receive events, one for reset of streams 1 and 2, the
other for streams 2 and 3 (which may puzzle them).

Of course, a slightly different scenario would be for both A and B to select the
same streams, say 1 and 3 (perhaps as a result of an application level event) in
which case, the scope for getting it wrong is even greater; when A receives
Outgoing SSN Reset Request Parameter with zero Stream Reset Request Sequence
Number, it might send an Error - Bad Sequence Number, which could really confuse
B

Tom Petch

----- Original Message -----
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <tsvwg@ietf.org>
Sent: Monday, November 29, 2010 6:30 PM
Subject: I-D Action:draft-ietf-tsvwg-sctp-strrst-08.txt


> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Transport Area Working Group Working Group of
the IETF.
>
>
> Title           : Stream Control Transmission Protocol (SCTP) Stream
Reconfiguration
> Author(s)       : R. Stewart, et al.
> Filename        : draft-ietf-tsvwg-sctp-strrst-08.txt
> Pages           : 31
> Date            : 2010-11-29
>
> Many applications that use SCTP want the ability to "reset" a stream.
> The intention of resetting a stream is to set the numbering sequence
> of the stream back to 'zero' with a corresponding notification to the
> upper layer that this has been performed.  The applications that want
> this feature want it so that they can "re-use" streams for different
> purposes but still utilize the stream sequence number so that the
> application can track the message flows.  Thus, without this feature,
> a new use of an old stream would result in message numbers greater
> than expected unless there is a protocol mechanism to "reset the
> streams back to zero".  This document also includes methods for
> resetting the transport sequence numbers, adding additional streams
> and resetting all stream sequence numbers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-strrst-08.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>