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

IETF · RFC · RFC6489

RFC6489 · Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)

Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)

This document describes how a Certification Authority (CA) in the Resource Public Key Infrastructure (RPKI) performs a planned rollover of its key pair. This document also notes the implications of this key rollover procedure for relying parties (RPs). In general, RPs are expected to maintain a local cache of the objects that have been published in the RPKI repository, and thus the way in which a CA performs key rollover impacts RPs. This memo documents an Internet Best Current Practice.

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

This document describes how a Certification Authority (CA) in the Resource Public Key Infrastructure (RPKI) performs a planned rollover of its key pair. This document also notes the implications of this key rollover procedure for relying parties (RPs). In general, RPs are expected to maintain a local cache of the objects that have been published in the RPKI repository, and thus the way in which a CA performs key rollover impacts RPs. This memo documents an Internet Best Current Practice.

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

is_also: BCP174

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

Полные импортированные сведения карточки
{
  "id": "RFC6489",
  "number": 6489,
  "title_en": "Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI)",
  "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 how a Certification Authority (CA) in the Resource Public Key Infrastructure (RPKI) performs a planned rollover of its key pair. This document also notes the implications of this key rollover procedure for relying parties (RPs). In general, RPs are expected to maintain a local cache of the objects that have been published in the RPKI repository, and thus the way in which a CA performs key rollover impacts RPs. This memo documents an Internet Best Current Practice.",
  "authors": [
    "G. Huston",
    "G. Michaelson",
    "S. Kent"
  ],
  "organizations": [],
  "publication_date": "2012-02-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "sidr",
  "source_draft": "draft-ietf-sidr-keyroll-08",
  "page_count": 10,
  "doi": "10.17487/RFC6489",
  "keywords": [
    "RPKI"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP174"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6489/",
    "html": "https://www.rfc-editor.org/rfc/rfc6489.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6489.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6489/"
  }
}