Re: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Wed, 05 February 2014 21:11 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 A897D1A01FC for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:11:55 -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 RT173EYNwtyY for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:11:53 -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 DA72F1A01CC for <rtcweb@ietf.org>; Wed, 5 Feb 2014 13:11:52 -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 7C68D1C0B3006; Wed, 5 Feb 2014 22:11:49 +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: <CAJrXDUGtf4U_jhX1hmbPTtXQidR=oHL0cCrKCaZhnLsQd8NvLw@mail.gmail.com>
Date: Wed, 05 Feb 2014 22:11:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9D7F81A-C0E6-44DF-AFC4-4AAB1E78DA19@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>
To: Peter Thatcher <pthatcher@google.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:11:55 -0000

On Feb 5, 2014, at 10:09 PM, Peter Thatcher <pthatcher@google.com> wrote:

> On Wed, Feb 5, 2014 at 12:40 PM, Makaraju, Maridi Raju (Raju)
> <Raju.Makaraju@alcatel-lucent.com> wrote:
>>> The PPID isn't exposed to the application.  It's just used to
>>> distinguish text/binary/control.    If an application uses different
>>> data channels with different protocols, it should use the SID to
>>> distinguish between them, not the PPID.  In fact, even if it wanted to
>>> use the PPID, it wouldn't be able to.
>> [Raju] PPID is also used by browsers (and other webrtc implementors like native clients) to fragment user given large data into smaller fragments (via "XYZ partial", "XYZ last" PPIDs) to avoid monopolizing the SCTP link for a single data channel's data.
>> See http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-06#section-6.6 for more details.
> 
> 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.
> 
> 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.

Best regards
Michael
> 
>> 
>> -Raju
>> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>