> On 22. Mar 2020, at 22:55, Spencer Dawkins at IETF <spencerdawkins.ietf@xxxxxxxxx> wrote: > > > > On Sun, Mar 22, 2020 at 8:52 AM Carsten Bormann <cabo@xxxxxxx> wrote: > On 2020-03-22, at 11:21, Michael Tuexen <Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote: > > > >> The one thing that would be most useful for me right now would be a document with operational considerations for keeping WebRTC running (e.g., How not to mess it up with your firewall). > > Would that be another candidate for C238? > > Not sure that it needs to get stuck there, but yes, it might be a useful part of that suite of documents. A lot of people here have been in the trenches long enough that they know deeply what breaks WebRTC in a firewall, and it would be a useful operational-area exercise to extract that knowledge and make it presentable (and RFP-referenceable!) to firewall builders and maintainers. > > I was hoping Michael was kidding, but since he's not ... Michael was. But Carsten took is seriously. I would like to see such a document, but don't keep it in the RFC editor queue for a long time... Best regards Michael > > As much as I enjoyed some getting some TSVWG doc unstuck from C238, someday that cluster needs to finally empty out, > > On a related note, I wonder if this document would be a candidate for MOPS? > > Best, > > Spencer > > Grüße, Carsten >
