IETF · RFC · RFC3788
RFC3788 · Security Considerations for Signaling Transport (SIGTRAN) Protocols Security Considerations for Signaling Transport (SIGTRAN) Protocols
This document discusses how Transport Layer Security (TLS) and IPsec can be used to secure communication for SIGTRAN protocols. The main goal is to recommend the minimum security means that a SIGTRAN node must implement in order to attain secured communication. The support of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS support is optional. [STANDARDS-TRACK]
IETF · RFC
Официальная английская аннотация This document discusses how Transport Layer Security (TLS) and IPsec can be used to secure communication for SIGTRAN protocols. The main goal is to recommend the minimum security means that a SIGTRAN node must implement in order to attain secured communication. The support of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS support is optional. [STANDARDS-TRACK]
Связи документа
Официальный источник · 2004-06-01
Проверка просрочена
Предлагаемый стандарт
Статус: 16.10.2026, 10:21 МСК
Срок следующей проверки: 17.10.2026, 10:21 МСК
Полный текст не зарегистрирован для автоматической сверки.
Errata: нет записей в успешно полученной базе
История и основания проверки
16.10.2026, 10:21 МСК · rfc-index · changed · HTTP 2004c599b64f95deebb9295a603747e28c7b172b15516b4d7140d35b3c5fec97311
16.10.2026, 10:21 МСК · rfc-errata · changed · HTTP 200e208d511c7450a0c65b6a6cfa47471ac873f0c81442bcb911eaac5a2097a8609
10.10.2026, 18:39 МСК · rfc-index · adapter_changed · HTTP 200d413c804505ea10e4abfabc529e82cbfd950616d85fd71658122beeabf74c73b
10.10.2026, 18:39 МСК · rfc-errata · adapter_changed · HTTP 2009fd444088360c9a55b9d1543eb948d627c9e30ac3d9d9cdc222e5883be7e59ee
10.10.2026, 18:36 МСК · rfc-index · unchanged · HTTP 304d413c804505ea10e4abfabc529e82cbfd950616d85fd71658122beeabf74c73b
10.10.2026, 18:36 МСК · rfc-errata · baseline · HTTP 2009fd444088360c9a55b9d1543eb948d627c9e30ac3d9d9cdc222e5883be7e59ee
10.10.2026, 18:34 МСК · rfc-index · changed · HTTP 200d413c804505ea10e4abfabc529e82cbfd950616d85fd71658122beeabf74c73b
10.10.2026, 18:34 МСК · rfc-errata · error · HTTP 200Empty response or forbidden XML entities
rfc-errata · официальный источник
rfc-index · официальный источник
Полные импортированные сведения карточки {
"id": "RFC3788",
"number": 3788,
"title_en": "Security Considerations for Signaling Transport (SIGTRAN) Protocols",
"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 discusses how Transport Layer Security (TLS) and IPsec can be used to secure communication for SIGTRAN protocols. The main goal is to recommend the minimum security means that a SIGTRAN node must implement in order to attain secured communication. The support of IPsec is mandatory for all nodes running SIGTRAN protocols. TLS support is optional. [STANDARDS-TRACK]",
"authors": [
"J. Loughney",
"M. Tuexen",
"J. Pastor-Balbas"
],
"organizations": [],
"publication_date": "2004-06-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": "sigtran",
"source_draft": "draft-ietf-sigtran-security-03",
"page_count": 13,
"doi": "10.17487/RFC3788",
"keywords": [
"SIGTRAN",
"Signaling Transport",
"Security"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc3788/",
"html": "https://www.rfc-editor.org/rfc/rfc3788.html",
"txt": "https://www.rfc-editor.org/rfc/rfc3788.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc3788/"
}
}