RFC7202 · Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
This memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.
IETF · RFCОфициальная английская аннотация
This memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.
{
"id": "RFC7202",
"number": 7202,
"title_en": "Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution",
"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 memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.",
"authors": [
"C. Perkins",
"M. Westerlund"
],
"organizations": [],
"publication_date": "2014-04-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IETF",
"stream_ru": "IETF",
"area": "wit",
"area_ru": "Веб и транспорт Интернета",
"working_group": "avtcore",
"source_draft": "draft-ietf-avt-srtp-not-mandatory-16",
"page_count": 10,
"doi": "10.17487/RFC7202",
"keywords": [
"SRTP",
"RTP Profile",
"Payload Format"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc7202/",
"html": "https://www.rfc-editor.org/rfc/rfc7202.html",
"txt": "https://www.rfc-editor.org/rfc/rfc7202.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc7202/"
}
}