RFC 5382
E545176
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 5382 canonical | 3 |
| RFC 5382 title NAT Behavioral Requirements for TCP | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5770831 — 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 5382 Context triple: [RFC 6146, updates, RFC 5382]
-
A.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
B.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
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.
-
E.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
- 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 5382 Target entity description: RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
A.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
B.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
C.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
D.
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.
-
E.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
NAT behavioral requirements specification ⓘ Request for Comments ⓘ |
| aimsTo |
improve application compatibility across NAT devices
ⓘ
improve interoperability across NAT devices ⓘ |
| appliesTo |
NAT vendors
ⓘ
middlebox implementers ⓘ network operators deploying NATs ⓘ |
| area | Internet Area ⓘ |
| BCPNumber | BCP 142 ⓘ |
| category | Best Current Practice ⓘ |
| concerns | IPv4 NAT behavior ⓘ |
| defines |
NAT behavioral requirements for TCP
ⓘ
linked to:
NAT Behavioral Requirements for TCP
terminology for TCP NAT behaviors ⓘ |
| documentType | Standards-track technical specification ⓘ |
| focusesOn |
TCP connection tracking behavior in NATs
ⓘ
TCP filtering behavior in NATs ⓘ TCP state management in NATs ⓘ TCP timers in NATs ⓘ |
| intendedTo |
reduce connectivity problems caused by NAT behavior
ⓘ
support a wide range of TCP-based applications across NATs ⓘ |
| language | English ⓘ |
| networkLayer | transport layer ⓘ |
| obsoletes | RFC 3489 ⓘ |
| partOf | NAT behavioral requirements document set ⓘ |
| protocolFamily | TCP/IP ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
NAT
ⓘ
linked to:
NAT-T
Network Address Translation ⓘ RFC 4787 ⓘ RFC 5508 ⓘ TCP ⓘ
linked to:
Transmission Control Protocol
Transmission Control Protocol ⓘ |
| specifies |
requirements for TCP endpoint-independent filtering in NATs
ⓘ
requirements for TCP endpoint-independent mapping in NATs ⓘ requirements for TCP keep-alive handling in NATs ⓘ requirements for TCP session timeouts in NATs ⓘ requirements for handling TCP FIN segments in NATs ⓘ requirements for handling TCP RST segments in NATs ⓘ requirements for handling TCP simultaneous open across NATs ⓘ requirements for handling unsolicited inbound TCP segments ⓘ |
| status | Best Current Practice ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | NAT Behavioral Requirements for TCP ⓘ |
| updates | RFC 4787 ⓘ |
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 5382 Description of subject: RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 5382