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

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 07 February 2014 07:27 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 593F21A05B7 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 23:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, 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 y6TUBH8Fi_Ij for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 23:27:51 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4701A05AC for <rtcweb@ietf.org>; Thu, 6 Feb 2014 23:27:50 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-48-52f48af4ef82
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 1C.3B.10875.4FA84F25; Fri, 7 Feb 2014 08:27:48 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0387.000; Fri, 7 Feb 2014 08:27:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] RTCWEB Data Channel: Usage of PPID for protocol multiplexing
Thread-Index: AQHPI5H4g+NNW9fTlk27SCBTz5+sApqpZO9Q
Date: Fri, 07 Feb 2014 07:27:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D16131F@ESESSMB209.ericsson.se>
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> <52F3B7A5.6070105@alum.mit.edu>, <3B7B334C-868A-4128-B7BF-07C66B649443@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D160930@ESESSMB209.ericsson.se>, <D5AE9FDB-77D9-422A-B995-C4BF299D9DE0@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D160A98@ESESSMB209.ericsson.se> <75145993-7226-4C5D-845C-A96D51D3D68B@lurchi.franken.de> <52F4189B.3020309@alvestrand.no>
In-Reply-To: <52F4189B.3020309@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+Jvje6Xri9BBocnG1kc6+tis1j7r53d gcnjyoQrrB5LlvxkCmCK4rJJSc3JLEst0rdL4Mr4PaONteAEZ8Xz67vYGxgvs3cxcnJICJhI XHt2hRXCFpO4cG89WxcjF4eQwCFGiZ6VLYwQziJGia1n3gFVcXCwCVhIdP/TBmkQEQiW6H3+ nhHEFhYIkXiytYsNIh4qcXP6D0aQchEBI4nVrbUgYRYBFYn2uffBdvEK+Eoc+/2bGWJ8O6vE sWPNYL2cAroSTd/ugs1kBDro+6k1TCA2s4C4xK0n85kgDhWQWLLnPDOELSrx8vE/qAcUJdqf NjBC1OtILNj9iQ3C1pZYtvA1M8RiQYmTM5+wTGAUnYVk7CwkLbOQtMxC0rKAkWUVI3tuYmZO ernhJkZgLBzc8lt3B+OpcyKHGKU5WJTEeT+8dQ4SEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnV wKinGbtyAVscf+A7x6BjXF/0dcRWuMz+Xnr3jPflCdazGKM3xptV8RbzbfN65CO8s4Hno2ri 3GD9KZfYo2LD6984OdxsXrXcy9zrjcZZoYMpoppnylnOZvBqXzJ3a7t7IFmtJbRtz0N23oy+ 53MCOgPb9xaGvb7whJWtbQqv8JQ5HOtf+iR+UGIpzkg01GIuKk4EAE3FGWZTAgAA
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: Fri, 07 Feb 2014 07:27:52 -0000

>>>>>>> I hope that if values are retained simply for backward compatibility they are explicitly marked as deprecated.
>>>>>> My plan was just not to defined what they are used for...
>>>>> I would like to have some explanation text. Having registered values without any kind of explanation is not a good approach, in my opinion.
>>>> The reason why I registered them is that they are used by Firefox 
>>>> and there was the possibility that the PPID based fragmentation and 
>>>> reassembly got standardised. I wanted to avoid the case that Firefox 
>>>> uses some values and other protocols register these values. That 
>>>> would have been pretty bad. Since they are a very cheap resource, I just went ahead and "saved"
>>>> the values.
>>> That is a all good. But, when people wonder 5 years from now, I don't 
>>> want them to have to look for this e-mail in oder to get an 
>>> explanation :)
>> Understood. But do you think they walk through the IANA registry? I 
>> would expect them to read RFCs and follow the procedures described there.
>
> Updating the registry to read "Obsolete; was used by <draft name>"
> should satisfy all comers.

+ 1

Regards,

Christer