IETF Logo Mail Archive

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

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Wed, 05 February 2014 21:32 UTC

Return-Path: <Raju.Makaraju@alcatel-lucent.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 428301A0223 for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 T8MUT-LROAbr for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:32:50 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3641A0211 for <rtcweb@ietf.org>; Wed, 5 Feb 2014 13:32:50 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s15LWlPv023074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 5 Feb 2014 15:32:48 -0600 (CST)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id s15LWk36005902 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Feb 2014 16:32:47 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.212]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.02.0247.003; Wed, 5 Feb 2014 16:32:46 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, Peter Thatcher <pthatcher@google.com>
Thread-Topic: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing
Thread-Index: AQHPIrbvBV3Y4lbqJU6LVDbjTFGdqpqnLPhQ
Date: Wed, 05 Feb 2014 21:32:46 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826DFCD683@US70UWXCHMBA02.zam.alcatel-lucent.com>
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>
In-Reply-To: <A9D7F81A-C0E6-44DF-AFC4-4AAB1E78DA19@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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:32:52 -0000

> > 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?

[Raju] -Raju

v2.23.0 | Report a Bug | By Email