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

IETF · RFC · RFC8285

RFC8285 · A General Mechanism for RTP Header Extensions

A General Mechanism for RTP Header Extensions

This document provides a general mechanism to use the header extension feature of RTP (the Real-time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is decentralized. The actual extensions in use in a session are signaled in the setup information for that session. This document obsoletes RFC 5285.

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

This document provides a general mechanism to use the header extension feature of RTP (the Real-time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is decentralized. The actual extensions in use in a session are signaled in the setup information for that session. This document obsoletes RFC 5285.

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

obsoletes: RFC5285

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

Полные импортированные сведения карточки
{
  "id": "RFC8285",
  "number": 8285,
  "title_en": "A General Mechanism for RTP Header Extensions",
  "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 provides a general mechanism to use the header extension feature of RTP (the Real-time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is decentralized. The actual extensions in use in a session are signaled in the setup information for that session. This document obsoletes RFC 5285.",
  "authors": [
    "D. Singer",
    "H. Desineni",
    "R. Even"
  ],
  "organizations": [],
  "publication_date": "2017-10-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "avtcore",
  "source_draft": "draft-ietf-avtcore-rfc5285-bis-14",
  "page_count": 25,
  "doi": "10.17487/RFC8285",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC5285"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8285/",
    "html": "https://www.rfc-editor.org/rfc/rfc8285.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8285.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8285/"
  }
}