W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2020

[webrtc-extensions] Invalid TURN credentials: What function should fail? (#52)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Nov 2020 15:43:52 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-737044913-1604591031-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-extensions:

== Invalid TURN credentials: What function should fail? ==
I had an issue come up with TURN credentials recently.

Sometimes, it's possible to tell that a TURN credential is invalid just from looking at them. For instance, username fields that violate the length restriction (509) in RFC 8489.

But I couldn't figure out from our spec what function should fail.

- RTCPeerConnection constructor or setConfiguration, where the parameters are passed in
- createOffer/addIceCandidate, where the candidates are used
- nowhere - just act as if the relevant TURN candidate was never generated

The last one is easiest to implement. Is it the right solution?

Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/52 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 November 2020 15:43:54 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 5 November 2020 15:43:55 UTC