IETF Logo Mail Archive

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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Thu, 06 February 2014 08:45 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 C3B651A01FB for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 00:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.535, SPF_HELO_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 2YMebvmWjmcT for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 00:45:54 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFE01A0090 for <rtcweb@ietf.org>; Thu, 6 Feb 2014 00:45:54 -0800 (PST)
Received: from [192.168.1.200] (p508F1F22.dip0.t-ipconnect.de [80.143.31.34]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 4DC931C0E97A5; Thu, 6 Feb 2014 09:45:52 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D15ED94@ESESSMB209.ericsson.se>
Date: Thu, 06 Feb 2014 09:45:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CE22DF8-DE34-400A-95AE-2E011828DE88@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D15E955@ESESSMB209.ericsson.se> <74072016-DA11-41E8-9944-779428163EE4@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D15ED94@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1510)
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:45:56 -0000

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.
> 
> Regards,
> 
> Christer
> 
>

v2.23.0 | Report a Bug | By Email