
datatracker.ietf.org/doc/html/rfc3550
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
4- 49 links todatatracker.ietf.org
- 5 links towww.rfc-editor.org
- 1 link togithub.com
- 1 link tomailarchive.ietf.org
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/html/rfc3550
RFC 3550: RTP: A Transport Protocol for Real-Time Applications
RTP: A Transport Protocol for Real-Time Applications (RFC 3550, )
Bing
RFC 3550: RTP: A Transport Protocol for Real-Time Applications
https://datatracker.ietf.org/doc/html/rfc3550
RTP: A Transport Protocol for Real-Time Applications (RFC 3550, )
DuckDuckGo

RFC 3550: RTP: A Transport Protocol for Real-Time Applications
RTP: A Transport Protocol for Real-Time Applications (RFC 3550, )
General Meta Tags
12- titleRFC 3550 - RTP: A Transport Protocol for Real-Time Applications
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- descriptionRTP: A Transport Protocol for Real-Time Applications (RFC 3550, )
Open Graph Meta Tags
10- og:titleRFC 3550: RTP: A Transport Protocol for Real-Time Applications
- og:urlhttps://datatracker.ietf.org/doc/html/rfc3550
- og:site_nameIETF Datatracker
- og:descriptionThis memorandum describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. Most of the text in this memorandum is identical to RFC 1889 which it obsoletes. There are no changes in the packet formats on the wire, only changes to the rules and algorithms governing how the protocol is used. The biggest change is an enhancement to the scalable timer algorithm for calculating when to send RTCP packets in order to minimize transmission in excess of the intended rate when many participants join a session simultaneously. [STANDARDS-TRACK]
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
12- alternate/feed/document-changes/rfc3550/
- apple-touch-iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/html/rfc3550
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png
Emails
5- hgs%40cs.columbia.edu
- casner%40acm.org
- ron_frederick%40symantec.com
- vanj%40google.com
- [email protected]?subject=rfc3550
Links
56- https://datatracker.ietf.org/doc/draft-ietf-avt-rtp-new/12
- https://datatracker.ietf.org/doc/html/bcp11
- https://datatracker.ietf.org/doc/html/bcp14
- https://datatracker.ietf.org/doc/html/bcp41
- https://datatracker.ietf.org/doc/html/draft-ietf-avt-rtp-new-12