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

Peter Thatcher <pthatcher@google.com> Wed, 05 February 2014 21:10 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 777981A020A for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:10:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.914
X-Spam-Level:
X-Spam-Status: No, score=-1.914 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, RP_MATCHES_RCVD=-0.535, 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 99Xp9ybgNxr5 for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:10:20 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B72191A01FC for <rtcweb@ietf.org>; Wed, 5 Feb 2014 13:10:20 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id kp14so837267pab.20 for <rtcweb@ietf.org>; Wed, 05 Feb 2014 13:10:20 -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=Q0rK9CBTYt5VYFXbk1eN9LUnva+Qpxwc8UrRZOCdxOs=; b=lp0Br0KyMLZD06tmRVNBfF0SzFODGLdrBuATpb4Cgsk/oXMVYnvIoYzD45j03ydbwN wFSyotANIUiSdW1NH3r649gu8EPz4kUO5JXpnmxB1brPYHaQXghxBRmGKCfhIf9YbNib GWUXA4H8UC7y3KApjIVtCMM4SXrHi6Ltms8W+P/HV24JNFeq180TCr+7gPQu+xxTVEoG Uglt11wB7Q0beGbSr0ZyssLSvXxN3Cd76a9YNr+kAqdsvwIxxF5GGNqh098NC7fc7weB sjLNg3566zht8WtY4APVPkElRWr5BzlvpIi9dnpO2YaeQsx6zglVECak8hh6+bcv9goy +wFQ==
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=Q0rK9CBTYt5VYFXbk1eN9LUnva+Qpxwc8UrRZOCdxOs=; b=jJd3xxsEtNW7QWYzehQKwHuh2v1hsFJJwr+KslfdHfdOMqVWoBmK/rjzVm9ll8Fv0B XmVofmMEDkkqjZKKePH/p9/qbENbYHn1R0nMUO7z63HGlcCzUn6LRr6QI12WvaSTi1H2 Re0FLWoeHr436jdRmRnjXo70865dDf5UnAV+GfSlpb8kez9d3NRnoNSlPh2s1BxMrfS/ QijogIjB3YTO+qVHLdrMLj7YAWPlQBMRgbjo8SKa87LQw83SaWbjNDZuf5mCsbhZpG9w whn+rfbKovyrhZIh98Pb90/4TP8N4A1T0aL7KSDRW7SYM+W35Ekjidf8+i5sbVu3vLxJ uyXQ==
X-Gm-Message-State: ALoCoQnCzIxpGLpXIlnnNMn8sMcWzeC1GgCoP6CpcpYP+qq6KUEPDrCUQcuZhzh1eORbKjm8joGi6g01luI292viUSlFf3jPih4fQZvywIN3j9pNq72AcmmJAeLF5inCsvUm8G0MIhC7wYm+WQ/+7qof35Pi5Cq3xevMjjF3OkG4XZeK8PMcWu3dTgwqMVYup9wNyf2TshR3
X-Received: by 10.69.20.139 with SMTP id hc11mr5380167pbd.63.1391634619605; Wed, 05 Feb 2014 13:10:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.163.234 with HTTP; Wed, 5 Feb 2014 13:09:39 -0800 (PST)
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826DFCD56D@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D15BD1A@ESESSMB209.ericsson.se> <CAJrXDUGJO1C-47PmU7nwgRaZu19XTvsgwyq=6m=-vsL6LYqqLA@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD56D@US70UWXCHMBA02.zam.alcatel-lucent.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 05 Feb 2014 13:09:39 -0800
Message-ID: <CAJrXDUGtf4U_jhX1hmbPTtXQidR=oHL0cCrKCaZhnLsQd8NvLw@mail.gmail.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
Content-Type: text/plain; charset="UTF-8"
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:10:24 -0000

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.

>
> -Raju
>