IETF · RFC · RFC8935
RFC8935 · Push-Based Security Event Token (SET) Delivery Using HTTP Push-Based Security Event Token (SET) Delivery Using HTTP
This specification defines how a Security Event Token (SET) can be delivered to an intended recipient using HTTP POST over TLS. The SET is transmitted in the body of an HTTP POST request to an endpoint operated by the recipient, and the recipient indicates successful or failed transmission via the HTTP response.
IETF · RFC
Официальная английская аннотация This specification defines how a Security Event Token (SET) can be delivered to an intended recipient using HTTP POST over TLS. The SET is transmitted in the body of an HTTP POST request to an endpoint operated by the recipient, and the recipient indicates successful or failed transmission via the HTTP response.
Связи документа
Официальный источник · 2020-11-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": "RFC8935",
"number": 8935,
"title_en": "Push-Based Security Event Token (SET) Delivery Using HTTP",
"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 specification defines how a Security Event Token (SET) can be delivered to an intended recipient using HTTP POST over TLS. The SET is transmitted in the body of an HTTP POST request to an endpoint operated by the recipient, and the recipient indicates successful or failed transmission via the HTTP response.",
"authors": [
"A. Backman",
"M. Jones",
"M. Scurtescu",
"M. Ansari",
"A. Nadalin"
],
"organizations": [],
"publication_date": "2020-11-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": "sec",
"area_ru": "Безопасность",
"working_group": "secevent",
"source_draft": "draft-ietf-secevent-http-push-14",
"page_count": 15,
"doi": "10.17487/RFC8935",
"keywords": [
"JSON Web Token",
"JWT",
"Security Event Token",
"SET",
"Delivery",
"JavaScript Object Notation",
"JSON"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8935/",
"html": "https://www.rfc-editor.org/rfc/rfc8935.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8935.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8935/"
}
}