IETF Logo Mail Archive

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

Harald Alvestrand <harald@alvestrand.no> Mon, 04 August 2014 20:45 UTC

Return-Path: <harald@alvestrand.no>
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 9D9621A030C for <rtcweb@ietfa.amsl.com>; Mon, 4 Aug 2014 13:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-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 QjJyqfG_eQpP for <rtcweb@ietfa.amsl.com>; Mon, 4 Aug 2014 13:45:08 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 820FB1A033C for <rtcweb@ietf.org>; Mon, 4 Aug 2014 13:44:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 5E90F7C3E8D; Mon, 4 Aug 2014 22:44:58 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZQhJPSTL5ch; Mon, 4 Aug 2014 22:44:57 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:99e6:15c8:36c3:4395] (unknown [IPv6:2001:470:de0a:27:99e6:15c8:36c3:4395]) by mork.alvestrand.no (Postfix) with ESMTPSA id 72C587C3E88; Mon, 4 Aug 2014 22:44:57 +0200 (CEST)
Message-ID: <53DFF0C8.7000604@alvestrand.no>
Date: Mon, 04 Aug 2014 22:44:56 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
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> <CAOJ7v-2SkB3Pqctpu1S_wMY2b6jdOYyz8KxAYLA-q++2WdUbYw@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E4C61A5@US70UWXCHMBA02.zam.alcatel-lucent.com> <53DDFEC1.3020907@alvestrand.no> <E1FE4C082A89A246A11D7F32A95A17828E4EC8B4@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E4EC8B4@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------020203080203050204080903"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/L7wgBBapm7ODMDKbgmX_raTaELQ
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: Mon, 04 Aug 2014 20:45:19 -0000

Not responding to rest of message.

On 08/04/2014 08:08 PM, Makaraju, Maridi Raju (Raju) wrote:
>
> */>PPID_OOB would make the compatibility problem worse, not better./*
> */<Raju2>/*
>
> */I would appreciate if you can provide reasons on why PPID_OOB making 
> compatibility worse?/*
>

Because WebSockets doesn't have any functionality corresponding to PPID_OOB.

Adding more functions that WebSockets doesn't have makes compatibility 
with WebSockets worse.

v2.23.0 | Report a Bug | By Email