IETF Logo Mail Archive

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

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 06 February 2014 08:36 UTC

Return-Path: <christer.holmberg@ericsson.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 7F3FF1A0090 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 00:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 55x9ICz9jbI4 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 00:36:04 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8651A006A for <rtcweb@ietf.org>; Thu, 6 Feb 2014 00:36:03 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-6e-52f34972016c
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 31.F0.04853.27943F25; Thu, 6 Feb 2014 09:36:02 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0387.000; Thu, 6 Feb 2014 09:36:01 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Thread-Topic: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing
Thread-Index: Ac8jEP4UAFTLik6/TaCDQ1g2OxFaDP//90SA///s4PA=
Date: Thu, 06 Feb 2014 08:36:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D15ED94@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D15E955@ESESSMB209.ericsson.se> <74072016-DA11-41E8-9944-779428163EE4@lurchi.franken.de>
In-Reply-To: <74072016-DA11-41E8-9944-779428163EE4@lurchi.franken.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyM+JvjW6R5+cgg9VfxC0uNi1htLi2/DWr xdp/7ewOzB4LNpV6LFnyk8ljQ8sOpgDmKC6blNSczLLUIn27BK6MbY8PsRbMZK34032fvYGx naWLkZNDQsBEou3cNnYIW0ziwr31bF2MXBxCAicYJZpmHWWCcBYxSjQ+u8DcxcjBwSZgIdH9 TxukQUTAVOLg8nlgg5gF/CSa1+0Bs4UFQiSm7T3DCFETKrH02gRmCNtKomvLKlaQMSwCKhKz f+uBhHkFfCV6f6yHWtXBKHHudA9YL6eAq8TmmV/ZQGxGoOO+n1rDBLFLXOLWk/lMEEcLSCzZ c54ZwhaVePn4HyuErShxdfpyqHodiQW7P7FB2NoSyxa+ZoZYLChxcuYTlgmMYrOQjJ2FpGUW kpZZSFoWMLKsYpQsTi0uzk03MtDLTc8t0UstykwuLs7P0ytO3cQIjKyDW34b7WA8ucf+EKM0 B4uSOO911pogIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYw7k1TPLd282P3dplM3go6mPc1x l2DvWlGdmiV2a/OjXZaFDzbdev7qrETODxm2zG/XHuZYbk2q5g55xG++2Hzi5r3MAYflPBPP r6+vO/Hv3MFdd3YZKP6pXXn7fZkP47MjFw3+SuxoWP9pi/qpb7cLDzK+WfZCRruKb2Uuw5+D O2cePBvV90BouRJLcUaioRZzUXEiAHJwsGl6AgAA
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: Thu, 06 Feb 2014 08:36:05 -0000

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?

Also, if they are removed from the data channel draft, what reference will be used in the IANA table?

Regards,

Christer

v2.23.0 | Report a Bug | By Email