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

IETF · RFC · RFC4192

RFC4192 · Procedures for Renumbering an IPv6 Network without a Flag Day

Procedures for Renumbering an IPv6 Network without a Flag Day

This document describes a procedure that can be used to renumber a network from one prefix to another. It uses IPv6's intrinsic ability to assign multiple addresses to a network interface to provide continuity of network service through a "make-before-break" transition, as well as addresses naming and configuration management issues. It also uses other IPv6 features to minimize the effort and time required to complete the transition from the old prefix to the new prefix. This memo provides information for the Internet community.

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

This document describes a procedure that can be used to renumber a network from one prefix to another. It uses IPv6's intrinsic ability to assign multiple addresses to a network interface to provide continuity of network service through a "make-before-break" transition, as well as addresses naming and configuration management issues. It also uses other IPv6 features to minimize the effort and time required to complete the transition from the old prefix to the new prefix. This memo provides information for the Internet community.

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

updates: RFC2072

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

Полные импортированные сведения карточки
{
  "id": "RFC4192",
  "number": 4192,
  "title_en": "Procedures for Renumbering an IPv6 Network without a Flag Day",
  "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": "This document describes a procedure that can be used to renumber a network from one prefix to another. It uses IPv6's intrinsic ability to assign multiple addresses to a network interface to provide continuity of network service through a \"make-before-break\" transition, as well as addresses naming and configuration management issues. It also uses other IPv6 features to minimize the effort and time required to complete the transition from the old prefix to the new prefix. This memo provides information for the Internet community.",
  "authors": [
    "F. Baker",
    "E. Lear",
    "R. Droms"
  ],
  "organizations": [],
  "publication_date": "2005-09-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-renumbering-procedure-05",
  "page_count": 22,
  "doi": "10.17487/RFC4192",
  "keywords": [
    "prefix",
    "internet protocol",
    "network interface",
    "make-before-break",
    "enterprise",
    "connecting routers"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC2072"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4192/",
    "html": "https://www.rfc-editor.org/rfc/rfc4192.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4192.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4192/"
  }
}