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

IETF · RFC · RFC6232

RFC6232 · Purge Originator Identification TLV for IS-IS

Purge Originator Identification TLV for IS-IS

At present, an IS-IS purge does not contain any information identifying the Intermediate System (IS) that generates the purge. This makes it difficult to locate the source IS. To address this issue, this document defines a TLV to be added to purges to record the system ID of the IS generating it. Since normal Link State Protocol Data Unit (LSP) flooding does not change LSP contents, this TLV should propagate with the purge. This document updates RFC 5301, RFC 5304, and RFC 5310. [STANDARDS-TRACK]

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

At present, an IS-IS purge does not contain any information identifying the Intermediate System (IS) that generates the purge. This makes it difficult to locate the source IS. To address this issue, this document defines a TLV to be added to purges to record the system ID of the IS generating it. Since normal Link State Protocol Data Unit (LSP) flooding does not change LSP contents, this TLV should propagate with the purge. This document updates RFC 5301, RFC 5304, and RFC 5310. [STANDARDS-TRACK]

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

updates: RFC5301, RFC5304, RFC5310

updated_by: RFC8918

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

Полные импортированные сведения карточки
{
  "id": "RFC6232",
  "number": 6232,
  "title_en": "Purge Originator Identification TLV 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": "At present, an IS-IS purge does not contain any information identifying the Intermediate System (IS) that generates the purge. This makes it difficult to locate the source IS. To address this issue, this document defines a TLV to be added to purges to record the system ID of the IS generating it. Since normal Link State Protocol Data Unit (LSP) flooding does not change LSP contents, this TLV should propagate with the purge. This document updates RFC 5301, RFC 5304, and RFC 5310. [STANDARDS-TRACK]",
  "authors": [
    "F. Wei",
    "Y. Qin",
    "Z. Li",
    "T. Li",
    "J. Dong"
  ],
  "organizations": [],
  "publication_date": "2011-05-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": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "isis",
  "source_draft": "draft-ietf-isis-purge-tlv-05",
  "page_count": 6,
  "doi": "10.17487/RFC6232",
  "keywords": [
    "Purge Originator Identification",
    "IIH:n",
    "LSP:y",
    "SNP:n",
    "Purge:y"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5301",
      "RFC5304",
      "RFC5310"
    ],
    "updated_by": [
      "RFC8918"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6232/",
    "html": "https://www.rfc-editor.org/rfc/rfc6232.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6232.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6232/"
  }
}