Re: [Tsvwg] Re: WGLC on draft-ietf-tsvwg-prsctp-00

"Randall R. Stewart (home)" <randall@stewart.chicago.il.us> Thu, 26 June 2003 18:21 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12847 for <tsvwg-archive@odin.ietf.org>; Thu, 26 Jun 2003 14:21:30 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QIL3D24138 for tsvwg-archive@odin.ietf.org; Thu, 26 Jun 2003 14:21:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VbMj-0006GZ-FL; Thu, 26 Jun 2003 14:21:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VbLs-0006DB-Uu for tsvwg@optimus.ietf.org; Thu, 26 Jun 2003 14:20:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12751 for <tsvwg@ietf.org>; Thu, 26 Jun 2003 14:20:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VbLq-0004Yy-00 for tsvwg@ietf.org; Thu, 26 Jun 2003 14:20:06 -0400
Received: from stewart.chicago.il.us ([66.93.186.36]) by ietf-mx with esmtp (Exim 4.12) id 19VbLL-0004Y4-00 for tsvwg@ietf.org; Thu, 26 Jun 2003 14:19:55 -0400
Received: from stewart.chicago.il.us (stewart.chicago.il.us [127.0.0.1]) by stewart.chicago.il.us (8.12.8p1/8.12.8) with ESMTP id h5QHeuMg059619; Thu, 26 Jun 2003 12:40:57 -0500 (CDT) (envelope-from randall@stewart.chicago.il.us)
Message-ID: <3EFB3028.1020102@stewart.chicago.il.us>
Date: Thu, 26 Jun 2003 12:40:56 -0500
From: "Randall R. Stewart (home)" <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030323
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Sourabh Ladha (EED)" <Sourabh.Ladha@eed.ericsson.se>
CC: "'tsvwg@ietf.org'" <tsvwg@ietf.org>
Subject: Re: [Tsvwg] Re: WGLC on draft-ietf-tsvwg-prsctp-00
References: <5E5172B4DE05D311B3AB0008C75DA941123CEF8E@edeacnt100.eed.ericsson.se>
In-Reply-To: <5E5172B4DE05D311B3AB0008C75DA941123CEF8E@edeacnt100.eed.ericsson.se>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Sourabh Ladha (EED) wrote:

>You can't send the FWD-TSN until the left edge of the number
>of TSN's is concurrent with your "abandoned chunk"
>
>
>  
>
>>Just because you abandon it does not mean you tell the peer.. you have
>>to follow all or the normal RFC2960 procedures and ONLY when you
>>have marked it to abandon and you would have retransmitted and the
>>left edge is aligned will you send the FWD-TSN... you may decide
>>to delay a while... aka the 200ms but you send only at the normal
>>retrans opp..
>>    
>>
>
>So consider this:
>
>everything before has been ACKed
>-----TSN101----> XlostX
>-----TSN102----> 
>-----TSN103---->
>-----TSN104---->
>-----TSN105----> 
>
>----TSN101-----> retransmitted
>---abandon 101--
>Now all your three points for sending a FW-TSN (as mentioned by you above) hold. So,
>
<<<<<here is your error... no stimulus

>-----FW TSN----
>  
>
So you can't send the FWD-TSN here.. unless a T3 occured

>Where is the "at least 1RTO"?? What if the FW TSN now reaches before TSN 101 going on a possible alternate path? 
>  
>
You have not reached a point to retransmit it yet...

You must hit a RTO or 4 strikes the key is in A4 and A5... you must
have a stimuleous to send the FWD-TSN i.e. a T3-Timeout (A5) or
a SACK (A4)..

You retransmitted 101 as shown for one of two reasons (before
it was abandoned)...

If you retransmitted TSN101 due to T3.. you are collapsed to 1 MTU and
have burnt that in sending TSN101. If the SACK of 105 is the 4th strike
for fast retransmit... you have sent 101 and have done a CWND reduction
and must await the T3 for 101 or a SACK for 101... so you have
no chance to send the FWD-TSN until a SACK or T3 occurs...

I see at a minimum a RTO or if 101 is sack'd no FWD-TSN is needed...

R





>
>-S
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg
>
>
>  
>



_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg