W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Re: Valid syntax for TURN USERNAME

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 15 Jan 2014 12:20:27 +0100
Message-ID: <CALiegf=UCtg=Gi+L-EER2WuMguLYRqeqWh7aivY6ZoDgH5fvsQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
2014/1/15 Justin Uberti <juberti@google.com>:
> The TURN URL is like any other URL, any magic characters need to be
> URL-encoded. However, the 'username' and 'credential' fields in RTCIceServer
> should be processed as-is.

Justin, URI for TURN is specified by RFC 7065 and as you can see in
the copy&paste below from RFC 7065, no username is allowed in a TURN
URI. The TURN username is provided at the same time than the TURN URI
(i.e. in WebRTC) but it is not part of the URI:

   Although a "turn" or "turns" URI does not itself include the username
   or password that will be used to authenticate the TURN client, in
   certain environments, such as WebRTC, the username and password will
   almost certainly be provisioned remotely by an external agent at the
   same time as a "turns" URI is sent to that client.


> If this isn't what you are seeing, please file a bug.

It is not a bug but something not specified in any RFC or draft
(unless I missed something). RFC 5766 (TURN) does neither specify the
valid syntax for the USERNAME field within the TURN protocol.

So:

- TURN USERNAME syntax is not specified in any document.
- Chrome does not allow "@" symbol in the IceServers "username" field.
Why? Based on what?

Note however this is not a question about Chrome but about the specification.

Thanks a lot.





-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Wednesday, 15 January 2014 11:21:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:37 UTC