RFC 4787
E546374
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4787 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5770830 — 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 4787 Context triple: [RFC 6146, updates, RFC 4787]
-
A.
RFC 4347
RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
-
B.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 6147
RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
-
E.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
- 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 4787 Target entity description: RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
A.
RFC 4347
RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
-
B.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 6147
RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
-
E.
RFC 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF RFC
ⓘ
standards document ⓘ |
| addresses |
ICMP handling by NATs
ⓘ
NAT hairpinning support ⓘ NAT mapping and filtering consistency ⓘ NAT traversal issues for UDP ⓘ fragmentation handling by NATs ⓘ interoperability of NATs with UDP-based applications ⓘ port preservation behavior ⓘ |
| appliesTo | IPv4 NAT ⓘ |
| area | Transport ⓘ |
| BCPNumber | BCP 127 NERFINISHED ⓘ |
| category | Best Current Practice ⓘ |
| defines |
behavioral requirements for NAT devices
ⓘ
requirements for endpoint-independent filtering ⓘ requirements for endpoint-independent mapping ⓘ requirements for hairpinning behavior ⓘ requirements for port assignment behavior ⓘ requirements for timer handling for UDP mappings ⓘ terminology for NAT behaviors ⓘ |
| focusesOn |
NAT behavioral requirements
ⓘ
Network Address Translation ⓘ unicast UDP traffic ⓘ |
| goal |
improve interoperability of NATs with UDP applications
ⓘ
standardize NAT behavior for unicast UDP ⓘ |
| hasSuccessor |
RFC 5382
NERFINISHED
ⓘ
RFC 5508 NERFINISHED ⓘ RFC 7857 NERFINISHED ⓘ |
| intendedFor |
designers of NAT devices
ⓘ
implementers of NAT devices ⓘ network operators ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 7857 NERFINISHED ⓘ |
| obsoletes | none ⓘ |
| protocol | UDP ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatedTo |
RFC 5382
ⓘ
RFC 5508 NERFINISHED ⓘ RFC 7857 NERFINISHED ⓘ |
| scope | unicast traffic ⓘ |
| series | Request for Comments NERFINISHED ⓘ |
| status | Best Current Practice ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Network Address Translation (NAT) Behavioral Requirements for Unicast UDP NERFINISHED ⓘ |
| updatesBehaviorOf | NAT devices ⓘ |
| workingGroup |
BEHAVE
NERFINISHED
ⓘ
Behavior Engineering for Hindrance Avoidance (BEHAVE) 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.
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 4787 Description of subject: RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.