Re: [rtcweb] Transports: RFC 4941 support?

[Justin Uberti <[e-mail]>]

OK. Perhaps the guidance should be that if an interface has a temporary and
a non-temporary address, only the temporary one should be gathered. This
avoids any problems if local policy chooses not to use temporary addresses.

FWIW, I have seen this setup where a client has both non-temporary and
temporary addresses in the wild, so this is a real-world problem.


On Thu, Mar 20, 2014 at 7:39 PM, Roman Shpount <[e-mail]> wrote:

> On Thu, Mar 20, 2014 at 8:28 PM, Justin Uberti <[e-mail]> wrote:
>
>>
>> On Thu, Mar 20, 2014 at 4:17 PM, Roman Shpount <[e-mail]> wrote:
>>
>>> On Thu, Mar 20, 2014 at 7:03 PM, Justin Uberti <[e-mail]>wrote:
>>>
>>>> Your take is what I had in mind. Basically a ruleset like this:
>>>>
>>>>  gather_ipv4_addresses();
>>>>  if (has_ipv6) {
>>>>   if (has_temporary_addresses && temporaries_not_forbidden_by_policy) {
>>>>     gather_temporary_ipv6_addresses();
>>>>   } else {
>>>>     gather_non_temporary_ipv6_addresses();
>>>>  }
>>>> }
>>>>
>>>>
>>>  What should be done when temporary enabled only on some of the network
>>> interfaces of the device, i.e. if, for instance, WiFI interface has only
>>> non temp ipv6 address and LTE has both temp and permanent address present?
>>>
>>>
>> Is this a real-world problem? As I understand it, temporary addresses are
>> assigned by the host, so you either support them or you don't.
>>
>
> On Linux you can enable temporary addresses per interface, so it is
> possible.
>
> The whole problem (with using temp or permanent addresses) is a bit
> imaginary since under most common client setups you only see temporary
> addresses. Permanent IPv6 addresses show up only on servers or if
> specifically configured on the host.
> _____________
> Roman Shpount
>
>