RFC 8108: Sending Multiple RTP Streams in a Single RTP Session
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 8108: Sending Multiple RTP Streams in a Single RTP Session
Summary
RFC 8108: Sending Multiple RTP Streams in a Single RTP Session is a Request for Comments[1].
Key Facts
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session authored Sending Multiple RTP Streams in a Single RTP Session — author (P50): Colin Perkins[2].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session authored Sending Multiple RTP Streams in a Single RTP Session — author (P50): Qin Wu[3].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session authored Sending Multiple RTP Streams in a Single RTP Session — author (P50): Magnus Westerlund[4].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's instance of is recorded as Sending Multiple RTP Streams in a Single RTP Session — instance of (P31): Request for Comments[5].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's publisher is recorded as Sending Multiple RTP Streams in a Single RTP Session — publisher (P123): Internet Engineering Task Force[6].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's based on is recorded as Sending Multiple RTP Streams in a Single RTP Session — based on (P144): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[7].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's based on is recorded as Sending Multiple RTP Streams in a Single RTP Session — based on (P144): RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)[8].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's DOI is recorded as 10.17487/RFC8108[9].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's language of work or name is recorded as Sending Multiple RTP Streams in a Single RTP Session — language of work or name (P407): English[10].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's publication date is recorded as +2017-03-01T00:00:00Z[11].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's RfC ID is recorded as 8108[12].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's work available at URL is recorded as https://tools.ietf.org/html/rfc8108[13].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's work available at URL is recorded as https://tools.ietf.org/rfc/rfc8108.txt[14].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc8108.txt[15].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc8108.txt.pdf[16].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's number of pages is recorded as {'unit': '1', 'amount': '+29'}[17].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's title is recorded as Sending Multiple RTP Streams in a Single RTP Session[18].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's author name string is recorded as J. Lennox[19].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 2119: Key words for use in RFCs to Indicate Requirement Levels[20].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[21].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 3711: The Secure Real-time Transport Protocol (SRTP)[22].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)[23].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 5124: Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)[24].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 5506: Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and Consequences[25].
- RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's cites work is recorded as Sending Multiple RTP Streams in a Single RTP Session — cites work (P2860): RFC 3390: Increasing TCP's Initial Window[26].
Body
Designation and Status
RFC 8108: Sending Multiple RTP Streams in a Single RTP Session's instance of is recorded as Sending Multiple RTP Streams in a Single RTP Session — instance of (P31): Request for Comments[5].