⌕ Поиск по атласу

IETF · RFC · RFC3551

RFC3551 · RTP Profile for Audio and Video Conferences with Minimal Control

RTP Profile for Audio and Video Conferences with Minimal Control

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]

Официальная английская аннотация

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]

Связи документа

obsoletes: RFC1890

updated_by: RFC5761, RFC7007, RFC8860

is_also: STD65

Официальный источник · 2003-07-01

Полные импортированные сведения карточки
{
  "id": "RFC3551",
  "number": 3551,
  "title_en": "RTP Profile for Audio and Video Conferences with Minimal Control",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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]",
  "authors": [
    "H. Schulzrinne",
    "S. Casner"
  ],
  "organizations": [],
  "publication_date": "2003-07-01",
  "current_status": "INTERNET STANDARD",
  "current_status_ru": "Стандарт Интернета",
  "publication_status": "DRAFT STANDARD",
  "publication_status_ru": "Проект стандарта (устаревшая стадия)",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rai",
  "area_ru": "rai",
  "working_group": "avt",
  "source_draft": "draft-ietf-avt-profile-new-13",
  "page_count": 44,
  "doi": "10.17487/RFC3551",
  "keywords": [
    "RTP-AV",
    "Real-time Transport Protocol",
    "audio",
    "video",
    "end-to-end",
    "network",
    "conference"
  ],
  "formats": [
    "TXT",
    "PS",
    "PDF",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC1890"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC5761",
      "RFC7007",
      "RFC8860"
    ],
    "is_also": [
      "STD65"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3551/",
    "html": "https://www.rfc-editor.org/rfc/rfc3551.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3551.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3551/"
  }
}