Changes between Initial Version and Version 1 of Ticket #15518


Ignore:
Timestamp:
Mar 31, 2015, 12:51:46 AM (4 years ago)
Author:
isis
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15518 – Description

    initial v1  
    1212}}}
    1313
    14 to determine if an address is in the same family. For an example IPv6 address, `2001:1234::0:1`, its /16 representation is `2001::/16`, meaning that `2001:ffff::` would be in the same family. A `\16` for IPv6 is ''huge'', particularly considering that [https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml only one-eighth of all IPv6 space is currently allocated for use on the internet] (`2000::/3`).
     14to determine if an address is in the same family. For an example IPv6 address, `2001:1234::0:1`, its /16 representation is `2001::/16`, meaning that `2001:ffff::` would be in the same family. A `\16` for IPv6 is ''huge'', particularly considering that [https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml only one-eighth of all IPv6 space is currently allocated for use on the internet] (`2000::/3`). for the path selection code, using `/16` essentially means that no two IPv6 routers in the same country (or possibly even continent) will be in the same path, and might possibly provide extremely increased chance of selection to routers in weird/rare IPv6 subnets.
    1515
    1616For a related ticket, see #15517 governing how BridgeDB's version of `EnforceDistinctSubnets` will work for IPv6. (In that ticket, I proposed using IPv6 `/32`s, since that is the [https://www.arin.net/resources/request/ipv6_initial_assign.html minimum ARIN IPv6 subnet allocation for a LIR].