- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Tue, 23 Jul 2013 17:58:03 -0400
- To: rtcweb@ietf.org
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
- Message-ID: <51EEFC6B.9090503@bbs.darktech.org>
On 23/07/2013 12:51 PM, Adam Roach wrote: > On 7/23/13 11:22, Roman Shpount wrote: >> The situation would be a bit clearer if patent holders were to >> provide the licensing policy regarding this IPR release. Given that >> Ericsson is actively involved in this working group, I think it would >> be reasonable to ask them for this. > > If process has been properly followed, the IPR holder has already been > notified by the IETF executive director. See > http://www.ietf.org/rfc/rfc4879.txt (section 1 paragraph 1) > > I doubt agitating for action on these mailing lists is likely to > produce useful results. > > /a Hi Adam, I'm a bit concerned about the optics of what just happened. * The Working Group has been pushing for the use of SDP since 2011 (see http://www.ietf.org/mail-archive/web/rtcweb/current/mail15.html). * The first post related to the use of SDP in WebRTC came from Christer Holmberg of Ericsson on September 14th, 2011. * One of the Chairs of the Working Group and one of the Specification editors are from Ericsson. * There has been a substantial push against the use of SDP by some mailing list participants, but this was rejected by the Working Group. * Suddenly we find out that Ericsson has filed two patents related to the use of SDP in WebRTC and these were filed *after* Ericsson actively pushed for the use of SDP. Isn't there a conflict of interest here? As a Web Developer who doesn't want/need SDP to begin with, I am finding this a bitter pill to swallow. I have no problem with other people using SDP (all the power to them) but, with this IPR discovery, forcing their preference on me will have real-world consequences (no less than had we mandated the use H264 in WebRTC). 1. Do the patents imply that Web Developers will have to pay patents when deploying application on top of the Browser or Native APIs? 2. Is there a way to retrofit the API so those of us who do not want/need to use SDP are not forced to license this IPR? For example, the specification states that the initial offer/answer mechanism is out of scope. Could we do the same for SDP? Thank you, Gili
Received on Tuesday, 23 July 2013 21:58:53 UTC