You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having /ip4 and /ip6 explicit is very useful and nice. Though there are use cases where people want to be able to represent either, such as being able to have a /dns multiaddr like:
/dns/example.com/tcp/80
Resolve to either ip4 or ip6 addresses, depending on the application's capabilities
/ip4/1.2.3.4/tcp/80
/ip6/aaaa::1/tcp/80
I'm not convinced this is necessary, we can likely do without.
We could have /ip which decides on /ip4 vs. /ip6 the same way as /dns will decide. RFC 6555 describes the Happy Eyeballs algorithm for this decision. Browser vendors all do this a little differently, even differing between platforms.
Jorropo
pushed a commit
to Jorropo/multiaddr
that referenced
this issue
Dec 4, 2021
Having
/ip4
and/ip6
explicit is very useful and nice. Though there are use cases where people want to be able to represent either, such as being able to have a/dns
multiaddr like:Resolve to either ip4 or ip6 addresses, depending on the application's capabilities
The text was updated successfully, but these errors were encountered: