Re: [rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK
Peter Thatcher <pthatcher@google.com> Mon, 10 February 2014 20:05 UTC
Return-Path: <pthatcher@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7328D1A089E for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 12:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PIcm4m_rJtrG for <rtcweb@ietfa.amsl.com>; Mon, 10 Feb 2014 12:05:18 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id D28521A0882 for <rtcweb@ietf.org>; Mon, 10 Feb 2014 12:05:18 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id fa1so6672419pad.28 for <rtcweb@ietf.org>; Mon, 10 Feb 2014 12:05:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5YoLpZj3aJoFoTr8v1MV2fyB9F4RzcVBs2ZHzfo8+Oo=; b=CCLWzXV5hfOHzdqHDmAIZyMHGwyud1qOHR9ammb0dBfLSTZq5A4w8+w6Ks23YJAbvZ BAe0qmv0Y5j3H6L4Xn+b+mAJEL0rQUcOILuBgu3aq6f9dseyhsRtNa28lqZWCMK5kwpy sOUSvJXSXklYotJUiMxGL6o5LP/UfTq2dzbYEwIW9P1QsXTv9ytrKIbAeZDySGP2jB9X 4RaEhA/PBfHDlG09vxWcH5umXpOVlvZ7cv630HH/mpeKr0bQggwJ/+nvMcRahKstQ7py GSDk94b8w+c1eLbJCoHCZSSR0aDmy15xoBDIYXcgdvSpLjV608FFX61U4vQrqf4Y+n7i CCYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=5YoLpZj3aJoFoTr8v1MV2fyB9F4RzcVBs2ZHzfo8+Oo=; b=mPy9Tgz7o6w7ztiWdjJpn5nbCnCyU07jPl5sgrzwhe44tmG5LBZ40YErFCYZGumK48 EakI0VEjZ3sQznh13k2wzDtkFicyWnRKfSsDqdgZBdRDQjGEGKjap8Kqqi1atWnT0i3z Wd4FB2IXIQN9nrevrZsJEwFO94Z7r+cDQKoX7XOYEyE3mtjF4xnReYYtgUHj1uDQabQH dV56xFtABbbDhnsOjiHVRLli7mUDnlc0/+AQeNeYm8ic60Es3mNQP9WDTilkI6eGBK0U P9ZJUExn3LhqFqlObosq8y6+8sTKVM+E7ukGVEl0ctt+Yinom7gbf0SZz5U4quqGCm6J m5gA==
X-Gm-Message-State: ALoCoQkt+QMDM0x1L4mYiGJeVi6PTjY2vOiP1/S/cu8/o6SCq6/35JmgftAR7mBdyjYrSHDKQOE6LpeSeApgGNJg4jdmQCRRSpUFeHksxNAhZXSgiRGuS/4NN1czdwv/Q2tIkx6K9RQ23aHcg7BrfvtYwQnQonPAz4VRQ/7tBVX0xpVibQJ/XOAyyLf5mDz9CGxaWJsMulix
X-Received: by 10.66.150.69 with SMTP id ug5mr27721305pab.55.1392062718644; Mon, 10 Feb 2014 12:05:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.163.234 with HTTP; Mon, 10 Feb 2014 12:04:38 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D167CCE@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D166D41@ESESSMB209.ericsson.se> <CAJrXDUHBBt6L7tp4Ck426xQEkAQEmOnscmu2mBFUGR8YVHqoaw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D167CCE@ESESSMB209.ericsson.se>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 10 Feb 2014 12:04:38 -0800
Message-ID: <CAJrXDUHVkcKWwmYmpZSyfaikq2shQwWUmOiBDPN=NPQJigDAnw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7b6dc31ed9aa4404f212db59"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Data Channel Protocol: Data before DATA_CHANNEL_ACK
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 10 Feb 2014 20:05:21 -0000
On Mon, Feb 10, 2014 at 11:55 AM, Christer Holmberg < christer.holmberg@ericsson.com> wrote: > Hi Peter, > > > If you have to wait for the ACK, it's one more RTT you have to wait > before you can send data. We've already > > got many RTTs form ICE and DTLS and what's built into SCTP. We > originally didn't have an ACK message at all, in > > large part because we didn't want more RTTs. The ACK was put in to > handle the edge case of unordered data arriving > > before the OPEN message. But we added it in a way that it doesn't add > more RTTs. > > But, you may not even know whether I support the protocol you are sending. > What should I do if I don't like/support what you send? > > The signalling is up to the application to define. If your application wants to send a message from the receiver to the sender saying "I support X" or "please send me X", then by all means add that to your application, and don't call channel.send() until the sender knows it should send. > I think it would be useful to have a REJ message, so that I can explicitly > tell you that I don't want what you send - rather than me reseting the > stream, or me not sending an ACK and hope that you will eventually stop > sending data. > The signalling is up to the application to define. If your application wants to send a message from the receiver to the sender saying "I don't support X" or "please don't send me X", then by all means add that to your application, and don't call channel.send() if the receiver says it doesn't want the message. I think what is already in the standard is sufficient for your use case. You just need to add a little application-specific signalling. I don't think the in-band signalling is the right place to put things like this. > > Regards, > > Christer > >
- [rtcweb] Data Channel Protocol: Data before DATA_… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Peter Thatcher
- Re: [rtcweb] Data Channel Protocol: Data before D… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Peter Thatcher
- Re: [rtcweb] Data Channel Protocol: Data before D… Christer Holmberg
- Re: [rtcweb] Data Channel Protocol: Data before D… Michael Tuexen
- Re: [rtcweb] Data Channel Protocol: Data before D… Randell Jesup