W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2013

Re: Allowing RTCIceServer to contain multiple URLs

From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 3 Jun 2013 09:38:25 -0700
Message-ID: <CA+9kkMC1aKxeWLLkt_AVXxf7_DJF+fZoB85S2nAJYodnWYoKeA@mail.gmail.com>
To: Iņaki Baz Castillo <ibc@aliax.net>
Cc: Justin Uberti <juberti@google.com>, Eric Rescorla <ekr@rtfm.com>, Martin Thomson <martin.thomson@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>, Mallinath Bareddy <mallinath@google.com>
On Mon, Jun 3, 2013 at 3:37 AM, Iņaki Baz Castillo <ibc@aliax.net> wrote:

> In some RT protocols, the client does load-balancing and failover
> based on NAPTR/SRV records. For example, a SIP/XMPP client gets the
> SRV records of its domain, chooses one server and, since it does not
> respond, it connects to the next one. That mechanism is builit-in the
> protocol.
> The reason to do with this NAPTR is that NAPTR allows you to provide data
on the preference order for the services or to provide info on what
protocol to use to get the services.  Load-balancing in the way you
describe (just go to the next one in the list) can be accomplished simply
by listing multiple responses (e.g. A or AAAA
records).  There may be some systems that don't do that correctly, but I
doubt that they'd handle NAPTR records better (if at all).



> If the WebRTC client performs a NAPTR query and retrieve multiple
> servers, it can try all of them in a *transparent* way for the JS
> application. If instead a single DNS A or IP is given, such a failover
> feature is lost (or should be implemented at JS layer).
> --
> Iņaki Baz Castillo
> <ibc@aliax.net>
Received on Monday, 3 June 2013 16:38:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:44 UTC