NAT and firewall traversal requirements for WebRTC
E134383
NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
All labels observed (1)
| Label | Occurrences |
|---|---|
| NAT and firewall traversal requirements for WebRTC canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1166611 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NAT and firewall traversal requirements for WebRTC Context triple: [IETF RTCWEB Working Group, defines, NAT and firewall traversal requirements for WebRTC]
-
A.
WebRTC
WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
-
B.
RTCPeerConnection
RTCPeerConnection is a WebRTC API interface that enables real-time audio, video, and data communication between web browsers or devices by managing the underlying peer-to-peer connection.
-
C.
Traversal Using Relays around NAT
Traversal Using Relays around NAT (TURN) is a network protocol that enables devices behind firewalls or NATs to communicate by relaying their traffic through an intermediate server.
-
D.
NAT-T
NAT-T (NAT Traversal) is an IPsec extension that enables VPN traffic to pass through Network Address Translation devices by encapsulating IPsec packets in UDP.
-
E.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: NAT and firewall traversal requirements for WebRTC Target entity description: NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
-
A.
WebRTC
WebRTC is an open web technology that enables real-time audio, video, and data communication directly between browsers and devices without requiring plugins.
-
B.
RTCPeerConnection
RTCPeerConnection is a WebRTC API interface that enables real-time audio, video, and data communication between web browsers or devices by managing the underlying peer-to-peer connection.
-
C.
Traversal Using Relays around NAT
Traversal Using Relays around NAT (TURN) is a network protocol that enables devices behind firewalls or NATs to communicate by relaying their traffic through an intermediate server.
-
D.
NAT-T
NAT-T (NAT Traversal) is an IPsec extension that enables VPN traffic to pass through Network Address Translation devices by encapsulating IPsec packets in UDP.
-
E.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
- F. None of above. chosen
Statements (71)
| Predicate | Object |
|---|---|
| instanceOf |
WebRTC requirement category
ⓘ
technical specification area ⓘ |
| allows | TCP and TLS-based fallback when UDP is blocked ⓘ |
| appliesTo |
WebRTC endpoints
ⓘ
WebRTC media servers ⓘ signaling servers used by WebRTC ⓘ |
| definedIn |
RFC 5245
ⓘ
surface form:
IETF RFC 5245
RFC 5389 ⓘ
surface form:
IETF RFC 5389
RFC 5766 ⓘ
surface form:
IETF RFC 5766
RFC 8445 ⓘ
surface form:
IETF RFC 8445
IETF RFC 8825 ⓘ IETF RFC 8826 ⓘ |
| hasConstraint |
must minimize information leakage through NAT traversal
ⓘ
must support typical enterprise firewall policies ⓘ must use secure transport protocols ⓘ |
| hasGoal |
enable WebRTC data to traverse NATs
ⓘ
enable WebRTC media to traverse NATs ⓘ enable WebRTC traffic through firewalls ⓘ fall back to relay when direct connectivity fails ⓘ maximize direct peer-to-peer connectivity ⓘ |
| hasSecurityProperty |
must authenticate STUN and TURN usage where appropriate
ⓘ
must protect TURN servers from unauthorized use ⓘ must protect against amplification attacks via STUN ⓘ |
| relatedTo |
DTLS
ⓘ
HTTPS ⓘ ICE ⓘ ICE candidates ⓘ ICE full implementation ⓘ ICE nomination ⓘ ICE restart ⓘ ICE-lite ⓘ IPv4 ⓘ IPv6 ⓘ NAT traversal ⓘ SCTP over DTLS ⓘ SRTP for secure media transport ⓘ
surface form:
SRTP
STUN protocol ⓘ
surface form:
STUN
STUN binding request ⓘ STUN binding response ⓘ Transmission Control Protocol ⓘ
surface form:
TCP
TLS ⓘ TURN ⓘ TURN allocation ⓘ TURN channels ⓘ TURN permissions ⓘ UDP ⓘ WebRTC ⓘ WebRTC gateways ⓘ browser WebRTC implementations ⓘ candidate gathering ⓘ carrier-grade NAT ⓘ connectivity checks ⓘ data channel connectivity ⓘ dual stack networks ⓘ enterprise firewalls ⓘ firewall traversal ⓘ full cone NAT ⓘ home routers ⓘ host candidates ⓘ interactive connectivity establishment ⓘ media path connectivity ⓘ port restricted cone NAT ⓘ relayed candidates ⓘ restricted cone NAT ⓘ server reflexive candidates ⓘ symmetric NAT ⓘ trickle ICE ⓘ |
| requires |
ICE support in endpoints
ⓘ
at least one STUN server ⓘ at least one TURN server for reliability ⓘ support for UDP connectivity checks ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: NAT and firewall traversal requirements for WebRTC Description of subject: NAT and firewall traversal requirements for WebRTC are the standardized technical guidelines that ensure WebRTC media and data can reliably pass through network address translators and firewalls in real-world internet deployments.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.