Home › Entities › request_for_comments › RFC 3550: RTP: A Transport Protocol for Real-Time Applications

RFC 3550: RTP: A Transport Protocol for Real-Time Applications

request for comments publication
Place request_for_comments Q47197819
Press Enter · cited answer in seconds

RFC 3550: RTP: A Transport Protocol for Real-Time Applications

Summary

RFC 3550: RTP: A Transport Protocol for Real-Time Applications is a Request for Comments[1].

Key Facts

  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications authored RTP: A Transport Protocol for Real-Time Applications — author (P50): Henning Schulzrinne[2].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's instance of is recorded as RTP: A Transport Protocol for Real-Time Applications — instance of (P31): Request for Comments[3].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's publisher is recorded as RTP: A Transport Protocol for Real-Time Applications — publisher (P123): Internet Engineering Task Force[4].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's DOI is recorded as 10.17487/RFC3550[5].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's language of work or name is recorded as RTP: A Transport Protocol for Real-Time Applications — language of work or name (P407): English[6].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's publication date is recorded as +2003-07-01T00:00:00Z[7].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's RfC ID is recorded as 3550[8].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's main subject is recorded as RTP: A Transport Protocol for Real-Time Applications — main subject (P921): Real-time Transport Protocol[9].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's main subject is recorded as RTP: A Transport Protocol for Real-Time Applications — main subject (P921): Real-time Transport Control Protocol[10].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://tools.ietf.org/html/rfc3550[11].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3550.txt[12].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3550.txt[13].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3550.txt.pdf[14].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3550.ps[15].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3550.pdf[16].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's number of pages is recorded as {'unit': '1', 'amount': '+104'}[17].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's replaces is recorded as RTP: A Transport Protocol for Real-Time Applications — replaces (P1365): RFC 1889: RTP: A Transport Protocol for Real-Time Applications[18].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's title is recorded as RTP: A Transport Protocol for Real-Time Applications[19].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's author name string is recorded as S. Casner[20].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's author name string is recorded as R. Frederick[21].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's author name string is recorded as V. Jacobson[22].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's amended by is recorded as RTP: A Transport Protocol for Real-Time Applications — amended by (P2567): RFC 5506: Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and Consequences[23].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's amended by is recorded as RTP: A Transport Protocol for Real-Time Applications — amended by (P2567): RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port[24].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's amended by is recorded as RTP: A Transport Protocol for Real-Time Applications — amended by (P2567): RFC 6051: Rapid Synchronisation of RTP Flows[25].
  • RFC 3550: RTP: A Transport Protocol for Real-Time Applications's amended by is recorded as RTP: A Transport Protocol for Real-Time Applications — amended by (P2567): RFC 6222: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)[26].

Body

Designation and Status

RFC 3550: RTP: A Transport Protocol for Real-Time Applications's instance of is recorded as RTP: A Transport Protocol for Real-Time Applications — instance of (P31): Request for Comments[3].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . wikidata.org.
  9. [10] ↑ . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . RFC Index. Retrieved . wikidata.org.
  19. [20] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . RFC Index. Retrieved . wikidata.org.
  23. [24] ↑ . RFC Index. Retrieved . wikidata.org.
  24. [25] ↑ . RFC Index. Retrieved . wikidata.org.
  25. [26] ↑ . RFC Index. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 3550: RTP: A Transport Protocol for Real-Time Applications. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-3550-rtp-a-transport-protocol-for-real-time-applications
MLA “RFC 3550: RTP: A Transport Protocol for Real-Time Applications.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-3550-rtp-a-transport-protocol-for-real-time-applications.
BibTeX @misc{4ortxyz_rfc-3550-rtp-a-transport-protocol-for-real-time-applications_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 3550: RTP: A Transport Protocol for Real-Time Applications}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-3550-rtp-a-transport-protocol-for-real-time-applications}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 3550: RTP: A Transport Protocol for Real-Time Applications — https://4ort.xyz/entity/rfc-3550-rtp-a-transport-protocol-for-real-time-applications (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-3550-rtp-a-transport-protocol-for-real-time-applications · Last refreshed: