IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 05 February 2014 21:59 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 97A9B1A0129 for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 orMNuz6qZ3uo for <rtcweb@ietfa.amsl.com>; Wed, 5 Feb 2014 13:59:52 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 865701A012F for <rtcweb@ietf.org>; Wed, 5 Feb 2014 13:59:52 -0800 (PST)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta13.westchester.pa.mail.comcast.net with comcast id Nd1k1n0021YDfWL5Dlzrri; Wed, 05 Feb 2014 21:59:51 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id Nlzr1n00P3ZTu2S3glzr2z; Wed, 05 Feb 2014 21:59:51 +0000
Message-ID: <52F2B457.8040305@alum.mit.edu>
Date: Wed, 05 Feb 2014 16:59:51 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
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> <CFF06852-E7C6-4A9D-A15B-D79F45D24834@lurchi.franken.de>
In-Reply-To: <CFF06852-E7C6-4A9D-A15B-D79F45D24834@lurchi.franken.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391637591; bh=0ZGQ3q779J3FC4yWUCztWpQj7SLnbv9s2oT/BSXB3Kk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=iN87rV5Sq6WF/RTj8xqZobqRzCrDGp1hAL4HfiFtBkjTx+cjEtwXObP7oNGXV/wej HcU0HCFco6bMLk6tZbm2YZtq5bB31l+hbTVK5f2lsGQbY+laQZE5DsXWEMIxG+9gMb VlvZBZY6b7KQHHPdWq75WsiG3VIrkBjeWnIyhOTuILMZ1antZHxHRxiD5VKUstpT/e WcEGYO1gyxDE5BXF6L90S7HY1IlvdFAsNO6PCOGUrnNMEDutC6lBbt7rXoONb/VwkO kFi3tTj20Ke9IMa5qh7YODCkvPY48pVl1JgCTmU161Spmrn84Utp7wrhaSIyihvTk0 aTxNOZ3Ohp10A==
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:59:53 -0000

Will NDATA support be required for rtcweb?

	Thanks,
	Paul

On 2/5/14 4:47 PM, Michael Tuexen wrote:
> 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 mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email