ironcore-dev / ironcore-dev/dpservice
Design choice: IP-in-IPv6 only – why not VXLAN/GRE/MPLS?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17
- Forks
- 10
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 5
Description
Question?
what's the main purpose of this project? I noticed it only supports IP-in-IPv6 tunneling, but not VXLAN, GRE, or MPLS. Why was this choice made? Isn't that limiting, especially when most cloud fabrics rely on VXLAN or GRE for overlay networking? Just trying to understand the design philosophy – thanks!
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
The issue names no files, tests, or entry points. Review the project's stated purpose and networking design, then explain why IP-in-IPv6 is supported instead of VXLAN, GRE, or MPLS. Done means the design rationale and intended protocol scope are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100