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

IETF · RFC · RFC9324

RFC9324 · Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh

Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh

A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with respect to new RPKI data.

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

A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with respect to new RPKI data.

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

updates: RFC8481

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

Полные импортированные сведения карточки
{
  "id": "RFC9324",
  "number": 9324,
  "title_en": "Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh",
  "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": "A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with respect to new RPKI data.",
  "authors": [
    "R. Bush",
    "K. Patel",
    "P. Smith",
    "M. Tinka"
  ],
  "organizations": [],
  "publication_date": "2022-12-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-rov-no-rr-08",
  "page_count": 7,
  "doi": "10.17487/RFC9324",
  "keywords": [
    "bgp"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC8481"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9324/",
    "html": "https://www.rfc-editor.org/rfc/rfc9324.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9324.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9324/"
  }
}