RFC 5764
E592166
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5764 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6432329 — 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 5764 Context triple: [DTLS-SRTP, specifiedIn, RFC 5764]
-
A.
RFC 5214
RFC 5214 is an IETF standard that specifies the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) for transmitting IPv6 packets over IPv4 networks.
-
B.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
D.
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.
-
E.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
- 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 5764 Target entity description: RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
A.
RFC 5214
RFC 5214 is an IETF standard that specifies the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) for transmitting IPv6 packets over IPv4 networks.
-
B.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
C.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
D.
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.
-
E.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| aimsTo | enable secure real-time communications over IP networks ⓘ |
| appliesTo |
VoIP
ⓘ
Voice over IP ⓘ interactive multimedia applications ⓘ real-time media ⓘ video conferencing ⓘ |
| area |
Real-time Applications and Infrastructure
ⓘ
linked to:
Applications and Real-Time Area
|
| category | Standards Track ⓘ |
| contributesTo |
authentication of media endpoints
ⓘ
confidentiality of RTP media ⓘ end-to-end security for real-time media ⓘ integrity protection of RTP media ⓘ |
| defines |
DTLS-SRTP
ⓘ
DTLS-SRTP key management for SRTP ⓘ use of DTLS to establish SRTP keys ⓘ |
| focusesOn |
key establishment for SRTP using DTLS
ⓘ
protection of media streams ⓘ secure negotiation of SRTP parameters ⓘ |
| number | 5764 ⓘ |
| obsoletedBy | none ⓘ |
| obsoletes | none ⓘ |
| organization | Internet Society ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
NAT traversal for media
ⓘ
RTP ⓘ SRTP key management ⓘ media security ⓘ |
| securesProtocol |
SRTP
ⓘ
linked to:
SRTP for secure media transport
Secure Real-time Transport Protocol ⓘ
linked to:
SRTP for secure media transport
|
| specifies |
DTLS-SRTP handshake procedures
ⓘ
SRTP key derivation from DTLS ⓘ SRTP protection profiles ⓘ cipher suite negotiation for SRTP via DTLS ⓘ demultiplexing of DTLS, SRTP, and STUN on a single port ⓘ security considerations for DTLS-SRTP ⓘ use of DTLS extensions for SRTP ⓘ use of a single UDP port for DTLS and SRTP ⓘ |
| standardizes | DTLS-based keying for SRTP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)
ⓘ
linked to:
DTLS-SRTP
|
| transportLayer | UDP ⓘ |
| usedIn |
WebRTC media security
ⓘ
secure VoIP systems ⓘ secure video conferencing systems ⓘ |
| usesProtocol |
DTLS
ⓘ
Datagram Transport Layer Security ⓘ
linked to:
DTLS
|
| yearPublished | 2010 ⓘ |
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 5764 Description of subject: RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.