RFC 3555: MIME Type Registration of RTP Payload Formats

Summary

RFC 3555: MIME Type Registration of RTP Payload Formats is a Request for Comments^[1].

Key Facts

• RFC 3555: MIME Type Registration of RTP Payload Formats's instance of is recorded as MIME Type Registration of RTP Payload Formats — instance of (P31): Request for Comments^[2].
• RFC 3555: MIME Type Registration of RTP Payload Formats's publisher is recorded as MIME Type Registration of RTP Payload Formats — publisher (P123): Internet Engineering Task Force^[3].
• RFC 3555: MIME Type Registration of RTP Payload Formats's DOI is recorded as 10.17487/RFC3555^[4].
• RFC 3555: MIME Type Registration of RTP Payload Formats's language of work or name is recorded as MIME Type Registration of RTP Payload Formats — language of work or name (P407): English^[5].
• RFC 3555: MIME Type Registration of RTP Payload Formats's publication date is recorded as +2003-07-01T00:00:00Z^[6].
• RFC 3555: MIME Type Registration of RTP Payload Formats's RfC ID is recorded as 3555^[7].
• RFC 3555: MIME Type Registration of RTP Payload Formats's main subject is recorded as MIME Type Registration of RTP Payload Formats — main subject (P921): Real-time Transport Protocol^[8].
• RFC 3555: MIME Type Registration of RTP Payload Formats's main subject is recorded as MIME Type Registration of RTP Payload Formats — main subject (P921): media type^[9].
• RFC 3555: MIME Type Registration of RTP Payload Formats's work available at URL is recorded as https://tools.ietf.org/html/rfc3555^[10].
• RFC 3555: MIME Type Registration of RTP Payload Formats's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3555.txt^[11].
• RFC 3555: MIME Type Registration of RTP Payload Formats's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3555.txt^[12].
• RFC 3555: MIME Type Registration of RTP Payload Formats's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3555.txt.pdf^[13].
• RFC 3555: MIME Type Registration of RTP Payload Formats's number of pages is recorded as {'unit': '1', 'amount': '+45'}^[14].
• RFC 3555: MIME Type Registration of RTP Payload Formats's replaced by is recorded as MIME Type Registration of RTP Payload Formats — replaced by (P1366): RFC 4855: Media Type Registration of RTP Payload Formats^[15].
• RFC 3555: MIME Type Registration of RTP Payload Formats's replaced by is recorded as MIME Type Registration of RTP Payload Formats — replaced by (P1366): RFC 4856: Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences^[16].
• RFC 3555: MIME Type Registration of RTP Payload Formats's title is recorded as MIME Type Registration of RTP Payload Formats^[17].
• RFC 3555: MIME Type Registration of RTP Payload Formats's author name string is recorded as S. Casner^[18].
• RFC 3555: MIME Type Registration of RTP Payload Formats's author name string is recorded as P. Hoschka^[19].
• RFC 3555: MIME Type Registration of RTP Payload Formats's amended by is recorded as MIME Type Registration of RTP Payload Formats — amended by (P2567): RFC 3625: The QCP File Format and Media Types for Speech Data^[20].
• RFC 3555: MIME Type Registration of RTP Payload Formats's amended by is recorded as MIME Type Registration of RTP Payload Formats — amended by (P2567): RFC 4629: RTP Payload Format for ITU-T Rec. H.263 Video^[21].
• RFC 3555: MIME Type Registration of RTP Payload Formats's DBLP publication ID is recorded as journals/rfc/rfc3555^[22].

Body

Designation and Status

RFC 3555: MIME Type Registration of RTP Payload Formats's instance of is recorded as MIME Type Registration of RTP Payload Formats — instance of (P31): Request for Comments^[2].