RFC 3551
E523057
RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3551 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5480293 — 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 3551 Context triple: [RTP, payloadTypesDefinedIn, RFC 3551]
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
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.
-
C.
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.
-
D.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- 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 3551 Target entity description: RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
-
A.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
B.
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.
-
C.
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.
-
D.
RFC 2570
RFC 2570 is an Internet standards document that updates and replaces earlier SNMP-related specifications, refining the framework for network management using the Simple Network Management Protocol.
-
E.
RFC 3415
RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
RTP profile specification ⓘ |
| appliesTo |
audio conferencing
ⓘ
real-time multimedia communication ⓘ video conferencing ⓘ |
| area | Real-time Applications and Infrastructure ⓘ |
| category | Standards Track ⓘ |
| defines |
MIME subtype names for RTP payload formats
ⓘ
RTP audio profile ⓘ RTP channel count conventions ⓘ RTP clock rate assignments ⓘ RTP media type mappings ⓘ RTP video profile NERFINISHED ⓘ channel and sample rate conventions for audio in RTP ⓘ default RTP payload format parameters ⓘ default RTP payload types ⓘ packetization rules for audio and video in RTP ⓘ payload type number assignments for common codecs ⓘ use of RTCP for audio and video conferences ⓘ |
| definesDefaultPort |
RTCP port 5005
ⓘ
RTP port 5004 ⓘ |
| definesPayloadType |
CN
NERFINISHED
ⓘ
DVI4 ⓘ G723 ⓘ G728 NERFINISHED ⓘ G729 NERFINISHED ⓘ GSM NERFINISHED ⓘ H261 NERFINISHED ⓘ H263 NERFINISHED ⓘ L16 ⓘ LPC NERFINISHED ⓘ MPA NERFINISHED ⓘ MPV ⓘ PCMA NERFINISHED ⓘ PCMU ⓘ QCELP NERFINISHED ⓘ |
| definesPayloadTypeRange |
dynamic payload types 96–127
ⓘ
static payload types 0–95 ⓘ |
| intendedUse | Internet-wide real-time multimedia applications ⓘ |
| obsoletes | RFC 1890 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | Request for Comments NERFINISHED ⓘ |
| rfcNumber | 3551 ⓘ |
| specifies | RTP profile for audio and video conferences with minimal control ⓘ |
| specifiesProtocol |
RTP
NERFINISHED
ⓘ
Real-time Transport Protocol NERFINISHED ⓘ |
| status | Internet Standard ⓘ |
| title | RTP Profile for Audio and Video Conferences with Minimal Control NERFINISHED ⓘ |
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 3551 Description of subject: RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.