[Rum] RUE NAT Traversal in draft-rosen-rue-01

[Paul Kyzivat <[e-mail]>]

In draft-rosen-rue-00 and earlier section 6.5 on NAT Traversal puts 
control of ICE, STUN, and TURN on the provider through provisioning of 
the RUE. The STUN/TURN servers are presumably selected by the provider.

In -01 this is changed to simply referencing 
draft-ietf-rtcweb-transports. That document puts some of the control 
over these in the hands of the browser, and allows the browser to be 
configured (presumably by the user). (Of course there is still a lot of 
control in the hands of the web server.)

Given that we are not assuming/requiring that the RUE be browser-based, 
it isn't clear to me that draft-ietf-rtcweb-transports is a necessary or 
sufficient condition.

OTOH, we don't want to exclude webrtc browser-based implementations. I 
have a feeling we need more options here. But at least we need more 
discussion on how this should work.

	Thanks,
	Paul