IETF Logo Mail Archive

Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Thu, 18 April 2013 18:23 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1701E21E803F for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 11:23:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXVS25W3ZfGk for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 11:23:13 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id C7DD021E803C for <rtcweb@ietf.org>; Thu, 18 Apr 2013 11:23:12 -0700 (PDT)
Received: from [192.168.1.102] (p548186C1.dip0.t-ipconnect.de [84.129.134.193]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 673451C0C069F; Thu, 18 Apr 2013 20:23:06 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5170247F.4090908@alvestrand.no>
Date: Thu, 18 Apr 2013 20:23:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BE3772E-AD2B-4F09-B4BC-2FEFB5787EEF@lurchi.franken.de>
References: <066.3120a55540cacaa74ee5fda0b5273a48@trac.tools.ietf.org> <516CE3EC.2050804@jesup.org> <CABkgnnVaTOLa-hs7AtEgaTk7eq00bEkCY+_8L96Y8pooqybBxA@mail.gmail.com> <CAJrXDUFgxLT3-1HehKbg5byzifFi4Obe3XW9G4sbWRbnU+Hi1A@mail.gmail.com> <CABkgnnXr85LZyJiSF+ok2KMS_xQnS0CE4VBq4PvEhBBscn2QZQ@mail.gmail.com> <516F1AF9.2080301@alvestrand.no> <CABkgnnVtUjk4jSDVioxQnrt-b69Hx0nZLefs7tpEzETSmLXeNA@mail.gmail.com> <516F9A5A.6080402@alvestrand.no> <CABkgnnWrAMnm5fTWCNA1jqC_8Js0a6ewfSkvni4xg0E6rXdCtA@mail.gmail.com> <5170247F.4090908@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1283)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2013 18:23:14 -0000

On Apr 18, 2013, at 6:51 PM, Harald Alvestrand wrote:

> On 04/18/2013 06:03 PM, Martin Thomson wrote:
>> On 18 April 2013 00:01, Harald Alvestrand <harald@alvestrand.no> wrote:
>>>> What if the data is ordered?  Couldn't the data you actually get
>>>> depend on the data that got discarded?
>>> If the data is required to be delivered in-order, it can't be delivered
>>> before the (in-order) OPEN packet I'm waiting for anyway, so the problem
>>> cannot occur.
>> Of course.
>> 
>>> The problem can occur if data can be sent reliably, but without ordering.
>>> 
>>> I'm willing to consider the option of saying that "throw the data away"
>>> means "report to the sender that this data channel closed with an error".
>>> It's even reasonably correct; what the sender expected to happen did not
>>> happen.
>>> 
>>> (The receiver will never know that a data channel was attempted. It never
>>> opened.)
>> In that case we'd have to reset the stream.  Maybe our SCTP experts
>> can advise on whether we could make that look like something other
>> than a normal close.
> 
> Yep, "reset the stream" is probably the right terminology.
I think just dropping messages without any indication that something went wrong should
be avoided. Closing the channel by resetting the streams is an option.

Best regards
Michael
> 
> Sounds good to me.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email