IETF Logo Mail Archive

Re: [rtcweb] Sending of zero-length messages over data channels

Justin Uberti <juberti@google.com> Thu, 24 July 2014 19:28 UTC

Return-Path: <juberti@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 48E331B280E for <rtcweb@ietfa.amsl.com>; Thu, 24 Jul 2014 12:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 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.001, SPF_PASS=-0.001] autolearn=no
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 PO8yFn7QVbKF for <rtcweb@ietfa.amsl.com>; Thu, 24 Jul 2014 12:28:19 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF2871B27F9 for <rtcweb@ietf.org>; Thu, 24 Jul 2014 12:28:18 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hu12so5715971vcb.20 for <rtcweb@ietf.org>; Thu, 24 Jul 2014 12:28:17 -0700 (PDT)
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=VAdn+CMDhCyGPEeCyqBB97W5+ralRlndNoFenViq0/Y=; b=GCF7MM3dQKC6Z3er5vmpzj7UAQwl3qBc7160LNKRjNvSYysfTF1hSv5jZIVGvuEEWf NCsG1gnkev1fMwnRazQx4weHgbRibxeU6TFz4y3DHm1MCYTPVm7Y0RAIaNPd/Z5IAGJ7 c0vK2lABAPxl5C0bc1gFuZwpwldS3dA2nDw44pMV0gw1L5mqLYxczP+opXGDKrjl+a5K wioFZGQvGmIc7PFkj5KzPjUuYQLMg5oF3xKttna+6X7653wDDPRmfmnH1Vo06faiHasw cqBFN41gdwMu4mI8udvUzHb+P7A8VGLvuEzSBhK8O5ZZFm6x8PQ1euOwDnX4POAvX1FS DVwg==
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=VAdn+CMDhCyGPEeCyqBB97W5+ralRlndNoFenViq0/Y=; b=ZYN7MzX9wNK6AqT1Wv2jbqZyckKEDAlgcpLsjpYP9j5BA+2t9bNMhls/QKHqzY2Rqa pj14KTzOPHsZyA8oD4tiBmHN1GeLyS1T3QTbJnFpoZQZI21dOx6fM2wEB2DOZ4YC5Ew5 Hb6RxfqJvGAnp1ZZvXNdDM7VIuXDgSUleakAzbjhKHABGU2ygoX3glYuHgoVWNkxh5e3 sRrzO5YcGWI7OAtsXPtlvBM0rxu6+02qHfYjs3aTGh2nJiFdguSi+Sq4Izrd+2e7nt6t WYa7RbmCHrdIyb4zMK7wPL8Ijksny1KVVeqq2T0i1KAFi0lV3IMOe36gkuF5+onfUHcx 1O3g==
X-Gm-Message-State: ALoCoQnPH9SO26/6m/P53s0xNP7DT82gYrrzYyx/JVHV9AEpe3PMpxJ2AowDB6VPoQX18Bf3AYo6
X-Received: by 10.220.49.10 with SMTP id t10mr15712569vcf.34.1406230095957; Thu, 24 Jul 2014 12:28:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.4.70 with HTTP; Thu, 24 Jul 2014 12:27:55 -0700 (PDT)
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E4C5E94@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <CAOJ7v-0F9pysYLehjTVDv1Sxz3TKaxi2y6J7RrpGqMdA=tiR_g@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E4BCC13@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAOJ7v-1r-vToAf-rUfZmKsBC4MX4ZXUcAkqahrskF1D3axOpuA@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E4C5974@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAOJ7v-1VPP8iAz+gr9h98QUzZnBVna84yPqtc0JZR=ehGgJL0A@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E4C5E94@US70UWXCHMBA02.zam.alcatel-lucent.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 24 Jul 2014 15:27:55 -0400
Message-ID: <CAOJ7v-2SkB3Pqctpu1S_wMY2b6jdOYyz8KxAYLA-q++2WdUbYw@mail.gmail.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="089e0163412c57b47404fef575a4"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/efEfS2xW8M3bBeZp3oleQMp9r9A
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Sending of zero-length messages over data channels
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: Thu, 24 Jul 2014 19:28:20 -0000

On Thu, Jul 24, 2014 at 3:19 PM, Makaraju, Maridi Raju (Raju) <
Raju.Makaraju@alcatel-lucent.com> wrote:

>     >We will send 1 byte, and this will not be reflected in
> bufferedAmount, same as WebSockets.
>
> *<Raju> I could be wrong, but I am not sure how 1 dummy byte can be sent
> over Websockets?! I do not see any special frame type defined at
> http://www.iana.org/assignments/websocket/websocket.xml
> <http://www.iana.org/assignments/websocket/websocket.xml> for this dummy
> byte purpose; without that how does the other end know to ignore it? My
> understanding is Websocket protocol allows zero-length frames by default.*
>
> *Also, the webkit bug fix for websocket*
> https://bugs.webkit.org/show_bug.cgi?id=65592 *talks about handling zero
> length payload as opposed to sending a dummy byte.*
>
>
>
> *In conclusion, I think websocket API supports zero length because
> websocket protocol supports zero-length data frames. So, it does not have
> the issue of ‘bufferedAmount’ discrepancy. *
>
>
>

Yes, that is what I meant.

v2.23.0 | Report a Bug | By Email