RFC 3948
E524096
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3948 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T5479278 — 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 3948 Context triple: [NAT-T, definedIn, RFC 3948]
-
A.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
B.
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.
-
C.
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.
-
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 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 3948 Target entity description: RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
A.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
B.
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.
-
C.
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.
-
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 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 (47)
| Predicate | Object |
|---|---|
| instanceOf | IETF Request for Comments ⓘ |
| abbreviation | ESP ⓘ |
| addressesProblem |
IPsec traversal through NAT devices
ⓘ
linked to:
NAT-T
NAT traversal for ESP ⓘ |
| appliesTo |
IPv4
ⓘ
IPv6 ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
UDP encapsulation for IPsec ESP
ⓘ
method for IPsec ESP traversal through NAT ⓘ non-ESP marker for UDP-encapsulated traffic ⓘ |
| definesBehaviorFor | NAT devices handling ESP over UDP ⓘ |
| definesDefaultPort | UDP port 4500 ⓘ |
| documentType | Standards Track RFC ⓘ |
| enables |
ESP over UDP
ⓘ
IPsec NAT traversal ⓘ |
| focusesOn | tunnel mode IPsec ESP ⓘ |
| intendedAudience |
network equipment vendors
ⓘ
network protocol implementers ⓘ security gateway implementers ⓘ |
| language | English ⓘ |
| networkLayer | transport layer encapsulation for security protocol ⓘ |
| obsoletes | draft-ietf-ipsec-udp-encaps ⓘ |
| protocolFamily |
Internet Protocol Suite
ⓘ
linked to:
TCP/IP
|
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedToProtocol |
Encapsulating Security Payload
ⓘ
IPsec ⓘ |
| relatedToRFC |
RFC 2401
ⓘ
RFC 3947 ⓘ RFC 4301 ⓘ |
| relation | part of IPsec NAT traversal specifications set ⓘ |
| securityProperty | preserves ESP security semantics over UDP ⓘ |
| specifies |
demultiplexing rules for ESP and IKE over UDP port 4500
ⓘ
keepalive behavior for NAT traversal ⓘ packet format for ESP over UDP ⓘ |
| standardizes |
UDP encapsulation format for ESP packets
ⓘ
port usage for ESP over UDP ⓘ |
| status | Proposed Standard ⓘ |
| title | UDP Encapsulation of IPsec ESP Packets ⓘ |
| updates | NAT traversal behavior for IPsec implementations ⓘ |
| useCase |
VPNs through NAT devices
ⓘ
remote access IPsec clients behind NAT ⓘ site-to-site IPsec tunnels across NAT ⓘ |
| usesTransportProtocol | UDP ⓘ |
| workingGroup |
IP Security (ipsec) Working Group
ⓘ
linked to:
IETF IPsec Working Group
|
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 3948 Description of subject: RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.