RFC 6062
E548581
RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6062 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5768009 — 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 6062 Context triple: [Traversal Using Relays around NAT, updatedBy, RFC 6062]
-
A.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
B.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
- 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 6062 Target entity description: RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
-
A.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
-
B.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
C.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf | IETF Request for Comments ⓘ |
| applicability |
applications requiring TCP connectivity through NATs
ⓘ
applications that cannot use UDP for media or data ⓘ |
| area | Transport ⓘ |
| category | Standards Track ⓘ |
| defines |
ChannelBind for TCP connections
ⓘ
TCP connection establishment through a TURN server ⓘ TCP relaying via TURN ⓘ TURN TCP allocations ⓘ allocation of a TCP connection pair via TURN ⓘ connection-oriented relaying semantics ⓘ permission handling for TCP relays ⓘ |
| definesRole |
TURN client
ⓘ
TURN server ⓘ peer ⓘ |
| extends |
RFC 5766
ⓘ
Traversal Using Relays around NAT (TURN) ⓘ
linked to:
Traversal Using Relays around NAT
|
| intendedAudience |
implementers of TURN clients
ⓘ
implementers of TURN servers ⓘ protocol designers ⓘ |
| keyword |
NAT traversal
ⓘ
TCP relay ⓘ TURN extensions ⓘ firewall traversal ⓘ |
| networkScope |
Internet
ⓘ
linked to:
the internet
private IP networks with NAT ⓘ |
| protocolFamily |
STUN/TURN
ⓘ
linked to:
STUN
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| purpose | to enable TCP-based applications to operate across NATs and firewalls using TURN relays ⓘ |
| relatedTo |
NAT traversal
ⓘ
client-server applications over TCP ⓘ firewall traversal ⓘ real-time communication applications ⓘ |
| relationship |
complements UDP-based TURN defined in RFC 5766
ⓘ
part of the STUN/TURN/ICE NAT traversal framework ⓘ |
| securityConsideration |
authentication using STUN long-term credentials
ⓘ
confidentiality via TLS or DTLS on the signaling path ⓘ integrity protection of TURN messages ⓘ |
| specifies |
error handling for TCP relays
ⓘ
lifetime handling for TCP allocations ⓘ message flows for TCP allocation ⓘ security considerations for TCP relaying ⓘ |
| status | Proposed Standard ⓘ |
| title |
Traversal Using Relays around NAT (TURN) Extensions for TCP Allocations
ⓘ
linked to:
Traversal Using Relays around NAT
|
| updatesProtocol | TURN ⓘ |
| usesTransport |
TCP
ⓘ
linked to:
Transmission Control Protocol
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 6062 Description of subject: RFC 6062 is an IETF specification that extends the TURN protocol to support TCP relaying for applications operating across NATs and firewalls.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.