RE: How to get/set a=ice-options attributes with ORTC


Ice-options can impact the connectivity check behaviors per RFC: 
"
8.1.1.  Nominating Pairs

   The controlling agent nominates pairs to be selected by ICE by using
   one of two techniques: regular nomination or aggressive nomination.
   If its peer has a lite implementation, an agent MUST use a regular
   nomination algorithm.  If its peer is using ICE options (present in
   an ice-options attribute from the peer) that the agent does not
   understand, the agent MUST use a regular nomination algorithm.  If
   its peer is a full implementation and isn't using any ICE options or
   is using ICE options understood by the agent, the agent MAY use
   either the aggressive or the regular nomination algorithm.  However,
   the regular algorithm is RECOMMENDED since it provides greater
   stability.
"
We cannot blindly throw it away at JS layer. Upon seeing unknown ice-options, browser must switch to regular nomination, however we don't have a way to retrieve/set it on browser through ORTC.

Thanks, 

-Jiannan 

-----Original Message-----
From: Iñaki Baz Castillo [mailto:ibc@aliax.net] 
Sent: Wednesday, October 22, 2014 4:29 PM
To: Jiannan Zheng
Cc: public-ortc@w3.org
Subject: Re: How to get/set a=ice-options attributes with ORTC

2014-10-22 21:51 GMT+02:00 Jiannan Zheng <jzheng@exchange.microsoft.com>:
> For SDP line a=ice-options, how to get the local/set the remote on ORTC?
> getLocalParameters only has:
> dictionary RTCIceParameters {
>     DOMString usernameFragment;
>     DOMString password;
> };


Currently there is no one standarized value for 'ice-options'. If you concern is about "a=ice-options:google-ice" or something like that (which obviously is defined no where) the answer is easy:

ORTC does not define a "format" like SDP. It is an API and hence there is no room for setting un-meaningful key/value pairs. This is, why do you want to provide your ORTC stack with a "google-ice" option if the stack itself will do nothing with it?

In the other side, if you are worried about "SDP<->ORTC migration/interoperability" then the JS shim should get rid of invalid attributes found in the SDP (as "google-ice").

--
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Thursday, 23 October 2014 01:06:10 UTC