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

IETF · RFC · RFC5169

RFC5169 · Handover Key Management and Re-Authentication Problem Statement

Handover Key Management and Re-Authentication Problem Statement

This document describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community.

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

This document describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC5169",
  "number": 5169,
  "title_en": "Handover Key Management and Re-Authentication Problem Statement",
  "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 describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community.",
  "authors": [
    "T. Clancy",
    "M. Nakhjiri",
    "V. Narayanan",
    "L. Dondeti"
  ],
  "organizations": [],
  "publication_date": "2008-03-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "sec",
  "area_ru": "Безопасность",
  "working_group": "hokey",
  "source_draft": "draft-ietf-hokey-reauth-ps-09",
  "page_count": 15,
  "doi": "10.17487/RFC5169",
  "keywords": [
    "hokey",
    "handover key management",
    "fast re-authentication",
    "mobility"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5169/",
    "html": "https://www.rfc-editor.org/rfc/rfc5169.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5169.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5169/"
  }
}