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

IETF · RFC · RFC9455

RFC9455 · Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes

Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes

When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing multiple IP prefixes and recommends that each ROA contain a single IP prefix.

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

When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing multiple IP prefixes and recommends that each ROA contain a single IP prefix.

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

is_also: BCP238

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

Полные импортированные сведения карточки
{
  "id": "RFC9455",
  "number": 9455,
  "title_en": "Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes",
  "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": "When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing multiple IP prefixes and recommends that each ROA contain a single IP prefix.",
  "authors": [
    "Z. Yan",
    "R. Bush",
    "G. Geng",
    "T. de Kock",
    "J. Yao"
  ],
  "organizations": [],
  "publication_date": "2023-08-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "sidrops",
  "source_draft": "draft-ietf-sidrops-roa-considerations-08",
  "page_count": 6,
  "doi": "10.17487/RFC9455",
  "keywords": [
    "ROA",
    "Route Origin Authorization"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [
      "BCP238"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9455/",
    "html": "https://www.rfc-editor.org/rfc/rfc9455.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9455.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9455/"
  }
}