Re: [rtcweb] Review of draft-ietf-rtcweb-mdns-ice-candidates

I would suggest observing the connection success rate of

* host-to-host candidate pairs only,
* without getUserMedia (on the local side), and
* only if the remote peer also takes part in the mDNS test (should be
easy to recognise by looking at the remote's host candidates but doesn't
work if the remote peer uses getUserMedia... perhaps signal it via an
SDP attribute)

in comparison to as it is now. All of the above conditions should be
required for reporting results because this is the case that we want to
observe.

Cheers
Lennart

On 29.09.2018 08:16, Justin Uberti wrote:
> We will turn it on for N% of Chrome instances and observe the connection
> success rate and setup time versus control.
> 
> On Fri, Sep 28, 2018 at 4:05 AM Lennart Grahl <lennart.grahl@gmail.com>
> wrote:
> 
>> How will that data be gathered? Is anyone else gathering data? Safari?
>>
>> Cheers
>> Lennart
>>
>> On 28.09.18 01:10, Justin Uberti wrote:
>>> I suggest that we hold off on assessing what this might mean for data
>>> channel and related applications until we have data from browsers showing
>>> the actual connectivity/traffic impact of mDNS.
>>>
>>> We should have initial data on this topic from Chrome by EOY.
>>>
>>> On Mon, Sep 24, 2018 at 10:14 PM youenn fablet <youennf@gmail.com>
>> wrote:
>>>
>>>>
>>>>
>>>>> Perhaps its feasible for those use cases where the administrator is
>>>>> already aware of the software but definitely not for small applications
>>>>> such as sharedrop.io, Threema Web whose main use case is the direct
>>>>> connection in same network environments and its significant benefits
>>>>> regarding throughput.
>>>>>
>>>>
>>>> I agree this is the most likely scenario where host candidates are
>>>> actually useful: two web browsers doing pure data channel on a
>>>> managed/complex network, and no coordination between the network admin
>>>> being and the app.
>>>>
>>>> _______________________________________________
>>>> rtcweb mailing list
>>>> rtcweb@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>>>
>>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
> 