RFC 3489
E544001
RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3489 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5768070 — 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 3489 Context triple: [RFC 5766, obsoletes, RFC 3489]
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
C.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- 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 3489 Target entity description: RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
C.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf | IETF Request for Comments ⓘ |
| area | Transport ⓘ |
| author |
Christian Huitema
NERFINISHED
ⓘ
Joel Weinberger NERFINISHED ⓘ Jonathan Rosenberg NERFINISHED ⓘ Rohan Mahy NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
STUN binding request
ⓘ
STUN binding response ⓘ STUN client ⓘ STUN server ⓘ |
| definesProtocol | STUN NERFINISHED ⓘ |
| documentLanguage | English ⓘ |
| focusesOn |
NAT traversal
ⓘ
UDP NERFINISHED ⓘ public IP address discovery ⓘ public port discovery ⓘ |
| format | text ⓘ |
| introducesConcept |
NAT type discovery
ⓘ
full cone NAT ⓘ port restricted cone NAT ⓘ restricted cone NAT ⓘ symmetric NAT ⓘ |
| obsoletedBy | RFC 5389 NERFINISHED ⓘ |
| portNumber | 3478 ⓘ |
| protocolFullName | Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) NERFINISHED ⓘ |
| publicationDate | 2003-03 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| relation |
early specification of the STUN protocol
ⓘ
predecessor of modern STUN, TURN, and ICE mechanisms ⓘ |
| replacedBy | new STUN specification in RFC 5389 ⓘ |
| RFCNumber | 3489 ⓘ |
| securityConsideration | vulnerability to certain attacks due to NAT classification heuristics ⓘ |
| shortTitle | STUN NERFINISHED ⓘ |
| specifiesMessageFormat |
STUN attributes
ⓘ
STUN message header ⓘ |
| standardizationLevel | Proposed Standard ⓘ |
| status | Obsoleted ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs) NERFINISHED ⓘ |
| transportProtocol | UDP NERFINISHED ⓘ |
| useCase |
NAT traversal for real-time communication
ⓘ
discovering a device’s public IP address ⓘ discovering a device’s public UDP port ⓘ |
| year | 2003 ⓘ |
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 3489 Description of subject: RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.