RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call
Summary
RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call is a Request for Comments[1].
Key Facts
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's instance of is recorded as RTP Payload Format for a 64 kbit/s Transparent Call — instance of (P31): Request for Comments[2].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's publisher is recorded as RTP Payload Format for a 64 kbit/s Transparent Call — publisher (P123): Internet Engineering Task Force[3].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's DOI is recorded as 10.17487/RFC4040[4].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's language of work or name is recorded as RTP Payload Format for a 64 kbit/s Transparent Call — language of work or name (P407): English[5].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's publication date is recorded as +2005-04-01T00:00:00Z[6].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's RfC ID is recorded as 4040[7].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's work available at URL is recorded as https://tools.ietf.org/html/rfc4040[8].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4040.txt[9].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4040.txt[10].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4040.txt.pdf[11].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's number of pages is recorded as {'unit': '1', 'amount': '+8'}[12].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's title is recorded as RTP Payload Format for a 64 kbit/s Transparent Call[13].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's author name string is recorded as R. Kreuter[14].
- RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's DBLP publication ID is recorded as journals/rfc/rfc4040[15].
Body
Designation and Status
RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call's instance of is recorded as RTP Payload Format for a 64 kbit/s Transparent Call — instance of (P31): Request for Comments[2].