Skip to content

How to deal with ip4 and ip6? #21

@jbenet

Description

@jbenet

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions