RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port
0 sources
RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port
Summary
RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port is a Request for Comments[1].
Key Facts
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port authored Multiplexing RTP Data and Control Packets on a Single Port — author (P50): Colin Perkins[2].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port authored Multiplexing RTP Data and Control Packets on a Single Port — author (P50): Magnus Westerlund[3].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's instance of is recorded as Multiplexing RTP Data and Control Packets on a Single Port — instance of (P31): Request for Comments[4].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's publisher is recorded as Multiplexing RTP Data and Control Packets on a Single Port — publisher (P123): Internet Engineering Task Force[5].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's based on is recorded as Multiplexing RTP Data and Control Packets on a Single Port — based on (P144): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[6].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's based on is recorded as Multiplexing RTP Data and Control Packets on a Single Port — based on (P144): RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control[7].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's DOI is recorded as 10.17487/RFC5761[8].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's language of work or name is recorded as Multiplexing RTP Data and Control Packets on a Single Port — language of work or name (P407): English[9].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's publication date is recorded as +2010-04-01T00:00:00Z[10].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's RfC ID is recorded as 5761[11].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's work available at URL is recorded as https://tools.ietf.org/html/rfc5761[12].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's work available at URL is recorded as https://tools.ietf.org/rfc/rfc5761.txt[13].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5761.txt[14].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5761.txt.pdf[15].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's number of pages is recorded as {'unit': '1', 'amount': '+13'}[16].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's title is recorded as Multiplexing RTP Data and Control Packets on a Single Port[17].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's amended by is recorded as Multiplexing RTP Data and Control Packets on a Single Port — amended by (P2567): RFC 8035: Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing[18].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's amended by is recorded as Multiplexing RTP Data and Control Packets on a Single Port — amended by (P2567): RFC 8858: Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)[19].
- RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's DBLP publication ID is recorded as journals/rfc/rfc5761[20].
Body
Designation and Status
RFC 5761: Multiplexing RTP Data and Control Packets on a Single Port's instance of is recorded as Multiplexing RTP Data and Control Packets on a Single Port — instance of (P31): Request for Comments[4].