IETF Logo Mail Archive

Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Martin Thomson <martin.thomson@gmail.com> Thu, 18 April 2013 16:04 UTC

Return-Path: <martin.thomson@gmail.com>
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 C4AC721F8CF0 for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 09:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 3RpU9daFn+L5 for <rtcweb@ietfa.amsl.com>; Thu, 18 Apr 2013 09:04:01 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 52B1921F8CE9 for <rtcweb@ietf.org>; Thu, 18 Apr 2013 09:04:00 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id ec20so2724109lab.13 for <rtcweb@ietf.org>; Thu, 18 Apr 2013 09:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=F+l7LOLtSsyqowMFrvLtWxIxqFYqR2R4CVwEMYBxh+w=; b=eHl2qwAhSxd3JRtJSHKaXFYcjUUetlVfkylE9SH0b0ChUOJ90U8cck2FDMsF9YFx4T 8tjZfgf5/b7wphvoMpeXkGfVX/YSnJFcKB499RWUr8uu+UY66hqkdvX0xelL21FsV2MH 7qWj200EFM/v06g7yRmhDDMOCj7xvB5CD9qxki0H5qHzpK6kTwbhj9A6kxD5ji/tmNwn j4Nw11ZnMZ8DSWa5qpatjJaL5YRbD22+7rol/CjWEfqK8lNrqzqAvPWGz32tkHUnCYgJ ynvmvoUAJq7jaYnoGcQpHqw6b00onLMXjCGe5nZXgvpEmRaMBeKTKoIJ0xHzR0dJ4K8o 7Ahw==
MIME-Version: 1.0
X-Received: by 10.112.140.1 with SMTP id rc1mr6228800lbb.43.1366301039308; Thu, 18 Apr 2013 09:03:59 -0700 (PDT)
Received: by 10.112.6.67 with HTTP; Thu, 18 Apr 2013 09:03:59 -0700 (PDT)
In-Reply-To: <516F9A5A.6080402@alvestrand.no>
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>
Date: Thu, 18 Apr 2013 09:03:59 -0700
Message-ID: <CABkgnnWrAMnm5fTWCNA1jqC_8Js0a6ewfSkvni4xg0E6rXdCtA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
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:04:01 -0000

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.

v2.23.0 | Report a Bug | By Email