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

Peter Thatcher <pthatcher@google.com> Wed, 05 February 2014 18:40 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 4894C1A0140 for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 10:40:36 -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 qInAPbw1dH3e for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 10:40:34 -0800 (PST)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 51F1F1A0138 for <rtcweb@ietf.org>; Wed, 5 Feb 2014 10:40:34 -0800 (PST)
Received: by mail-pb0-f42.google.com with SMTP id jt11so720549pbb.29 for <rtcweb@ietf.org>; Wed, 05 Feb 2014 10:40:33 -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:content-transfer-encoding; bh=5sQPrPycpJfZYkjG4ug/ERdvpNb1+BFmQw2BxPkgi9E=; b=GKEH6Nl+WD8pHye8nHch2Vyoggp+6bq3QoxZ88l+I6xkZ7hiaH3CrRk7Dv7j35q0rD bHgAYYiLRw+vHuafOPzHakX7uUXkPK2bNTUQUYolCzSgNoGvqZJRTgzHe0KzLvgcRFQK 69w9NGmN6MRn7c6YOkrBFrzo9RlL++TjX6CRQPQfGwjNNmDWSxYVFZZruA6KUrs1zoCq stAZTOhoPHd5plxkdNzUsZO0RiUFbNmQmt7IW0Swsut5we/iBMMcAi9XT2C6JfFdxq7a R7EHLFXg/PyVFgjHhyDPUEqw5MtDmHP/opHJXI4iZjI2sny+mjktkWpHjcX7JBt6Mo+M 4N7g==
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:content-transfer-encoding; bh=5sQPrPycpJfZYkjG4ug/ERdvpNb1+BFmQw2BxPkgi9E=; b=Aaax3Ofr8Z30t7hqq/OfIrXRT1yun0KWboPepqCZT+RXIIYUUZO2FeDXbAdT9IGFmu TYyx9XcEEWAJ9cLn8SqN9poOooufj8PsAEXHHSnMcmgenYCiJv53jx2neeL258teFs6C A1eqsMgVr/Gvn/tAhd1AZjsM9Uz00RUuRrimiF0X9IQd8wVTtu8gDp0jqBkvuSKBT0xi nYbXA1mgilIDozKHPgfMwO0LorbjsnBZaD5vtH7lvkesLN/qBj9lzUnYt5cqNytK+q6d XmU/dg+M0qvR1UuRGMOs4+RIaK0PJGBXfa+4rICaIURiqmtBWRYCLUds89769KLI53ib 8DuQ==
X-Gm-Message-State: ALoCoQkLZN00Q3PkXvotcp3mSUB02YDREStLtciBew6qu6Io0ImBxoFEH1TI37jqCQm05nx0/qXpGRAwPfe7kl9oOnzSuYcRx87AIurjipWucCQ9Svyf50VVJQm0jwDff7OpVz8VVelpBa2nhygSZDTKFyL5U3xL/w/w9OKa5b0J9cruiihNUTCsml1RMC1VwZoSWQM+xJf+
X-Received: by 10.68.111.65 with SMTP id ig1mr4188677pbb.3.1391625633630; Wed, 05 Feb 2014 10:40:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.66.163.234 with HTTP; Wed, 5 Feb 2014 10:39:53 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D15BD1A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D15BD1A@ESESSMB209.ericsson.se>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 05 Feb 2014 10:39:53 -0800
Message-ID: <CAJrXDUGJO1C-47PmU7nwgRaZu19XTvsgwyq=6m=-vsL6LYqqLA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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 18:40:36 -0000

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.

On Wed, Feb 5, 2014 at 3:23 AM, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Hi,
>
>
>
> This is related to the e-mail Paul sent yesterday (Data Channel question:
> correlating streams with channels).
>
>
>
> Section 5 of draft-ietf-rtcweb-data-channel-06 says:
>
>
>
> “Each SCTP user message contains a so called Payload Protocol
>
>                 Identifier (PPID) that is passed to SCTP by its upper layer
> and sent
>
>                 to its peer.  This value can be used to multiplex multiple
> protocols
>
>                 over a single SCTP association.  The sender provides for
> each
>
>                 protocol a specific PPID and the receiver can demultiplex
> the
>
>                 messages based on the received PPID.”
>
>
>
> Now, when I look at the IANA registration page for PPID values, most seem to
> be associated with specific protocols.
>
>
>
> However, if I e.g. use PPID values 51-54 (as rtcweb applications will do)
> they don’t say anything about the protocol. They refer to an encoding
> format, and multiple protocols may have the same format.
>
>
>
> I would assume that the SCTP stream id would have to be used to multiplex
> protocols.
>
>
>
> Regards,
>
>
>
> Christer
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>