Break out internal/net/udp

[backkem]

Breaking out the UDP wrapper to make it re-
usable in pion/sctp.

Relates to pion/sctp#74

TODO:

• Tag pion/udp after landing CI

[codecov]

Codecov Report

Merging #267 into master will decrease coverage by 0.44%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #267      +/-   ##
==========================================
- Coverage   77.82%   77.38%   -0.45%     
==========================================
  Files          76       75       -1     
  Lines        4077     3944     -133     
==========================================
- Hits         3173     3052     -121     
+ Misses        623      611      -12     
  Partials      281      281              

Flag	Coverage Δ
#go	77.42% <ø> (-0.45%)	⬇️
#wasm	75.07% <ø> (+2.42%)	⬆️

Impacted Files	Coverage Δ
listener.go	45.71% <ø> (ø)
internal/net/connctx/connctx.go	86.41% <0.00%> (-2.47%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f813a7d...daba2c5. Read the comment docs.

[Sean-Der]

Mind tagging v0.0.1

[Sean-Der]

Never mind you already made a note :)

[Sean-Der]

Are you able to delete github.com/pion/dtls/v2/internal/net/udp now?

[at-wat]

I definitely agree to split udp package and make it exposed. (pion/transport#57)
Do you think it's better to be a independent package out of pion/transport?

[backkem]

I definitely agree to split udp package and make it exposed. (pion/transport#57)
Do you think it's better to be a independent package out of pion/transport?

I think we've had overall positive experience with putting 'protocols' in their own repo. While pion/udp is only a thin wrapper it may still be useful on its own. In such case I prefer a separate repo since I want to encourage others to mix and match our protocols into their own stack. The DTLS implementation has been a prime example of this.
pion/transport is becoming a bit of a 'utils' package. That's fine for tooling we use across our libraries. However, if some piece, like maybe the mux, are useful to let people throw together their own stack, I'd consider exposing them using their own repo.