RFC9071 · RTP-Mixer Formatting of Multiparty Real-Time Text

{
  "id": "RFC9071",
  "number": 9071,
  "title_en": "RTP-Mixer Formatting of Multiparty Real-Time Text",
  "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 enhancements of real-time text (as specified in RFC 4103) suitable for mixing in a centralized conference model, enabling source identification and rapidly interleaved transmission of text from different sources. The intended use is for real-time text mixers and participant endpoints capable of providing an efficient presentation or other treatment of a multiparty real-time text session. The specified mechanism builds on the standard use of the Contributing Source (CSRC) list in the Real-time Transport Protocol (RTP) packet for source identification. The method makes use of the same \"text/t140\" and \"text/red\" formats as for two-party sessions. Solutions using multiple RTP streams in the same RTP session are briefly mentioned, as they could have some benefits over the RTP-mixer model. The RTP-mixer model was selected to be used for the fully specified solution in this document because it can be applied to a wide range of existing RTP implementations. A capability exchange is specified so that it can be verified that a mixer and a participant can handle the multiparty-coded real-time text stream using the RTP-mixer method. The capability is indicated by the use of a Session Description Protocol (SDP) (RFC 8866) media attribute, \"rtt-mixer\". This document updates RFC 4103 (\"RTP Payload for Text Conversation\"). A specification for how a mixer can format text for the case when the endpoint is not multiparty aware is also provided.",
  "authors": [
    "G. Hellström"
  ],
  "organizations": [],
  "publication_date": "2021-07-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-multi-party-rtt-mix-20",
  "page_count": 35,
  "doi": "10.17487/RFC9071",
  "keywords": [
    "conference",
    "bridge",
    "SIP"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC4103"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9071/",
    "html": "https://www.rfc-editor.org/rfc/rfc9071.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9071.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9071/"
  }
}