RFC 5766
E127261
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
All labels observed (4)
| Label | Occurrences |
|---|---|
| RFC 5766 canonical | 6 |
| IETF RFC 5766 | 1 |
| RFC 5766 Section 14.9 | 1 |
| TURN specification RFC 5766 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1096597 — 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: RFC 5766 Context triple: [TURN, definedIn, RFC 5766]
-
A.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
B.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
C.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
D.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
E.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
- 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: RFC 5766 Target entity description: RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
A.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
B.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
C.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
D.
RFC 3416
RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
-
E.
RFC 6668
RFC 6668 is an Internet Engineering Task Force (IETF) standard that updates the Secure Shell (SSH) protocol to add support for modern elliptic curve cryptography methods.
- F. None of above. chosen
Statements (52)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| abbreviation | TURN ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| definesAttribute |
CHANNEL-NUMBER
ⓘ
DATA ⓘ DONT-FRAGMENT ⓘ EVEN-PORT ⓘ LIFETIME ⓘ REQUESTED-ADDRESS-FAMILY ⓘ REQUESTED-TRANSPORT ⓘ RESERVATION-TOKEN ⓘ XOR-PEER-ADDRESS ⓘ XOR-RELAYED-ADDRESS ⓘ |
| definesConcept |
TURN client
ⓘ
TURN server ⓘ allocation ⓘ allocation lifetime ⓘ channel binding ⓘ permission ⓘ relayed transport address ⓘ |
| definesMessageType |
Allocate request
ⓘ
Allocate response ⓘ ChannelBind request ⓘ CreatePermission request ⓘ Data indication ⓘ Refresh request ⓘ Send indication ⓘ |
| definesSecurityMechanism |
long-term credential mechanism
ⓘ
short-term credential mechanism ⓘ |
| enables | NAT traversal for real-time communication ⓘ |
| extends |
STUN
ⓘ
Session Traversal Utilities for NAT ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3489 ⓘ |
| primaryPurpose | relaying network traffic across NATs and firewalls ⓘ |
| protocolDefined | Traversal Using Relays around NAT ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedToProtocol | STUN ⓘ |
| shortTitle | TURN ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)
ⓘ
linked to:
Traversal Using Relays around NAT
|
| updates | RFC 5389 ⓘ |
| usedIn |
VoIP
ⓘ
WebRTC ⓘ |
| usesTransportProtocol |
DTLS
ⓘ
TCP ⓘ
linked to:
Transmission Control Protocol
TLS ⓘ UDP ⓘ |
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: RFC 5766 Description of subject: RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
Referenced by (9)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 5766
linked to: RFC 5766
linked to: RFC 5766