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

IETF · RFC · RFC8168

RFC8168 · DHCPv6 Prefix-Length Hint Issues

DHCPv6 Prefix-Length Hint Issues

DHCPv6 Prefix Delegation allows a client to include a prefix-length hint value in the IA_PD option to indicate a preference for the size of the prefix to be delegated, but it is unclear about how the client and server should act in different situations involving the prefix-length hint. This document provides a summary of the existing problems with the prefix-length hint and guidance on what the client and server could do in different situations.

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

DHCPv6 Prefix Delegation allows a client to include a prefix-length hint value in the IA_PD option to indicate a preference for the size of the prefix to be delegated, but it is unclear about how the client and server should act in different situations involving the prefix-length hint. This document provides a summary of the existing problems with the prefix-length hint and guidance on what the client and server could do in different situations.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8168",
  "number": 8168,
  "title_en": "DHCPv6 Prefix-Length Hint Issues",
  "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": "DHCPv6 Prefix Delegation allows a client to include a prefix-length hint value in the IA_PD option to indicate a preference for the size of the prefix to be delegated, but it is unclear about how the client and server should act in different situations involving the prefix-length hint. This document provides a summary of the existing problems with the prefix-length hint and guidance on what the client and server could do in different situations.",
  "authors": [
    "T. Li",
    "C. Liu",
    "Y. Cui"
  ],
  "organizations": [],
  "publication_date": "2017-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": "int",
  "area_ru": "Интернет",
  "working_group": "dhc",
  "source_draft": "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-06",
  "page_count": 9,
  "doi": "10.17487/RFC8168",
  "keywords": [
    "DHCPv6",
    "Dynamic Host Configuration Protocol",
    "IPv6",
    "Prefix",
    "Prefix Delegation",
    "Prefix Length",
    "Hint",
    "Address Allocation"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8168/",
    "html": "https://www.rfc-editor.org/rfc/rfc8168.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8168.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8168/"
  }
}