A browser client can accept a RTC connection from any other client. The connection is established using a offer\/answer model. It is good model surely but how can i understand if the offer contains the properties\u00a0of connection i m expecting? The problem seams in particular about data channels. In SDP protocol\u00a0for now \u00a0there is no information about the count\/identifiers\u00a0\u00a0of datachannels …. so\u00a0a\u00a0bad client could send a offer for 100000 datachannels \u00a0when the other peer was expecting 1 datachannel.\u00a0Same problem in renegotiation of offer\/answer. For my opinion it was better to introduce a more adavanced\u00a0security management in the native RTC model instead to leave to develop it by \u00a0web developer.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
A browser client can accept a RTC connection from any other client. The connection is established using a offer\/answer model. It is good model surely but how can i understand if the offer contains the properties\u00a0of connection i m expecting? … Continue reading