username/password in a=candidate or a=ice-ufrag, a=ice-pwd

1,010 views
Skip to first unread message

Raju

unread,
May 25, 2012, 6:39:32 PM5/25/12
to discuss...@googlegroups.com
Hi Folks,

Right now Chrome v17 is sending username and password parameters in a=candidate SDP line.
a=candidate:1 1 udp 1 135.252.143.76 2480 typ host name rtp network_name {DA9CED16-1BC8-4FBA-AC16-5775D00603E8} username utGhiGhOoUMOQT/Z password 0KTqLptc7U75JNW7 generation 0

As I understand these are extension parameters to a=candidate lines (thus not inter-operable across implementations).

Per ICE RFC 5245 (21.1.5. ice-pwd Attribute and 21.1.6. ice-ufrag Attribute) username should be in a=ice-ufrag and password should be in a=ice-pwd.
Is there a way to make Chrome se a=ice lines for username/password?
If not, what are the plans for using these standard ICE parameters in future?

Thanks!
Raju

Raju

unread,
May 26, 2012, 4:40:21 PM5/26/12
to discuss...@googlegroups.com
Sorry for my earlier typo, we are indeed using Chrom v19 which is evident from the following http header:
Does anyone know the future plans (Chrome version? and/or dates) for making this item ICE RFC compliant?
The URL provided in earlier post do not seem to have any dates though.

Sorry for seemingly duplicate posts.. they are all related to ICE RFC compliance. But, I just to make sure to
get answers separately as the date(s)/version(s) availability may be different for each of the item. 

Thanks
Raju 

Punyabrata Ray

unread,
May 29, 2012, 12:04:53 PM5/29/12
to discuss...@googlegroups.com
Hi Raju,

Please refer to the following issue  http://code.google.com/p/webrtc/issues/detail?id=345 

-pr
Reply all
Reply to author
Forward
0 new messages