IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 06 February 2014 16:26 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 13B7C1A03E2 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 08:26:16 -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 MtRBinFJew0E for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 08:26:15 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 20C071A017B for <rtcweb@ietf.org>; Thu, 6 Feb 2014 08:26:15 -0800 (PST)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta12.westchester.pa.mail.comcast.net with comcast id P0l51n0040Fqzac5C4SEYW; Thu, 06 Feb 2014 16:26:14 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id P4SD1n00g3ZTu2S3U4SDqW; Thu, 06 Feb 2014 16:26:14 +0000
Message-ID: <52F3B7A5.6070105@alum.mit.edu>
Date: Thu, 06 Feb 2014 11:26:13 -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: <7594FB04B1934943A5C02806D1A2204B1D15E955@ESESSMB209.ericsson.se> <74072016-DA11-41E8-9944-779428163EE4@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D15ED94@ESESSMB209.ericsson.se> <4CE22DF8-DE34-400A-95AE-2E011828DE88@lurchi.franken.de>
In-Reply-To: <4CE22DF8-DE34-400A-95AE-2E011828DE88@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=1391703974; bh=l00a2yfZfPCjjNZQ0WndVj+cTIf7CTElUacXvDKcVbk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=dr1yMwyjJkw+5s/usO9j3BdEGmYrhR2yKg1RkXEQiipM/My9zZDRfF/jNzR6XJ+ji J0AFLgQL0mbl6WKXImgSFwZ3uHdgnxuWzBch2ci8NFzC3fNeywKkEbp2Ek2jv270bN CI9Tg2uqcigJpG46lG4Dls1UOw+jRHWWIU99WkDhEaGp1l21XKj/UDiOtyp15rkk6j QjYyE8Wihp9IvcPyt0o+fDHmD5sHmcyTyX0LH7a+/p38vEqWnMGthfMVVvcnWsWf6p AHPGMlZHk1Fyzo33yGeTNCNouk0z+IWaIBnmzhjKvtNngG/q7+Vtzk6sHQMIowfOza X4cvGNp5FHVhw==
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: Thu, 06 Feb 2014 16:26:16 -0000

On 2/6/14 3:45 AM, Michael Tuexen wrote:
> On Feb 6, 2014, at 9:36 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>>>>> As discussed in the last IETF meeting, this PPID based fragmentation and reassembly will be removed from the ID.
>>>>
>>>> I assume the associated PPID values will also be un-registered with IANA?
>>> I guess they will stay... They are supported by Firefox and PPIDs are a pretty cheap resource. They are from a pool of 32-bit entities. That is why we registered the values before the RFCs get published.
>>
>> So, does that mean my WebRTC entity has to support them, in case the remote peer is on Firefox?
> I don't think so. Not sure what the plan for Firefox is, but I expect Firefox to change the
> code as soon as the final solution is specified.
>>
>> Also, if they are removed from the data channel draft, what reference will be used in the IANA table?
> I think it will stay. For PPIDs you even don't have to have an RFC. You can even register PPIDs
> as a person.

I hope that if values are retained simply for backward compatibility 
they are explicitly marked as deprecated.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email