WebRTC <-> TAPS Mapping Document

[tfpauly]

We should have a clarified mapping document (not in the primary draft) to address WebRTC, etc.

[csperkins]

WebRTC requires, e.g., RTP and DataChannel on the same port. Need to be clear how this fits into TAPS.

[mwelzl]

Just a note to say that NEAT is able to talk to a WebRTC peer; Michael Tuexen made sure that this would work and tested it.

I don't remember if there were many specific things necessary just for that... but I do remember one thing: Michael was concerned about peers that would make an assumption based on the stream number certain comunication arrives at - e.g. an SCTP server that assumes that stream 13 is only used for evil text messages (I'm coming up with a nonsense example as Halloween gets close). If we don't expose the stream number as such, we can't reasonably talk to such a server.

TAPS currently doesn't expose stream numbers, and if we don't absolutely have to, I don't think we should. I also suspect that stream numbers do not play a role for WebRTC - but I don't know... so I thought I'd write this here just in case.