Re: [rtcweb] TURN server address via DHCP, WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11

[Harald Alvestrand <[e-mail]>]

On 09/26/2013 01:38 AM, Karl Stahl wrote:
>
> -----Ursprungligt meddelande-----
> Från: Cullen Jennings (fluffy) [mailto:[e-mail]]
> Skickat: den 25 september 2013 06:56
> Till: cb.list6
> Kopia: Karl Stahl; <[e-mail]>
> Ämne: Re: [rtcweb] TURN server address via DHCP, WGLC of
> draft-ietf-rtcweb-use-cases-and-requirements-11
>
>
>> On desktop OS, it is very hard for an application like a browser to learn
> any information that was passed via DHCP to the host. This has long been a
> problem for things like geopriv.
> [Karl] A WebRTC browser must be far beyond "a simple application". How can
> it otherwise see and hear us, send RTP over UDP, do ICE and other advanced
> stuff? It must already hook deep into the OS, so that in itself cannot be a
> problem if the OS would know about such a handy thing as a network provided
> TURN server...

All OSes have APIs. These APIs are controlled by the OS vendor.
Most of the information that's common across the relevant platforms is 
the information encapsulated in the POSIX standard (which is the base 
for both *BSD and Linux, which again form the basis for Android, MacOS 
and Linux).

So far, neither the POSIX standard nor any OS vendor has offered a 
generic facility to access information made available in DHCP packets.

Please don't talk about what "must be". Talk about what is. And if you 
don't know what is, ask.