IETF Logo Mail Archive

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

"t.petch" <ietfc@btconnect.com> Wed, 03 November 2010 16:25 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 09FA23A69CF for <tsvwg@core3.amsl.com>; Wed, 3 Nov 2010 09:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.764
X-Spam-Level:
X-Spam-Status: No, score=-1.764 tagged_above=-999 required=5 tests=[AWL=-0.813, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 x3VOL8EfmwN4 for <tsvwg@core3.amsl.com>; Wed, 3 Nov 2010 09:25:01 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by core3.amsl.com (Postfix) with ESMTP id 0211A3A69AB for <tsvwg@ietf.org>; Wed, 3 Nov 2010 09:24:59 -0700 (PDT)
Received: from host86-154-167-163.range86-154.btcentralplus.com (HELO pc6) ([86.154.167.163]) by c2bthomr07.btconnect.com with SMTP id ATV78831; Wed, 03 Nov 2010 16:24:58 +0000 (GMT)
Message-ID: <002d01cb7b6b$0fd92fc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
References: <20100823124502.7BD433A6A2E@core3.amsl.com><4C77BCD1.9010706@cisco.com> <4C7E8A4F.5080807@erg.abdn.ac.uk> <005201cb4de6$40c41440$4001a8c0@gateway.2wire.net> <AB2F4404-EF37-422F-BAF9-A546FFE7A039@lurchi.franken.de> <001501cb4e7b$f2fcf880$4001a8c0@gateway.2wire.net> <87C786EA-F4E6-4868-944A-6989942C19A8@lurchi.franken.de> <00b301cb74fc$5f6dc0c0$4001a8c0@gateway.2wire.net> <780326A5-35E3-49A5-ABD8-B21E5BFC8884@lakerest.net>
Subject: Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt
Date: Wed, 03 Nov 2010 15:59:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4CD18CCD.0102, actions=TAG
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4CD18CDA.01AC, 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: gorry@erg.abdn.ac.uk, Michael Tüxen <Michael.Tuexen@lurchi.franken.de>, 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, 03 Nov 2010 16:25:02 -0000

What happens in a race condition, eg when one endpoint requests an Incoming SSN
Reset for streams 1,2,3 and simultaneously the other endpoint requests an
Outgoing SSN Reset for stream 2? (races are a bit of a mess in TCP)

E1 last sentence; which acknowledgement is being referred to?

Tom Petch


----- Original Message -----
From: "Randy Stewart" <randall@lakerest.net>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Michael Tüxen" <Michael.Tuexen@lurchi.franken.de>; <gorry@erg.abdn.ac.uk>;
<tsvwg@ietf.org>
Sent: Tuesday, October 26, 2010 6:39 PM
Subject: Re: I-D Action:draft-ietf-tsvwg-sctp-strrst-05.txt

v2.23.0 | Report a Bug | By Email