STUN protocol
E544009
The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
All labels observed (2)
| Label | Occurrences |
|---|---|
| STUN | 2 |
| STUN protocol canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5768154 — 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.
Target entity: STUN protocol Context triple: [Interactive Connectivity Establishment, relatedTo, STUN protocol]
-
A.
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.
-
B.
Session Initiation Protocol
Session Initiation Protocol (SIP) is a signaling protocol used to establish, modify, and terminate real-time communication sessions such as voice and video calls over IP networks.
-
C.
NAT and firewall traversal requirements for WebRTC
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.
-
D.
H.323
H.323 is an ITU-T standard that defines protocols for voice, video, and data communication over packet-based networks such as IP.
-
E.
SIP
SIP is the IATA airport code for Simferopol International Airport, the main air gateway to the Crimean Peninsula.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: STUN protocol Target entity description: The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
-
A.
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.
-
B.
Session Initiation Protocol
Session Initiation Protocol (SIP) is a signaling protocol used to establish, modify, and terminate real-time communication sessions such as voice and video calls over IP networks.
-
C.
NAT and firewall traversal requirements for WebRTC
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.
-
D.
H.323
H.323 is an ITU-T standard that defines protocols for voice, video, and data communication over packet-based networks such as IP.
-
E.
SIP
SIP is the IATA airport code for Simferopol International Airport, the main air gateway to the Crimean Peninsula.
- F. None of above. chosen
Statements (54)
| Predicate | Object |
|---|---|
| instanceOf |
IETF protocol
ⓘ
network protocol ⓘ |
| abbreviation | STUN ⓘ |
| canUsePort |
TCP port 5349
ⓘ
UDP port 5349 ⓘ |
| category | NAT traversal protocol ⓘ |
| clientRole | sends binding requests to STUN server ⓘ |
| definedIn | RFC 5389 NERFINISHED ⓘ |
| designGoal |
be simple and lightweight
ⓘ
minimize server state ⓘ |
| firstStandardized | 2003 ⓘ |
| fullName | Session Traversal Utilities for NAT NERFINISHED ⓘ |
| layer | application layer ⓘ |
| limitation |
cannot reliably traverse all symmetric NATs
ⓘ
does not itself relay media ⓘ |
| messageType |
Binding Error Response
ⓘ
Binding Request ⓘ Binding Response ⓘ Shared Secret Error Response ⓘ Shared Secret Request ⓘ Shared Secret Response ⓘ |
| obsoletes | RFC 3489 NERFINISHED ⓘ |
| operatesOver |
TCP
NERFINISHED
ⓘ
UDP NERFINISHED ⓘ |
| purpose |
assist devices in traversing NATs and firewalls
ⓘ
discover public IP address and port of a client ⓘ enable peer-to-peer connectivity ⓘ help determine the type of NAT a client is behind ⓘ |
| relatedTo |
ICE
NERFINISHED
ⓘ
TURN ⓘ |
| securityMechanism |
HMAC-SHA1 for message integrity
ⓘ
long-term credential mechanism ⓘ short-term credential mechanism ⓘ |
| serverRole | reflects observed source IP address and port ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| supportsTransport |
IPv4
ⓘ
IPv6 ⓘ |
| updatedSpecificationYear | 2008 ⓘ |
| usedBy |
SIP-based systems
ⓘ
VoIP applications ⓘ WebRTC NERFINISHED ⓘ real-time communication applications ⓘ |
| usesAttribute |
FINGERPRINT
ⓘ
MAPPED-ADDRESS ⓘ MESSAGE-INTEGRITY ⓘ NONCE ⓘ REALM ⓘ USERNAME ⓘ XOR-MAPPED-ADDRESS ⓘ |
| usesEncoding | binary message format ⓘ |
| usesIdentifier | transaction ID ⓘ |
| usesPort |
TCP port 3478
ⓘ
UDP port 3478 ⓘ |
| workingGroup | MMUSIC NERFINISHED ⓘ |
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.
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.
Subject: STUN protocol Description of subject: The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.