Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues

Randy Stewart <randall@lakerest.net> Wed, 16 March 2011 14:06 UTC

Return-Path: <randall@lakerest.net>
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 09B103A69A3 for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level:
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[AWL=0.300, 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 6HIxuu7CtIIO for <tsvwg@core3.amsl.com>; Wed, 16 Mar 2011 07:06:52 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:213:d4ff:fef3:2d8d]) by core3.amsl.com (Postfix) with ESMTP id 9FD933A69A1 for <tsvwg@ietf.org>; Wed, 16 Mar 2011 07:06:51 -0700 (PDT)
Received: from [10.193.34.52] ([12.133.183.34]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id p2GE8CKs086089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 16 Mar 2011 10:08:15 -0400 (EDT) (envelope-from randall@lakerest.net)
Subject: Re: WGLC for draft-ietf-tsvwg-sctp-strrst-09 continues
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <4D808D2A.9060705@oracle.com>
Date: Wed, 16 Mar 2011 10:07:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFC0BCC4-9168-4E18-A718-7FF3DBACB24B@lakerest.net>
References: <201102080311.p183BpvU025288@sj-core-2.cisco.com> <201103132048.p2DKmrP1017369@rcdn-core-2.cisco.com> <4D7DE97D.6010609@oracle.com> <14AE857C-8699-46EB-9FB0-E740CFED0BCE@lurchi.franken.de> <4D7F3C4B.7090303@oracle.com> <D891B32A-51F4-401C-A4D6-4DF5FEAF3E91@lakerest.net> <4D808D2A.9060705@oracle.com>
To: Kacheong Poon <ka-cheong.poon@oracle.com>
X-Mailer: Apple Mail (2.1082)
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, 16 Mar 2011 14:06:53 -0000

On Mar 16, 2011, at 6:12 AM, Kacheong Poon wrote:

> On 03/15/11 08:55 PM, Randy Stewart wrote:
> 
>> Resetting a stream then lets an app re-use it sort of like
>> ftp uses the closing of a connection to indicate that the
>> file transfer is complete.... I don't see thats a poor design
>> choice.
> 
> 
> I guess the question is whether the app layer cannot do
> it or the app layer cannot do it any better than in the
> transport layer.  To tell the other side that a transfer
> is complete in one stream does not require resetting SSN.
> For example, HTTP allows sending multiple files and it
> does not require resetting the TCP connection.


So you use a whole transport connection setup has a mechanism to
tell that something is complete. This is the same thing as ftp and
I think resetting a stream is a LOT less heavy weight....

> 
> 
>> So lets see .. what happens when I send more than 65,536 messages
>> as I re-use the stream say 10.000 times?
>> 
>> Or do we say no you may only send N messages where N = 65k/number-of-times you wish to
>> use it?
> 
> 
> I am not sure I understand the example above.  An app can
> send as many messages in a stream.  Using the file transfer
> example above, an app sends the whole file to the other
> side (number of messages does not matter here).  The app
> layer receives the whole file and it knows where it ends.
> After this, the next file is sent using the same stream.
> What is the reason that the SSN needs to be reset to 0 before
> sending the next file?

I can easily know that I close the file and when the stream
reset arrives. This tells me the transfer is done the same way
in ftp you use the closing of the connection as an indication that
the transfer is complete.

R



> 
> 
> -- 
> 
> 					K. Poon.
> 					ka-cheong.poon@oracle.com
> 

-----
Randall Stewart
randall@lakerest.net