-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Relative Drafts And Usages
TODO
- List the protocols used in the project
- What are the issues that these protocols used to solve
These are the protocols that make up the full WebRTC stack. The listed Sub-protocols are mentioned in the WebRTC spec.
API spec: https://w3c.github.io/webrtc-pc/
Protocol overview: https://tools.ietf.org/wg/rtcweb/
Transports overview: https://tools.ietf.org/html/draft-ietf-rtcweb-transports
Data-channel overview: https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel
Spec: RFC5245Bis
Usage: Used to establish a p2p connection by gathering network addresses using STUN and TURN and trying different combinations.
Sub-specs:
- IPv6 support
- RFC6544: ICE-TCP candidates
- Trickle ICE
- Dual Stack Fairness
Spec: RFC4566
Usage: Used to negotiate capabilities between peers. The capabilities include but are not limited to: networking details, media tracks, data channel information.
Spec: RFC5389
Usage: Used to identify your external IP address and keep a NAT binding alive until a direct connection to a peer can be established.
Sub-specs:
- IPv6 support (part of the main spec).
- (TLS-over-)TCP
- ALTERNATE-SERVER
Spec: RFC5766
Usage: Used to relay network traffic through the TRUN server. This is required in networks where direct p2p connection cannot be established due to highly restrictive NAT(s).
Sub-specs:
- RFC6156: TURN Extension for IPv6
- (TLS-over-)TCP Sending over TCP or TLS-over-TCP
Spec: RFC6347
Usage: Datagram Transport Layer Security
Sub-specs:
- DTLS-SRTP Multiplexing
- [RFC7983] Multiplexing Scheme Updates for SRTP Extension for DTLS
Spec: RFC4960
Usage: Stream Control Transmission Protocol
Sub-specs:
- RFC3758: SCTP Partial Reliability Extension
- RFC7496: Additional Policies for Partially Reliable Extension
- RFC6525: SCTP Stream Reconfiguration
- RFC8260: Stream Schedulers and User Message Interleaving for the SCTP
- RFC8261: DTLS Encapsulation of SCTP Packets
- RFC4821: Packetization Layer Path MTU Discovery
- RFC4820: Padding Chunk and Parameter for SCTP
- RFC5061: SCTP Dynamic Address Reconfiguration
Sign up for the Golang Slack and join the #pion channel for discussions and support
If you need commercial support/don't want to use public methods you can contact us at [email protected]