microsoft / microsoft/demikernel

[inetstack] Rely on `SocketAddr` `enum` Rather Than `SocketAddrV4` `struct`

Open
#204 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug confirmed good first issue
Dominant language
Rust
Stars
1.2k
Forks
151
PR merge metrics
No merged PRs in 30d

Description

Description

Catnip uses the Ipv4Endpoint SocketAddrV4 structure to refer to remote and local endpoints. While this is fine when supporting IPv4 addresses only, once we add support to IPv6 it is make the stack a mess. Therefore, we should change the stack so as to refer to local and remote endpoints using a more generic type, like IpEndpointSocketAddr.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating Catnip's local and remote endpoint declarations and every use of SocketAddrV4. Trace how those endpoints are passed through the stack, then replace the IPv4-specific type with SocketAddr consistently. Done means the stack uses the generic endpoint type throughout and its existing tests still pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.