[metrics-team] onionoo exit_addresses semantics

[nusenu]

Karsten Loesing:
>>>> I would still omit that field if ORPort IP would be the _only_ member in the exit_addresses 
>>>> array because it increases size without increasing information.
>>> That's true, but it also increases client code complexity, because a user has to
>>> write something like:
>>>
>>> Set actual exit addresses to exit addresses
>>>
>>> if exit policy is not reject all IPv4 and exit addresses field is blank:
>>>   Add ORPort IPv4 addresses to actual exit addresses
>>>
>>> if exit policy is not reject all IPv6 and exit addresses field is blank:
>>>   Add ORPort IPv6 addresses to actual exit addresses
>>>
>>> Use actual exit addresses
>>>
>>> Do we think users will understand the definition of exit addresses, and
>>> write correct code like this every time?
>>>
>>> It might be worth the extra data. Compression should reduce the extra
>>> network bandwidth.
>> I my case it is just the other way around, if onionoo will include the 
>> data I'll have to do what onionoo does for me now (deduplication).
> Ah, so would that be an issue for you? I believe we'd have to make a
> major protocol version bump for this change anyway, so you'd have at
> least 1 month early warning.
> 
> Also, we can still decide whether to change the code or clarify the
> specification.

I'd prefer the current implementation over one that always includes
the ORPort IP in the exit_addresses, but either way it is not a
big effort to add a check on my site that drops exit_addresses
if exit_addresses consists of the OR Port IP only. 



-- 
https://mastodon.social/@nusenu
twitter: @nusenu_

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/metrics-team/attachments/20180217/48492e08/attachment.sig>