Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to deal with ip4 and ip6? #21

Open
jbenet opened this issue Sep 16, 2016 · 1 comment
Open

How to deal with ip4 and ip6? #21

jbenet opened this issue Sep 16, 2016 · 1 comment

Comments

@jbenet
Copy link
Member

jbenet commented Sep 16, 2016

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.
  • But opening issue to gather thoughts
  • This is also related to combinations of multiaddrs
@ghost
Copy link

ghost commented Dec 19, 2016

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
Update README.md multibase table to values from csv
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants