Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Harald Alvestrand <harald@alvestrand.no> Thu, 18 April 2013 07:01 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 E618921F8EDA for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 00:01:49 -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 3MApImQO+bm3 for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 00:01:49 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 1F85921F8ED6 for <rtcweb@ietf.org>; Thu, 18 Apr 2013 00:01:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id DBB7639E0F0; Thu, 18 Apr 2013 09:01:47 +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 8ZWo-FcipGFH; Thu, 18 Apr 2013 09:01:47 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:8d75:2a83:3d29:f267] (unknown [IPv6:2001:470:de0a:27:8d75:2a83:3d29:f267]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 2159839E056; Thu, 18 Apr 2013 09:01:47 +0200 (CEST)
Message-ID: <516F9A5A.6080402@alvestrand.no>
Date: Thu, 18 Apr 2013 09:01:46 +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>
In-Reply-To: <CABkgnnVtUjk4jSDVioxQnrt-b69Hx0nZLefs7tpEzETSmLXeNA@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 07:01:50 -0000

On 04/18/2013 12:01 AM, Martin Thomson wrote:
> On 17 April 2013 14:58, Harald Alvestrand <harald@alvestrand.no> wrote:
>> I think I (on behalf of applications I'll be writing) am in the camp of "If
>> I asked to be told what the incoming data channel was (by not registering to
>> handle data without an OPEN), and didn't get told what it was, I don't want
>> the data".
>>
>> Perhaps provide a few buffers to handle packet reordering.
>> But beyond that: Throw the data away.
> 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.

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.)