Re: [rtcweb] Is rtcweb the right place for draft-ietf-rtcweb-mdns-ice-candidates?

[Harald Alvestrand <[e-mail]>]

Den 04.07.2019 20:46, skrev Roman Shpount:
> I understand that running experiments before proposing a solution is
> probably a good thing and this is what Chrome was doing up until this
> point. At the same time, rolling this feature into production before at
> least documenting it, will definitely cause interop problems. What we
> have now is a fairly major feature with a fairly outdated specification
> where all the interop issues weren't considered.
> 

To be precise, we have documentation for the feature
(draft-ietf-rtcweb-mdns-ice-candidates), it's been largely unchanged for
quite some time, and it's what Chrome is in the process of shipping.

It addresses a quite substantive issue (as in "millions of occurences
per day" of the behavior we want to prevent).

The fact that we're only getting the interoperability issues discovered
as we roll out the feature to stable is sad; I don't know how to get
other people's software tested earlier in the cycle, which is what would
have given us more time to work through these issues.

Given mmusic's traditional processing speed, I am not sure there's any
point in formally moving the document at this point.

Harald