RFC 3947
E522223
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 3947 canonical | 2 |
| RFC 3947 (as an Internet-Draft predecessor) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479277 — 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 3947 Context triple: [NAT-T, definedIn, RFC 3947]
-
A.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
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 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
E.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
- 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 3947 Target entity description: RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
A.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
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 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 4954
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
E.
RFC 3980
RFC 3980 is an Internet Engineering Task Force (IETF) document that previously specified aspects of the iSCSI (Internet Small Computer Systems Interface) protocol before being superseded by RFC 7143.
- F. None of above. chosen
Statements (44)
| Predicate | Object |
|---|---|
| instanceOf | IETF Request for Comments ⓘ |
| appliesTo | IPv4 networks with NAT ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| complements | RFC 3948 ⓘ |
| defines |
NAT-Discovery (NAT-D) payloads in IKE
ⓘ
NAT-Traversal (NAT-T) capability negotiation in IKE ⓘ hash-based NAT discovery method in IKE ⓘ mechanism to detect presence of NAT between IPsec peers ⓘ mechanism to negotiate use of NAT traversal for IPsec ⓘ vendor-independent NAT traversal negotiation ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | operation of IPsec across Network Address Translators ⓘ |
| hasIdentifier | RFC 3947 ⓘ |
| intendedProtocol |
IKE
ⓘ
IPsec ⓘ |
| language | English ⓘ |
| networkLayer | Layer 3 ⓘ |
| obsoletes |
RFC 3947 (as an Internet-Draft predecessor)
ⓘ
linked to:
RFC 3947
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| purpose | to enable IPsec to function correctly through NAT devices ⓘ |
| relatedTo |
IKE
ⓘ
IKEv1 ⓘ IPsec ⓘ Internet Key Exchange ⓘ
linked to:
IKEv1
NAT Traversal ⓘ NAT-T ⓘ RFC 3948 ⓘ |
| scope | IKE Phase 1 and Phase 2 exchanges for NAT-T ⓘ |
| securityDomain |
IPsec VPNs
ⓘ
linked to:
IPsec
Virtual Private Networks ⓘ |
| securityProperty | preserves IPsec security semantics when traversing NATs ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies |
IKE payloads and exchanges for NAT detection
ⓘ
IKE payloads and exchanges for NAT-T negotiation ⓘ use of UDP encapsulation for IPsec ESP packets when NAT is detected ⓘ |
| standardizes | NAT traversal negotiation for IPsec using IKE ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | Negotiation of NAT-Traversal in the IKE ⓘ |
| updates | IPsec NAT traversal behavior for IKEv1 ⓘ |
| usesTransportProtocol | 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 3947 Description of subject: RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.