netaddr
netaddr copied to clipboard
inetaf
Network address types
For IPv4 addresses mapped to IPv6 (e.g. ::ffff:127.0.0.1) `netaddr.IP` methods (e.g. `IsLoopback()`) return `false`, but `net.IP` returns `true` (tested with go 1.16.4). Given the goal of compatibility with net.IP this...
I'm puzzling over how IPPort and IPPrefix's MarshalText methods should work when their IP is the zero IP but they have a non-zero port/bits. Currently we return an empty slice,...
If I AddRange an invalid range, IPSet does nothing, successfully. This is surprising, a more normal idiom in Go would be to have AddRange return an error, and have a...
(Re-filing #154, which was closed when half of it was done) An IPPrefix is currently an IP + a uint16, 32 bytes. Now that IPPrefix is opaque, we can make...
Currently this library is untranslatable to other languages due to having just error strings. So please add lot of `error` types and/or error enums to the `error` types so that...
I suggest we refactor out our 128 bit support in a go4.org package. Perhaps it will be of use to the people engaged in https://github.com/golang/go/issues/9455 —and perhaps uses of that...
We should document what methods are safe to call concurrently. In general things aren't safe (and that's the default to assume in Go when not documented otherwise), but we have...
In a twitter thread (end of the thread: https://twitter.com/dave_universetf/status/1341977567658536960), the question came up of why handle IPv4-mapped IPv6 addresses specially. After much consideration, I can't identify any good use cases...
Perhaps the zero value of IP can be the (or, "an") unspecified address. Then our version of https://golang.org/pkg/net/#IP.IsUnspecified can also respect a nil `ipImpl` as being unspecified. We'd need to...