multiformats / multiformats/multiaddr
How to deal with ip4 and ip6?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 482
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reading this issue and the related combinations-of-multiaddrs issue (#20), then determine whether representing either IPv4 or IPv6 needs a protocol change. Done would require a decided approach and an agreed specification before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100