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

IETF · RFC · RFC8481

RFC8481 · Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)

Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)

Deployment of BGP origin validation based on Resource Public Key Infrastructure (RPKI) is hampered by, among other things, vendor misimplementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those misimplementations; it thus updates RFC 6811 by clarifying that all prefixes should have their validation state set and that policy must not be applied without operator configuration.

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

Deployment of BGP origin validation based on Resource Public Key Infrastructure (RPKI) is hampered by, among other things, vendor misimplementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those misimplementations; it thus updates RFC 6811 by clarifying that all prefixes should have their validation state set and that policy must not be applied without operator configuration.

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

updates: RFC6811

updated_by: RFC9324

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

Полные импортированные сведения карточки
{
  "id": "RFC8481",
  "number": 8481,
  "title_en": "Clarifications to BGP Origin Validation Based on 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": "Deployment of BGP origin validation based on Resource Public Key Infrastructure (RPKI) is hampered by, among other things, vendor misimplementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those misimplementations; it thus updates RFC 6811 by clarifying that all prefixes should have their validation state set and that policy must not be applied without operator configuration.",
  "authors": [
    "R. Bush"
  ],
  "organizations": [],
  "publication_date": "2018-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "sidrops",
  "source_draft": "draft-ietf-sidrops-ov-clarify-05",
  "page_count": 5,
  "doi": "10.17487/RFC8481",
  "keywords": [
    "security",
    "routing"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC6811"
    ],
    "updated_by": [
      "RFC9324"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8481/",
    "html": "https://www.rfc-editor.org/rfc/rfc8481.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8481.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8481/"
  }
}