Re: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Wed, 05 February 2014 21:47 UTC
Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 7936B1A011C for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.535, SPF_HELO_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 0K3wtZcgjyRn for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:47:40 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id F1F511A0101 for <rtcweb@ietf.org>; Wed, 5 Feb 2014 13:47:39 -0800 (PST)
Received: from [192.168.1.200] (p508F1F22.dip0.t-ipconnect.de [80.143.31.34]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id D0D981C0B4043; Wed, 5 Feb 2014 22:47:37 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826DFCD683@US70UWXCHMBA02.zam.alcatel-lucent.com>
Date: Wed, 05 Feb 2014 22:47:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFF06852-E7C6-4A9D-A15B-D79F45D24834@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D15BD1A@ESESSMB209.ericsson.se> <CAJrXDUGJO1C-47PmU7nwgRaZu19XTvsgwyq=6m=-vsL6LYqqLA@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD56D@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAJrXDUGtf4U_jhX1hmbPTtXQidR=oHL0cCrKCaZhnLsQd8NvLw@mail.gmail.com> <A9D7F81A-C0E6-44DF-AFC4-4AAB1E78DA19@lurchi.franken.de> <E1FE4C082A89A246A11D7F32A95A17826DFCD683@US70UWXCHMBA02.zam.alcatel-lucent.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1510)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing
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: Wed, 05 Feb 2014 21:47:42 -0000
On Feb 5, 2014, at 10:32 PM, "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> wrote: >>> I believe that Firefox is the browser that does that. At the last >>> IETF, I think we agreed that it's a temporary fix at best while we >>> wait until this problem is solved at the SCTP layer and not above it. > [Raju] Using NDATA I believe. > >>> >>> I'm not aware of any native clients that use this technique, unless >>> there are native clients that use Firefox's code. Perhaps there are; >>> I just don't know of any. >>> >>> In any case, it's not part of the standard, and I think the plan is >>> that it won't be needed long-term. >> As discussed in the last IETF meeting, this PPID based fragmentation and >> reassembly >> will be removed from the ID. > [Raju] Can I then assume the reason for such removal is the availability of NDATA (http://tools.ietf.org/html/draft-stewart-tsvwg-sctp-ndata-03) sooner than later, which will make such PPID based fragmentation/reassembly immediately obsolete? Right. The point was not to have two solutions, but use one. Best regards Michael > > [Raju] -Raju >
- [rtcweb] RTCWEB Data Channel: Usage of PPID for p… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Peter Thatcher
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Peter Thatcher
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Paul Kyzivat
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: message interle… Paul Kyzivat
- Re: [rtcweb] RTCWEB Data Channel: message interle… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: message interle… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: message interle… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: message interle… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: message interle… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: message interle… Paul Kyzivat
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Paul Kyzivat
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Harald Alvestrand
- Re: [rtcweb] RTCWEB Data Channel: message interle… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Michael Tuexen
- [rtcweb] PPID, UTF-16 and DOMString (Re: RTCWEB D… Harald Alvestrand
- Re: [rtcweb] RTCWEB Data Channel: message interle… Justin Uberti
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Christer Holmberg
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Martin Thomson
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Christer Holmberg
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Michael Tuexen
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Christer Holmberg
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Christer Holmberg
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Michael Tuexen
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Christer Holmberg
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Makaraju, Maridi Raju (Raju)
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Randell Jesup
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Michael Tuexen
- Re: [rtcweb] RTCWEB Data Channel: Usage of PPID f… Paul Kyzivat
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Harald Alvestrand
- Re: [rtcweb] PPID, UTF-16 and DOMString (Re: RTCW… Makaraju, Maridi Raju (Raju)