⌕ Поиск по атласу

IETF · RFC · RFC8471

RFC8471 · The Token Binding Protocol Version 1.0

The Token Binding Protocol Version 1.0

This document specifies version 1.0 of the Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokens to the TLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLS and can be reset by the user at any time.

Официальная английская аннотация

This document specifies version 1.0 of the Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokens to the TLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLS and can be reset by the user at any time.

Связи документа

Официальный источник · 2018-10-01

Полные импортированные сведения карточки
{
  "id": "RFC8471",
  "number": 8471,
  "title_en": "The Token Binding Protocol Version 1.0",
  "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 specifies version 1.0 of the Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokens to the TLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLS and can be reset by the user at any time.",
  "authors": [
    "A. Popov",
    "M. Nystroem",
    "D. Balfanz",
    "J. Hodges"
  ],
  "organizations": [],
  "publication_date": "2018-10-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": "tokbind",
  "source_draft": "draft-ietf-tokbind-protocol-19",
  "page_count": 18,
  "doi": "10.17487/RFC8471",
  "keywords": [
    "Token",
    "cookie",
    "TLS",
    "export",
    "replay"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8471/",
    "html": "https://www.rfc-editor.org/rfc/rfc8471.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8471.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8471/"
  }
}