Re: [Tsvwg] SCTP stream EOF
Randy Stewart <randall@lakerest.net> Wed, 17 September 2008 14:40 UTC
Return-Path: <tsvwg-bounces@ietf.org>
X-Original-To: tsvwg-archive@optimus.ietf.org
Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 245203A682D; Wed, 17 Sep 2008 07:40:13 -0700 (PDT)
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 31FEC3A679C for <tsvwg@core3.amsl.com>; Wed, 17 Sep 2008 07:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 F2EIeAyzCare for <tsvwg@core3.amsl.com>; Wed, 17 Sep 2008 07:40:08 -0700 (PDT)
Received: from lakerest.net (unknown [IPv6:2001:240:585:2:203:6dff:fe1a:4ddc]) by core3.amsl.com (Postfix) with ESMTP id 9BC383A682D for <tsvwg@ietf.org>; Wed, 17 Sep 2008 07:40:07 -0700 (PDT)
Received: from [10.1.1.54] ([10.1.1.54]) (authenticated bits=0) by lakerest.net (8.14.1/8.14.1) with ESMTP id m8HEeHE3053087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 17 Sep 2008 10:40:17 -0400 (EDT) (envelope-from randall@lakerest.net)
DKIM-Signature: a=rsa-sha1; c=simple/simple; d=lakerest.net; s=mail; t=1221662417; h=Cc:Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: X-Mailer; b=N/PxXRn+TVbjpTtU58+Q53ENYU97j9hC6xCtMdzESk5m6QamovSREHV ZG04QnvqVZ+6eFlynft3kBqYpMK5B8Q==
Message-Id: <D914D831-188B-4194-835F-E2A6EDD495B3@lakerest.net>
From: Randy Stewart <randall@lakerest.net>
To: Florian Niederbacher <florian.niederbacher@student.uibk.ac.at>
In-Reply-To: <48D10AD3.10307@student.uibk.ac.at>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 17 Sep 2008 10:40:16 -0400
References: <48D10AD3.10307@student.uibk.ac.at>
X-Mailer: Apple Mail (2.929.2)
Cc: tsvwg@ietf.org
Subject: Re: [Tsvwg] SCTP stream EOF
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: <https://www.ietf.org/mailman/private/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>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
Florian: What do you mean by an EOF? For messages there is a SCTP_EOR to tell you a "message" as ended. If you were using stream reset, and the peer decides to "reset" a stream and then use the stream for some other purpose (this is what I think you are stating).... then the user would get a STREAM_RESET event for that stream. I don't see the difference (other than name) in stream-x has been reset vs stream X receives a EOF. Note that an app MAY choose to use a RESET as a EOF.. but it can also mean something different to an app.. I am done sending this type of message, I will now send other types of messages. Which is different than an EOF.... Note also that the socket-api section is still missing (if I remember right) from the stream-reconfig draft... I do need to add this. But I really think the Stream-Reset serves the purpose you are looking for. R On Sep 17, 2008, at 9:49 AM, Florian Niederbacher wrote: > Hi, > I would ask what are you thinking about a definition for an EOF on > streams in SCTP. My problem is that I would need a signaling method > to report an EOF without closing the whole SCTP association. If I am > right, socket connections get only an EOF if the connection will be > closed (no sending of EOF on socktes in another way is possible). In > draft-stewart-tsvwg-sctpstrrst-00 the possibility the reset of > streams is discussed. This would also be a solution if you can check > the numbering sequence in User Space. > A proposal would be to generate an SCTP_EVENT e.g. SCTP_STREAM_EOF > to signal EOF on streams. In this way you can stop receiving and > also reuse the stream or at least continue in multi-streamed network > applications, if you use different threads or processes for the > receiving procedure on streams. Maybe an other possibility exists to > signal an EOF on SCTP streams, but at the moment I can't find any > solution to deal with this problem. What are your proposals and > comments? > > Best regards > Florian Niederbacher ----- Randall Stewart randall@lakerest.net
- [Tsvwg] SCTP stream EOF Florian Niederbacher
- Re: [Tsvwg] SCTP stream EOF Randy Stewart
- Re: [Tsvwg] SCTP stream EOF Florian Niederbacher
- Re: [Tsvwg] SCTP stream EOF Michael Tüxen
- Re: [Tsvwg] SCTP stream EOF Michael Tüxen
- Re: [Tsvwg] SCTP stream EOF Randy Stewart
- Re: [Tsvwg] SCTP stream EOF Florian Niederbacher
- Re: [Tsvwg] SCTP stream EOF Michael Tüxen