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

IETF · RFC · RFC5998

RFC5998 · An Extension for EAP-Only Authentication in IKEv2

An Extension for EAP-Only Authentication in IKEv2

IKEv2 specifies that Extensible Authentication Protocol (EAP) authentication must be used together with responder authentication based on public key signatures. This is necessary with old EAP methods that provide only unilateral authentication using, e.g., one- time passwords or token cards. This document specifies how EAP methods that provide mutual authentication and key agreement can be used to provide extensible responder authentication for IKEv2 based on methods other than public key signatures. [STANDARDS-TRACK]

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

IKEv2 specifies that Extensible Authentication Protocol (EAP) authentication must be used together with responder authentication based on public key signatures. This is necessary with old EAP methods that provide only unilateral authentication using, e.g., one- time passwords or token cards. This document specifies how EAP methods that provide mutual authentication and key agreement can be used to provide extensible responder authentication for IKEv2 based on methods other than public key signatures. [STANDARDS-TRACK]

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

updates: RFC5996

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

Полные импортированные сведения карточки
{
  "id": "RFC5998",
  "number": 5998,
  "title_en": "An Extension for EAP-Only Authentication in IKEv2",
  "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": "IKEv2 specifies that Extensible Authentication Protocol (EAP) authentication must be used together with responder authentication based on public key signatures. This is necessary with old EAP methods that provide only unilateral authentication using, e.g., one- time passwords or token cards. This document specifies how EAP methods that provide mutual authentication and key agreement can be used to provide extensible responder authentication for IKEv2 based on methods other than public key signatures. [STANDARDS-TRACK]",
  "authors": [
    "P. Eronen",
    "H. Tschofenig",
    "Y. Sheffer"
  ],
  "organizations": [],
  "publication_date": "2010-09-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": "ipsecme",
  "source_draft": "draft-ietf-ipsecme-eap-mutual-05",
  "page_count": 16,
  "doi": "10.17487/RFC5998",
  "keywords": [
    "mutual authentication",
    "password",
    "credentials",
    "AAA",
    "key agreement",
    "channel binding"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5996"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5998/",
    "html": "https://www.rfc-editor.org/rfc/rfc5998.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5998.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5998/"
  }
}