Antione,

We're (netaddr) going to try to use ipaddr if possible, but there are 
operations which we are providing to API users that aren't directly
supported by ipaddr. We haven't yet determined the level of effort
involved in trying to work with ipaddr's base classes in supporting
these, but it may be more effort (and code) than it's worth (the
benefits of using ipaddr may be lost).

In a sense, it would be a shame. But on the other hand, we have examples
where 3-rd party web frameworks don't use the built-in HTTP server, and
that hasn't been a problem. In many ways, netaddr is evolving into an IP
manipulation framework. Those that need its features can use it; those
that just need the basics will be able to get that in the stdlib.

In any case, it will be in our best interest to provide some
compatibility layer between the two :-)