- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Wed, 29 Oct 2014 17:15:18 -0700
- To: public-webrtc@w3.org
On 10/28/2014 09:12 PM, cowwoc wrote: > On 28/10/2014 11:35 PM, Harald Alvestrand wrote: >> On 10/28/2014 01:07 PM, Matthew Kaufman (SKYPE) wrote: >>> I'm not entirely thrilled about all the bugs being closed as "this >>> is the IETF's problem", but this one in particular is an issue. >>> There is currently NO chain of normative references, RFC or >>> otherwise, which when used as a specification results in SDP that is >>> compatible with any SDP generated or consumed by any WEBRTC >>> implementation. This is a bug *with the W3C specification* until >>> such time as we reach the point where the normative references are >>> sufficient to create an interoperable implementation without >>> reference to third party source code. >> I disagree with your interpretation of the state of play. >> >> The current reference to how SDP should be generated and parsed is JSEP. >> >> I agree that JSEP is not specifying the generation and parsing that >> browsers do today. This is a) a problem with JSEP (it wasn't complete >> last time I looked at it), and b) a problem with the browsers (they have >> not been updated to follow the parts of the spec that *are* complete). >> >> But the WEBRTC (W3C) bugtracker is about tracking issues that can be >> solved by *modifying W3C specifications*. There is nothing here that can >> be fixed by modifying a W3C specification. >> >> My conclusion is that keeping a bug in the W3C bugtracker that says >> "JSEP is not complete" makes no sense. Therefore, I closed this bug. > > How do you propose making sure that WebRTC 1.0 does not ship with > critical components (such as JSEP) underspecified? I get the fact that > this is in IETF's court but, semantics aside, isn't this something we > need to worry about? Speaking personally: I intend to participate in the IETF and contribute towards making sure JSEP is completed. I have the faith that the IETF will not publish JSEP as an RFC until it is complete. WRT the concept of "ship": At the time of W3C Last Call, references to internet-drafts are appropriate. At some later state in the W3C process, they are not appropriate - Dom will know the details. Sooner or later, the work will be done. But leaving a bug open in the W3C bug tracker has no influence on how fast it gets done. -- Surveillance is pervasive. Go Dark.
Received on Thursday, 30 October 2014 00:16:08 UTC