Martin v. Löwis added the comment:
I'm always in favour of using official terminology (and adjust if that changes
over time). So in this case, I agree with David's analysis, and suggest the
following specification:
- is_global returns False for all addresses where "Global" is "False" in the
IPv4 or IPv6 Special-Purpose Address Registry
- a new method is_private_use is introduced, giving True only for the RFC1918
addresses
- a new method is_unique_local is introduced, giving True only for the RFC 4193
addresses.
- is_private is deprecated. Alternatively, it could be preserved and documented
to being the union of is_privte_use and is_unique_local.
I don't think it it necessary to discuss footnote 1 in the IPv6 registry ("not
global unless a specific allocations says otherwise"). The specific allocations
that might override this come right below, so if we implement the table, we
would cover all those more specific case.
I'm puzzled why Teredo is listed as "not global"; my understanding is that the
Teredo prefixes even get announced in BGP, and are fully global.
----------
nosy: +loewis
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue20857>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
