Re: [Tsvwg] SCTP stream EOF
Michael Tüxen <Michael.Tuexen@lurchi.franken.de> Wed, 17 September 2008 18:57 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 DD2093A6814; Wed, 17 Sep 2008 11:57:17 -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 5CF083A6765 for <tsvwg@core3.amsl.com>; Wed, 17 Sep 2008 11:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 oGh04NzPXcRN for <tsvwg@core3.amsl.com>; Wed, 17 Sep 2008 11:57:11 -0700 (PDT)
Received: from mail-n.franken.de (mail-n.franken.de [193.175.24.27]) by core3.amsl.com (Postfix) with ESMTP id 3FB923A6899 for <tsvwg@ietf.org>; Wed, 17 Sep 2008 11:57:11 -0700 (PDT)
Received: from [IPv6:2002:508f:c56f::21e:c2ff:fe00:76c8] (unknown [IPv6:2002:508f:c56f:0:21e:c2ff:fe00:76c8]) by mail-n.franken.de (Postfix) with ESMTP id 224AB1C0C0BEA; Wed, 17 Sep 2008 20:57:22 +0200 (CEST)
Message-Id: <96742FCA-CF4C-4EAB-AD38-84B7CFB1AAD9@lurchi.franken.de>
From: Michael Tüxen <Michael.Tuexen@lurchi.franken.de>
To: Randy Stewart <randall@lakerest.net>
In-Reply-To: <D914D831-188B-4194-835F-E2A6EDD495B3@lakerest.net>
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 20:57:20 +0200
References: <48D10AD3.10307@student.uibk.ac.at> <D914D831-188B-4194-835F-E2A6EDD495B3@lakerest.net>
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
On Sep 17, 2008, at 4:40 PM, Randy Stewart wrote: > 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.... Just provide a notification that the stream is reset... > > > 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 No we haven't. And that should go into the stream reset ID. > > the Stream-Reset serves the purpose you are looking for. ACK. > > > 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