RFC 1889
E523056
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1889 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T5480255 — 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 1889 Context triple: [RTP, replaces, RFC 1889]
-
A.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
B.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
E.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
- 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 1889 Target entity description: RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
-
A.
RFC 1869
RFC 1869 is an early Internet standard that introduced the Extended Simple Mail Transfer Protocol (ESMTP) framework for adding optional extensions to SMTP.
-
B.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 1668
RFC 1668 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specifications evolved.
-
E.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments
ⓘ
technical standard ⓘ |
| abbreviation | RTP ⓘ |
| applicationDomain |
audio over IP
ⓘ
interactive conferencing ⓘ multimedia communication ⓘ real-time applications ⓘ streaming media ⓘ video over IP ⓘ |
| area | Transport ⓘ |
| category | Standards Track ⓘ |
| defines | Real-time Transport Protocol ⓘ |
| definesConcept |
CSRC
ⓘ
RTP header ⓘ RTP mixer ⓘ
linked to:
RTP
RTP payload format ⓘ RTP payload type ⓘ RTP profile ⓘ RTP sequence number ⓘ RTP synchronization source identifier ⓘ RTP timestamp ⓘ RTP translator ⓘ
linked to:
RTP
SSRC ⓘ contributing source identifier ⓘ interarrival jitter ⓘ jitter calculation ⓘ lip-sync using RTP timestamps ⓘ |
| networkType | IP networks ⓘ |
| obsoletedBy | RFC 3550 ⓘ |
| obsoletes | none (first RTP specification) ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relatedSpecification |
RTCP
ⓘ
RTP Control Protocol ⓘ
linked to:
Real-time Transport Control Protocol
|
| rfcNumber | 1889 ⓘ |
| shortTitle | RTP ⓘ |
| specifiesLayer | transport layer ⓘ |
| specifiesProtocol | Real-time Transport Protocol ⓘ |
| status | Obsoleted ⓘ |
| title | RTP: A Transport Protocol for Real-Time Applications ⓘ |
| transportProtocol | UDP ⓘ |
| useCase |
delivery of real-time audio
ⓘ
delivery of real-time video ⓘ multicast sessions ⓘ unicast sessions ⓘ |
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 1889 Description of subject: RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.