Re: ICE use cases

[RR] Per BA's point #2, we have the same issue. We need to be able to 
filter out wwan in our mobile gather process as an optional setting for 
the user of our mobile application if we want to prevent traffic from 
going over going over a wwan interface. This is important because wwan 
interfaces can be fairly costly with high cost roaming style charges. 
Alternatively, you might also want to chose to only send audio over wwan 
but don't allow video over wwan.


> Bernard Aboba <mailto:Bernard.Aboba@microsoft.com>
> April 17, 2014 at 1:42 PM
> In the discussion of ICE issues, it may be helpful to have some use 
> cases in mind. In particular, there are two use cases that we have 
> found to be tricky:
>
> 1. IPv6. With IPv6, it is possible to have a variety of IPv6 address 
> types (e.g. temporary, various types of tunnels, etc.). In some cases, 
> it may be desirable to exclude some types of addresses (e.g. only want 
> privacy addresses) or prioritize them in a way that might be different 
> from the system default (e.g. prioritize tunnels likely to be 
> unroutable lower, etc.)
>
> http://tools.ietf.org/html/draft-reddy-mmusic-ice-happy-eyeballs 
> provides a general approach, but doesn't deal with the tunnel issue.
>
> 2. Interface control. In situations where interfaces may have 
> differing costs (e.g. a WWAN interface that charges for traffic), 
> there may be a desire to control whether candidates from that 
> interface are included and if so, what the priority should be. This 
> may not be taken into account from conventional routing metrics which 
> may only take things like the interface speed into account.