SDP capability negotiation extensions
E565072
SDP capability negotiation extensions are a set of IETF-defined mechanisms that allow endpoints using the Session Description Protocol to dynamically negotiate and select compatible media and transport capabilities during session setup.
All labels observed (1)
| Label | Occurrences |
|---|---|
| SDP capability negotiation extensions canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6034571 — 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: SDP capability negotiation extensions Context triple: [IETF MMUSIC Working Group, standardizes, SDP capability negotiation extensions]
-
A.
Session Description Protocol
Session Description Protocol (SDP) is a format used in multimedia communication systems to describe streaming media sessions for purposes such as session announcement, invitation, and negotiation of media parameters.
-
B.
RFC 5245
RFC 5245 is the IETF specification that standardizes Interactive Connectivity Establishment (ICE), a framework for NAT traversal used to establish media and data connections in real-time communication protocols like SIP and WebRTC.
-
C.
STUN protocol
The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
-
D.
DTLS-SRTP
DTLS-SRTP is a security protocol framework that uses Datagram Transport Layer Security to negotiate keys and provide encryption and authentication for Secure Real-time Transport Protocol media streams, commonly used in VoIP and WebRTC.
-
E.
SRTP for secure media transport
SRTP for secure media transport is a security protocol that encrypts and authenticates real-time audio and video streams, commonly used in VoIP and WebRTC communications.
- 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: SDP capability negotiation extensions Target entity description: SDP capability negotiation extensions are a set of IETF-defined mechanisms that allow endpoints using the Session Description Protocol to dynamically negotiate and select compatible media and transport capabilities during session setup.
-
A.
Session Description Protocol
Session Description Protocol (SDP) is a format used in multimedia communication systems to describe streaming media sessions for purposes such as session announcement, invitation, and negotiation of media parameters.
-
B.
RFC 5245
RFC 5245 is the IETF specification that standardizes Interactive Connectivity Establishment (ICE), a framework for NAT traversal used to establish media and data connections in real-time communication protocols like SIP and WebRTC.
-
C.
STUN protocol
The STUN protocol (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port and determine the type of NAT or firewall they are behind to enable peer-to-peer connectivity.
-
D.
DTLS-SRTP
DTLS-SRTP is a security protocol framework that uses Datagram Transport Layer Security to negotiate keys and provide encryption and authentication for Secure Real-time Transport Protocol media streams, commonly used in VoIP and WebRTC.
-
E.
SRTP for secure media transport
SRTP for secure media transport is a security protocol that encrypts and authenticates real-time audio and video streams, commonly used in VoIP and WebRTC communications.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
IETF protocol extension
ⓘ
SDP extension mechanism ⓘ |
| abbreviation | SDP capneg ⓘ |
| appliesTo |
multimedia sessions
ⓘ
offer/answer model ⓘ |
| backwardsCompatibleWith | basic SDP ⓘ |
| category | media negotiation mechanism ⓘ |
| definedIn |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| definedInRFC | RFC 5939 ⓘ |
| designGoal |
flexible capability selection
ⓘ
interoperability between heterogeneous endpoints ⓘ minimal impact on legacy SDP processing ⓘ |
| documentType | Internet Standard Track specification ⓘ |
| enables |
advertising multiple capability sets in a single SDP
ⓘ
selection of a single agreed configuration ⓘ |
| extends | SDP offer/answer procedures ⓘ |
| governedBy |
IETF MMUSIC working group
ⓘ
linked to:
IETF MMUSIC Working Group
|
| hasGoal |
backward compatibility with legacy SDP endpoints
ⓘ
selection of compatible media capabilities ⓘ selection of compatible transport capabilities ⓘ |
| negotiates |
codec alternatives
ⓘ
security alternatives ⓘ transport alternatives ⓘ |
| organization | Internet Engineering Task Force ⓘ |
| provides |
mechanisms to describe alternative capabilities
ⓘ
mechanisms to fall back to baseline SDP ⓘ mechanisms to negotiate preferred configurations ⓘ |
| relatedTo |
SDP
ⓘ
media capability negotiation ⓘ offer/answer model ⓘ transport capability negotiation ⓘ |
| standardStatus | Proposed Standard ⓘ |
| supports |
dynamic negotiation of media capabilities
ⓘ
dynamic negotiation of transport capabilities ⓘ |
| supportsCapabilityType |
bandwidth-related capabilities
ⓘ
media format capabilities ⓘ security capabilities ⓘ transport protocol capabilities ⓘ |
| updatesRFC | RFC 3264 ⓘ |
| usedDuring | session setup ⓘ |
| usedIn |
VoIP systems
ⓘ
multimedia conferencing ⓘ real-time communication systems ⓘ |
| usesModel | offer/answer negotiation ⓘ |
| usesProtocol | Session Description Protocol ⓘ |
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: SDP capability negotiation extensions Description of subject: SDP capability negotiation extensions are a set of IETF-defined mechanisms that allow endpoints using the Session Description Protocol to dynamically negotiate and select compatible media and transport capabilities during session setup.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.