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

IETF · RFC · RFC9666

RFC9666 · Area Proxy for IS-IS

Area Proxy for IS-IS

Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues. To avoid such issues, this document discusses extensions to the IS-IS routing protocol that allow Level 1 (L1) areas to provide transit but only inject an abstraction of the Level 1 topology into Level 2 (L2). Each Level 1 area is represented as a single Level 2 node, thereby enabling a greater scale.

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

Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues. To avoid such issues, this document discusses extensions to the IS-IS routing protocol that allow Level 1 (L1) areas to provide transit but only inject an abstraction of the Level 1 topology into Level 2 (L2). Each Level 1 area is represented as a single Level 2 node, thereby enabling a greater scale.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC9666",
  "number": 9666,
  "title_en": "Area Proxy for IS-IS",
  "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": "Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their internal topologies to each other, thereby leading to scaling issues. To avoid such issues, this document discusses extensions to the IS-IS routing protocol that allow Level 1 (L1) areas to provide transit but only inject an abstraction of the Level 1 topology into Level 2 (L2). Each Level 1 area is represented as a single Level 2 node, thereby enabling a greater scale.",
  "authors": [
    "T. Li",
    "S. Chen",
    "V. Ilangovan",
    "G. Mishra"
  ],
  "organizations": [],
  "publication_date": "2024-10-01",
  "current_status": "EXPERIMENTAL",
  "current_status_ru": "Экспериментальный",
  "publication_status": "EXPERIMENTAL",
  "publication_status_ru": "Экспериментальный",
  "lifecycle": "experimental",
  "lifecycle_ru": "Экспериментальный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "lsr",
  "source_draft": "draft-ietf-lsr-isis-area-proxy-12",
  "page_count": 17,
  "doi": "10.17487/RFC9666",
  "keywords": [
    "datacenter",
    "IGP",
    "routing",
    "topology",
    "level",
    "abstraction",
    "IS-IS",
    "proxy"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9666/",
    "html": "https://www.rfc-editor.org/rfc/rfc9666.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9666.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9666/"
  }
}