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

IETF · RFC · RFC9751

RFC9751 · Closing the RTP Payload Format Media Types Registry

Closing the RTP Payload Format Media Types Registry

The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA "RTP Payload Format Media Types" registry as recommended by RFC 8088. To simplify the process and rely only on the "Media Types" registry, this document closes the RTP payload- specific registry. In addition, it updates the instruction in RFC 8088 to reflect this change.

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

The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA "RTP Payload Format Media Types" registry as recommended by RFC 8088. To simplify the process and rely only on the "Media Types" registry, this document closes the RTP payload- specific registry. In addition, it updates the instruction in RFC 8088 to reflect this change.

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

updates: RFC8088

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

Полные импортированные сведения карточки
{
  "id": "RFC9751",
  "number": 9751,
  "title_en": "Closing the RTP Payload Format Media Types Registry",
  "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": "The working group process and the authors of RTP payload formats have sometimes failed to ensure that the media types are registered in the IANA \"RTP Payload Format Media Types\" registry as recommended by RFC 8088. To simplify the process and rely only on the \"Media Types\" registry, this document closes the RTP payload- specific registry. In addition, it updates the instruction in RFC 8088 to reflect this change.",
  "authors": [
    "M. Westerlund"
  ],
  "organizations": [],
  "publication_date": "2025-03-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-rtp-payload-registry-05",
  "page_count": 6,
  "doi": "10.17487/RFC9751",
  "keywords": [],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC8088"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9751/",
    "html": "https://www.rfc-editor.org/rfc/rfc9751.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9751.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9751/"
  }
}