Home › Entities › request_for_comments › RFC 8860: Sending Multiple Types of Media in a Single RTP Session

RFC 8860: Sending Multiple Types of Media in a Single RTP Session

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

RFC 8860: Sending Multiple Types of Media in a Single RTP Session

Summary

RFC 8860: Sending Multiple Types of Media in a Single RTP Session is a Request for Comments[1].

Key Facts

  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session authored Sending Multiple Types of Media in a Single RTP Session — author (P50): Colin Perkins[2].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session authored Sending Multiple Types of Media in a Single RTP Session — author (P50): Magnus Westerlund[3].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's instance of is recorded as Sending Multiple Types of Media in a Single RTP Session — instance of (P31): Request for Comments[4].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's publisher is recorded as Sending Multiple Types of Media in a Single RTP Session — publisher (P123): Internet Engineering Task Force[5].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's based on is recorded as Sending Multiple Types of Media in a Single RTP Session — based on (P144): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[6].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's based on is recorded as Sending Multiple Types of Media in a Single RTP Session — based on (P144): RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control[7].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's DOI is recorded as 10.17487/RFC8860[8].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's language of work or name is recorded as Sending Multiple Types of Media in a Single RTP Session — language of work or name (P407): English[9].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's publication date is recorded as +2021-01-01T00:00:00Z[10].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's RfC ID is recorded as 8860[11].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's work available at URL is recorded as https://tools.ietf.org/html/rfc8860[12].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's title is recorded as Sending Multiple Types of Media in a Single RTP Session[13].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's author name string is recorded as J. Lennox[14].
  • RFC 8860: Sending Multiple Types of Media in a Single RTP Session's DBLP publication ID is recorded as journals/rfc/rfc8860[15].

Body

Designation and Status

RFC 8860: Sending Multiple Types of Media in a Single RTP Session's instance of is recorded as Sending Multiple Types of Media in a Single RTP Session — instance of (P31): Request for Comments[4].

References

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

Direct Wikidata claims

  1. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [3] ↑ . 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] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . 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] ↑ . 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 8860: Sending Multiple Types of Media in a Single RTP Session. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session
MLA “RFC 8860: Sending Multiple Types of Media in a Single RTP Session.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session.
BibTeX @misc{4ortxyz_rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 8860: Sending Multiple Types of Media in a Single RTP Session}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 8860: Sending Multiple Types of Media in a Single RTP Session — https://4ort.xyz/entity/rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-8860-sending-multiple-types-of-media-in-a-single-rtp-session · Last refreshed: