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

IETF · RFC · RFC8978

RFC8978 · Reaction of IPv6 Stateless Address Autoconfiguration (SLAAC) to Flash-Renumbering Events

Reaction of IPv6 Stateless Address Autoconfiguration (SLAAC) to Flash-Renumbering Events

In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit and reliable signaling of that condition (such as when a Customer Edge router crashes and reboots without knowledge of the previously employed prefixes), hosts on the local network may continue using stale prefixes for an unacceptably long time (on the order of several days), thus resulting in connectivity problems. This document describes this issue and discusses operational workarounds that may help to improve network robustness. Additionally, it highlights areas where further work may be needed.

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

In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit and reliable signaling of that condition (such as when a Customer Edge router crashes and reboots without knowledge of the previously employed prefixes), hosts on the local network may continue using stale prefixes for an unacceptably long time (on the order of several days), thus resulting in connectivity problems. This document describes this issue and discusses operational workarounds that may help to improve network robustness. Additionally, it highlights areas where further work may be needed.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8978",
  "number": 8978,
  "title_en": "Reaction of IPv6 Stateless Address Autoconfiguration (SLAAC) to Flash-Renumbering Events",
  "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": "In scenarios where network configuration information related to IPv6 prefixes becomes invalid without any explicit and reliable signaling of that condition (such as when a Customer Edge router crashes and reboots without knowledge of the previously employed prefixes), hosts on the local network may continue using stale prefixes for an unacceptably long time (on the order of several days), thus resulting in connectivity problems. This document describes this issue and discusses operational workarounds that may help to improve network robustness. Additionally, it highlights areas where further work may be needed.",
  "authors": [
    "F. Gont",
    "J. Žorž",
    "R. Patterson"
  ],
  "organizations": [],
  "publication_date": "2021-03-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "v6ops",
  "source_draft": "draft-ietf-v6ops-slaac-renum-05",
  "page_count": 11,
  "doi": "10.17487/RFC8978",
  "keywords": [],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8978/",
    "html": "https://www.rfc-editor.org/rfc/rfc8978.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8978.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8978/"
  }
}