How does js-libp2p deal with private networks and IPs?

[2color]

How does js-libp2p deal with private IPs with the default configuration?

For example, do the private IPs get shared over the wire when identify runs and then filtered locally?

Or does it check if a connection is over a private address and based on that chose which IPs to advertise?

[achingbrain]

All listening addresses are sent during identify. Other modules may make other decisions, for example Kad-DHT can be configured to filter out private addresses (i.e. amino does this) or public addresses (lan-only DHT does this).

Are you seeing public/private addresses in places you don't expect them?

[2color]

No, this came up in the context of p2plabsxyz/peersky-browser#39 and I wanted to make sure we have this documented somewhere.