Connectivity Transports

Open
#99 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
networking

Research direction

Use the three example multiaddrs as the initial behavioral scope and clarify how packet loss, latency, and bandwidth parameters should be represented. Done means an agreed design and implementation plan for these transports, including parsing and observable behavior; the payload names no files or tests to run.

Written by the indexing model from the issue text.

Description

It would be interesting to add special transports for thing like:

  • packet loss
  • latency
  • bandwidth limits
    with parameters specified as the address.

Something like:

/ip4/1.2.3.4/testloss/0.7/udp/1234     # 70% packet loss
/ip4/1.2.3.4/testlat/0.250:1/udp/1234  # + ~ N(0.25, 1) s of latency
/ip4/1.2.3.4/testbw/10M:1M/udp/1234    # bandwidth ratio limit: 10Mbps down : 1Mbps up
Dominant language
Go
Stars
482
Forks
87
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from multiformats/multiaddr

All issues in multiformats/multiaddr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.