RFC 4855: Media Type Registration of RTP Payload Formats
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 4855: Media Type Registration of RTP Payload Formats
Summary
RFC 4855: Media Type Registration of RTP Payload Formats is a Request for Comments[1].
Key Facts
- RFC 4855: Media Type Registration of RTP Payload Formats's instance of is recorded as Media Type Registration of RTP Payload Formats — instance of (P31): Request for Comments[2].
- RFC 4855: Media Type Registration of RTP Payload Formats's publisher is recorded as Media Type Registration of RTP Payload Formats — publisher (P123): Internet Engineering Task Force[3].
- RFC 4855: Media Type Registration of RTP Payload Formats's DOI is recorded as 10.17487/RFC4855[4].
- RFC 4855: Media Type Registration of RTP Payload Formats's language of work or name is recorded as Media Type Registration of RTP Payload Formats — language of work or name (P407): English[5].
- RFC 4855: Media Type Registration of RTP Payload Formats's publication date is recorded as +2007-02-01T00:00:00Z[6].
- RFC 4855: Media Type Registration of RTP Payload Formats's RfC ID is recorded as 4855[7].
- RFC 4855: Media Type Registration of RTP Payload Formats's main subject is recorded as Media Type Registration of RTP Payload Formats — main subject (P921): Real-time Transport Protocol[8].
- RFC 4855: Media Type Registration of RTP Payload Formats's main subject is recorded as Media Type Registration of RTP Payload Formats — main subject (P921): media type[9].
- RFC 4855: Media Type Registration of RTP Payload Formats's work available at URL is recorded as https://tools.ietf.org/html/rfc4855[10].
- RFC 4855: Media Type Registration of RTP Payload Formats's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4855.txt[11].
- RFC 4855: Media Type Registration of RTP Payload Formats's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4855.txt[12].
- RFC 4855: Media Type Registration of RTP Payload Formats's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4855.txt.pdf[13].
- RFC 4855: Media Type Registration of RTP Payload Formats's number of pages is recorded as {'unit': '1', 'amount': '+11'}[14].
- RFC 4855: Media Type Registration of RTP Payload Formats's replaces is recorded as Media Type Registration of RTP Payload Formats — replaces (P1365): RFC 3555: MIME Type Registration of RTP Payload Formats[15].
- RFC 4855: Media Type Registration of RTP Payload Formats's title is recorded as Media Type Registration of RTP Payload Formats[16].
- RFC 4855: Media Type Registration of RTP Payload Formats's author name string is recorded as S. Casner[17].
- RFC 4855: Media Type Registration of RTP Payload Formats's amended by is recorded as Media Type Registration of RTP Payload Formats — amended by (P2567): RFC 8851: RTP Payload Format Restrictions[18].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 4288: Media Type Specifications and Registration Procedures[19].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 3550: RTP: A Transport Protocol for Real-Time Applications[20].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 2119: Key words for use in RFCs to Indicate Requirement Levels[21].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control[22].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 4566: SDP: Session Description Protocol[23].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies[24].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types[25].
- RFC 4855: Media Type Registration of RTP Payload Formats's cites work is recorded as Media Type Registration of RTP Payload Formats — cites work (P2860): RFC 4856: Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences[26].
Body
Designation and Status
RFC 4855: Media Type Registration of RTP Payload Formats's instance of is recorded as Media Type Registration of RTP Payload Formats — instance of (P31): Request for Comments[2].