IETF Logo Mail Archive

Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Harald Alvestrand <harald@alvestrand.no> Thu, 18 April 2013 16:51 UTC

Return-Path: <harald@alvestrand.no>
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 2599421F8F06 for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 09:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 uTTIOiiCdOp8 for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 09:51:13 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 802FF21F8EEC for <rtcweb@ietf.org>; Thu, 18 Apr 2013 09:51:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4EC0F39E12F; Thu, 18 Apr 2013 18:51:12 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w5V2SIfwErHN; Thu, 18 Apr 2013 18:51:11 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:d42:6e2d:d108:3324] (unknown [IPv6:2001:470:de0a:27:d42:6e2d:d108:3324]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 8F0F639E0F0; Thu, 18 Apr 2013 18:51:11 +0200 (CEST)
Message-ID: <5170247F.4090908@alvestrand.no>
Date: Thu, 18 Apr 2013 18:51:11 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
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>
In-Reply-To: <CABkgnnWrAMnm5fTWCNA1jqC_8Js0a6ewfSkvni4xg0E6rXdCtA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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 16:51:14 -0000

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.

Sounds good to me.

v2.23.0 | Report a Bug | By Email