RFC 9147
E548582
RFC 9147 is the Internet Engineering Task Force (IETF) specification that defines Datagram Transport Layer Security (DTLS) version 1.3, providing TLS-equivalent security over datagram-based transports.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9147 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5768039 — 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 9147 Context triple: [DTLS, definedInRFC, RFC 9147]
-
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 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.
-
C.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
D.
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.
-
E.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
- 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 9147 Target entity description: RFC 9147 is the Internet Engineering Task Force (IETF) specification that defines Datagram Transport Layer Security (DTLS) version 1.3, providing TLS-equivalent security over datagram-based transports.
-
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 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.
-
C.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
D.
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.
-
E.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
DTLS specification
ⓘ
IETF standard ⓘ Request for Comments ⓘ |
| alignsWith | RFC 8446 ⓘ |
| appliesToTransport |
DTLS over SCTP
ⓘ
linked to:
SCTP
UDP ⓘ datagram-based transports ⓘ |
| area | Security ⓘ |
| basedOn |
TLS 1.3
ⓘ
linked to:
RFC 8446
|
| category | Standards Track ⓘ |
| defines |
0-RTT data procedures for DTLS 1.3
ⓘ
alert protocol for DTLS 1.3 ⓘ anti-replay mechanisms for DTLS 1.3 ⓘ cipher suite negotiation for DTLS 1.3 ⓘ connection identifiers for DTLS 1.3 ⓘ handshake protocol for DTLS 1.3 ⓘ key schedule for DTLS 1.3 ⓘ privacy and security considerations for DTLS 1.3 ⓘ record layer for DTLS 1.3 ⓘ record sequence number handling for DTLS 1.3 ⓘ retransmission and loss handling for DTLS 1.3 ⓘ session resumption for DTLS 1.3 ⓘ |
| definesProtocolVersion |
DTLS 1.3
ⓘ
linked to:
DTLS
|
| hasNumber | 9147 ⓘ |
| monthPublished | April ⓘ |
| obsoletes |
DTLS 1.2 specification
ⓘ
linked to:
DTLS
RFC 6347 ⓘ |
| provides | TLS-equivalent security over datagram transports ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedToProtocol |
DTLS
ⓘ
Datagram Transport Layer Security ⓘ
linked to:
DTLS
|
| securityProperty |
authentication
ⓘ
confidentiality ⓘ integrity ⓘ |
| standardizes |
DTLS 1.3 record format
ⓘ
DTLS 1.3 version negotiation ⓘ Datagram TLS 1.3 handshake behavior ⓘ |
| standardsStatus | Internet Standard ⓘ |
| status |
Internet Standard
ⓘ
Standards Track ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
ⓘ
linked to:
DTLS
|
| updates | DTLS 1.2 design with TLS 1.3 features ⓘ |
| useCase |
IoT protocols over datagrams
ⓘ
QUIC-like environments requiring DTLS ⓘ VPN over UDP ⓘ real-time media over SRTP ⓘ |
| workingGroup | TLS Working Group ⓘ |
| yearPublished | 2022 ⓘ |
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 9147 Description of subject: RFC 9147 is the Internet Engineering Task Force (IETF) specification that defines Datagram Transport Layer Security (DTLS) version 1.3, providing TLS-equivalent security over datagram-based transports.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.