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

IETF · RFC · RFC8918

RFC8918 · Invalid TLV Handling in IS-IS

Invalid TLV Handling in IS-IS

The key to the extensibility of the Intermediate System to Intermediate System (IS-IS) protocol has been the handling of unsupported and/or invalid Type-Length-Value (TLV) tuples. Although there are explicit statements in existing specifications, deployment experience has shown that there are inconsistencies in the behavior when a TLV that is disallowed in a particular Protocol Data Unit (PDU) is received. This document discusses such cases and makes the correct behavior explicit in order to ensure that interoperability is maximized. This document updates RFCs 5305 and 6232.

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

The key to the extensibility of the Intermediate System to Intermediate System (IS-IS) protocol has been the handling of unsupported and/or invalid Type-Length-Value (TLV) tuples. Although there are explicit statements in existing specifications, deployment experience has shown that there are inconsistencies in the behavior when a TLV that is disallowed in a particular Protocol Data Unit (PDU) is received. This document discusses such cases and makes the correct behavior explicit in order to ensure that interoperability is maximized. This document updates RFCs 5305 and 6232.

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

updates: RFC5305, RFC6232

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

Полные импортированные сведения карточки
{
  "id": "RFC8918",
  "number": 8918,
  "title_en": "Invalid TLV Handling in 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": "The key to the extensibility of the Intermediate System to Intermediate System (IS-IS) protocol has been the handling of unsupported and/or invalid Type-Length-Value (TLV) tuples. Although there are explicit statements in existing specifications, deployment experience has shown that there are inconsistencies in the behavior when a TLV that is disallowed in a particular Protocol Data Unit (PDU) is received. This document discusses such cases and makes the correct behavior explicit in order to ensure that interoperability is maximized. This document updates RFCs 5305 and 6232.",
  "authors": [
    "L. Ginsberg",
    "P. Wells",
    "T. Li",
    "T. Przygienda",
    "S. Hegde"
  ],
  "organizations": [],
  "publication_date": "2020-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": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "lsr",
  "source_draft": "draft-ietf-lsr-isis-invalid-tlv-03",
  "page_count": 8,
  "doi": "10.17487/RFC8918",
  "keywords": [
    "TLV",
    "IS-IS"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5305",
      "RFC6232"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8918/",
    "html": "https://www.rfc-editor.org/rfc/rfc8918.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8918.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8918/"
  }
}