RFC 3550
E523055
RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
All labels observed (3)
| Label | Occurrences |
|---|---|
| Real-time Transport Protocol | 7 |
| RFC 3550 canonical | 3 |
| IETF RTP | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5480254 — 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 3550 Context triple: [RTP, definedIn, RFC 3550]
-
A.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
B.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
C.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
D.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
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 3550 Target entity description: RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
-
A.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
B.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
C.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
-
D.
RFC 3530
RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
-
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 (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| abbreviation | RTP ⓘ |
| applicationDomain |
IP telephony
ⓘ
audio streaming ⓘ multimedia conferencing ⓘ real-time applications ⓘ video streaming ⓘ |
| area | Real-time applications and infrastructure ⓘ |
| category | Standards Track ⓘ |
| defines |
CSRC identifiers
ⓘ
RTCP ⓘ
linked to:
Real-time Transport Control Protocol
RTP control protocol ⓘ RTP data transfer protocol ⓘ SSRC identifiers ⓘ contributing source identifiers ⓘ synchronization source identifiers ⓘ |
| designGoal |
end-to-end network transport for real-time data
ⓘ
jitter compensation support ⓘ robustness to packet loss ⓘ source identification ⓘ support for multicast and unicast ⓘ |
| intendedUse | Internet-scale real-time media transport ⓘ |
| language | English ⓘ |
| networkType |
IP networks
ⓘ
packet-switched networks ⓘ |
| obsoletes | RFC 1889 ⓘ |
| protocolType | transport protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relatedTo | RTP profiles such as RFC 3551 ⓘ |
| rfcNumber | 3550 ⓘ |
| specifies |
RTCP control packet formats
ⓘ
RTCP receiver reports ⓘ RTCP sender reports ⓘ RTCP source description packets ⓘ RTP header format ⓘ RTP mixing and translation rules ⓘ RTP payload identification mechanisms ⓘ RTP profile-independent mechanisms ⓘ RTP sequence number handling ⓘ RTP synchronization mechanisms ⓘ RTP timestamp handling ⓘ Real-time Transport Protocol ⓘ
linked to:
RFC 3550
|
| status | Internet Standard ⓘ |
| title | RTP: A Transport Protocol for Real-Time Applications ⓘ |
| uses | UDP as common underlying transport ⓘ |
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 3550 Description of subject: RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
Referenced by (11)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 3550
linked to: RFC 3550
linked to: RFC 3550
linked to: RFC 3550
linked to: RFC 3550
linked to: RFC 3550