RFC 4347
E543999
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 4347 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T5768037 — 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 4347 Context triple: [DTLS, definedInRFC, RFC 4347]
-
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 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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 4347 Target entity description: 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.
-
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 4741
RFC 4741 is the original IETF specification that defines the NETCONF network configuration protocol for managing network devices.
-
D.
RFC 3447
RFC 3447 is an earlier IETF standard that specified the RSA Cryptography Standard (PKCS #1) before being superseded by RFC 8017.
-
E.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard document
ⓘ
Request for Comments ⓘ |
| abbreviation | DTLS ⓘ |
| applicationDomain |
VoIP
ⓘ
multimedia streaming ⓘ online games ⓘ real-time applications ⓘ |
| area | Security Area ⓘ |
| basedOn |
TLS
ⓘ
Transport Layer Security ⓘ
linked to:
TLS
|
| category | Standards Track ⓘ |
| compatibleWith | existing TLS cipher suites ⓘ |
| definesProtocol |
Datagram Transport Layer Security
ⓘ
linked to:
DTLS
|
| designGoal | TLS-like security over unreliable datagram transports ⓘ |
| ensures | end-to-end security over datagram transports ⓘ |
| handles |
packet duplication
ⓘ
packet loss ⓘ packet reordering ⓘ |
| includesMechanism |
alert protocol
ⓘ
change cipher spec protocol ⓘ cookie exchange for denial-of-service protection ⓘ handshake protocol ⓘ record protocol ⓘ retransmission of handshake messages ⓘ sequence numbers for records ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 6347 ⓘ |
| protocolType |
security protocol
ⓘ
transport layer security protocol ⓘ |
| provides |
authentication
ⓘ
confidentiality ⓘ integrity ⓘ replay protection ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| shortName |
DTLS 1.0
ⓘ
linked to:
DTLS
|
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| supports |
pre-shared key cipher suites
ⓘ
public key cipher suites ⓘ |
| supportsTransport |
UDP-based applications
ⓘ
unreliable datagram transports ⓘ |
| title |
Datagram Transport Layer Security
ⓘ
linked to:
DTLS
|
| updates | TLS specification ⓘ |
| usesTransport |
UDP
ⓘ
User Datagram Protocol ⓘ
linked to:
UDP
|
| workingGroup | Network 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 4347 Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.