RFC4855 · Media Type Registration of RTP Payload Formats

{
  "id": "RFC4855",
  "number": 4855,
  "title_en": "Media Type Registration of RTP Payload Formats",
  "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 specifies the procedure to register RTP payload formats as audio, video, or other media subtype names. This is useful in a text-based format description or control protocol to identify the type of an RTP transmission. [STANDARDS-TRACK]",
  "authors": [
    "S. Casner"
  ],
  "organizations": [],
  "publication_date": "2007-02-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": "rai",
  "area_ru": "rai",
  "working_group": "avt",
  "source_draft": "draft-ietf-avt-rfc3555bis-05",
  "page_count": 11,
  "doi": "10.17487/RFC4855",
  "keywords": [
    "realtime transport protocol",
    "multipurpose internet mail extensions"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC3555"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8851"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4855/",
    "html": "https://www.rfc-editor.org/rfc/rfc4855.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4855.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4855/"
  }
}