RFC 4587: RTP Payload Format for H.261 Video Streams
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 4587: RTP Payload Format for H.261 Video Streams
Summary
RFC 4587: RTP Payload Format for H.261 Video Streams is a Request for Comments[1].
Key Facts
- RFC 4587: RTP Payload Format for H.261 Video Streams authored RTP Payload Format for H.261 Video Streams — author (P50): Roni Even[2].
- RFC 4587: RTP Payload Format for H.261 Video Streams's instance of is recorded as RTP Payload Format for H.261 Video Streams — instance of (P31): Request for Comments[3].
- RFC 4587: RTP Payload Format for H.261 Video Streams's publisher is recorded as RTP Payload Format for H.261 Video Streams — publisher (P123): Internet Engineering Task Force[4].
- RFC 4587: RTP Payload Format for H.261 Video Streams's DOI is recorded as 10.17487/RFC4587[5].
- RFC 4587: RTP Payload Format for H.261 Video Streams's language of work or name is recorded as RTP Payload Format for H.261 Video Streams — language of work or name (P407): English[6].
- RFC 4587: RTP Payload Format for H.261 Video Streams's publication date is recorded as +2006-08-01T00:00:00Z[7].
- RFC 4587: RTP Payload Format for H.261 Video Streams's RfC ID is recorded as 4587[8].
- RFC 4587: RTP Payload Format for H.261 Video Streams's work available at URL is recorded as https://tools.ietf.org/html/rfc4587[9].
- RFC 4587: RTP Payload Format for H.261 Video Streams's work available at URL is recorded as https://tools.ietf.org/rfc/rfc4587.txt[10].
- RFC 4587: RTP Payload Format for H.261 Video Streams's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc4587.txt[11].
- RFC 4587: RTP Payload Format for H.261 Video Streams's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc4587.txt.pdf[12].
- RFC 4587: RTP Payload Format for H.261 Video Streams's number of pages is recorded as {'unit': '1', 'amount': '+17'}[13].
- RFC 4587: RTP Payload Format for H.261 Video Streams's replaces is recorded as RTP Payload Format for H.261 Video Streams — replaces (P1365): RFC 2032: RTP Payload Format for H.261 Video Streams[14].
- RFC 4587: RTP Payload Format for H.261 Video Streams's title is recorded as RTP Payload Format for H.261 Video Streams[15].
- RFC 4587: RTP Payload Format for H.261 Video Streams's DBLP publication ID is recorded as journals/rfc/rfc4587[16].
Body
Designation and Status
RFC 4587: RTP Payload Format for H.261 Video Streams's instance of is recorded as RTP Payload Format for H.261 Video Streams — instance of (P31): Request for Comments[3].