RE: Summary of API for ICE State Reporting

I note that the slide deck does not cover the alternative that is documented in Martin Thomson's posting to the list (within the CU-RTCWEB document) , namely to not *have* an ICE state machine in the browser that needs its internals exposed in this way. I would suggest that if we are to devote any agenda time to discussing the alternative ways for handling issues that have come up with implementing ICE in the browser some of that time should be discussing that alternative.

Matthew Kaufman

From: Cullen Jennings (fluffy) [mailto:fluffy@cisco.com]
Sent: Sunday, August 26, 2012 9:59 AM
To: <public-webrtc@w3.org>
Subject: Summary of API for ICE State Reporting


I've tried to distill a bunch of the ICE state conversation into a proposal for the API to discuss on the conference call. Slides attached.

We probably need between 25 and 45 minutes on the conference call to sort this out