RFC7329 · A Session Identifier for the Session Initiation Protocol (SIP)
A Session Identifier for the Session Initiation Protocol (SIP)
There is a need for having a globally unique session identifier for the same SIP session that can be consistently maintained across SIP Proxies, Back-to-Back User Agents (B2BUAs), and other SIP middleboxes, for the purpose of troubleshooting. This document proposes a new SIP header to carry such a value: Session-ID. The mechanism defined in this document has been widely deployed, and is being followed in a backward-compatible fashion for a new Standards Track document produced by the INSIPID Working Group.
IETF · RFCОфициальная английская аннотация
There is a need for having a globally unique session identifier for the same SIP session that can be consistently maintained across SIP Proxies, Back-to-Back User Agents (B2BUAs), and other SIP middleboxes, for the purpose of troubleshooting. This document proposes a new SIP header to carry such a value: Session-ID. The mechanism defined in this document has been widely deployed, and is being followed in a backward-compatible fashion for a new Standards Track document produced by the INSIPID Working Group.
{
"id": "RFC7329",
"number": 7329,
"title_en": "A Session Identifier for the Session Initiation Protocol (SIP)",
"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": "There is a need for having a globally unique session identifier for the same SIP session that can be consistently maintained across SIP Proxies, Back-to-Back User Agents (B2BUAs), and other SIP middleboxes, for the purpose of troubleshooting. This document proposes a new SIP header to carry such a value: Session-ID. The mechanism defined in this document has been widely deployed, and is being followed in a backward-compatible fashion for a new Standards Track document produced by the INSIPID Working Group.",
"authors": [
"H. Kaplan"
],
"organizations": [],
"publication_date": "2014-08-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "superseded",
"lifecycle_ru": "Заменён",
"stream": "IETF",
"stream_ru": "IETF",
"area": "",
"area_ru": "",
"working_group": "NON WORKING GROUP",
"source_draft": "draft-kaplan-insipid-session-id-04",
"page_count": 17,
"doi": "10.17487/RFC7329",
"keywords": [],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [
"RFC7989"
],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc7329/",
"html": "https://www.rfc-editor.org/rfc/rfc7329.html",
"txt": "https://www.rfc-editor.org/rfc/rfc7329.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc7329/"
}
}