datatracker.ietf.org/doc/draft-ietf-avt-profile-new

Preview meta tags from the datatracker.ietf.org website.

Linked Hostnames

10

Thumbnail

Search Engine Appearance

Google

https://datatracker.ietf.org/doc/draft-ietf-avt-profile-new

RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control

RTP Profile for Audio and Video Conferences with Minimal Control (RFC 3551, July 2003)



Bing

RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control

https://datatracker.ietf.org/doc/draft-ietf-avt-profile-new

RTP Profile for Audio and Video Conferences with Minimal Control (RFC 3551, July 2003)



DuckDuckGo

https://datatracker.ietf.org/doc/draft-ietf-avt-profile-new

RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control

RTP Profile for Audio and Video Conferences with Minimal Control (RFC 3551, July 2003)

  • General Meta Tags

    10
    • title
      RFC 3551 - RTP Profile for Audio and Video Conferences with Minimal Control
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • article:section
      IETF - Internet Engineering Task Force
  • Open Graph Meta Tags

    10
    • og:title
      RFC 3551: RTP Profile for Audio and Video Conferences with Minimal Control
    • og:url
      https://datatracker.ietf.org/doc/rfc3551/
    • og:site_name
      IETF Datatracker
    • og:description
      This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. [STANDARDS-TRACK]
    • og:type
      article
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

    13
    • alternate
      /feed/document-changes/rfc3551/
    • apple-touch-icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/rfc3551/
    • icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png

Emails

6

Links

95