TCP ICE first iteration

[sgfn]

ref: elixir-webrtc/ex_ice#89

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.01%. Comparing base (55582ce) to head (de27e07).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #238      +/-   ##
==========================================
- Coverage   88.07%   88.01%   -0.07%     
==========================================
  Files          59       59              
  Lines        2835     2836       +1     
==========================================
- Hits         2497     2496       -1     
- Misses        338      340       +2     

Files with missing lines	Coverage Δ
lib/ex_webrtc/peer_connection.ex	85.35% <100.00%> (-0.24%)	⬇️
lib/ex_webrtc/peer_connection/configuration.ex	95.05% <ø> (ø)
lib/ex_webrtc/rtp_receiver/nack_generator.ex	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Karolk99]

You can add simple tests that check if a transceiver was created with the correct protocol

[sgfn]

Even though RFC 4571, sec. 4. defines a token value TCP/RTP/AVP that should seemingly "fit better" in the SDP mlines when using TCP transport, we adhere to the guidelines from RFC 5764, sec. 8. and always use UDP/TLS/RTP/SAVPF. This is because the media stream still uses DTLS and is essentially unchanged, the only difference being handled by ICE (RFC 4571 framing and TCP transport for the would-be UDP datagram payloads).

The same applies to UDP/DTLS/SCTP used in data channels.