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

IETF · RFC · RFC4361

RFC4361 · Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)

Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)

This document specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers. [STANDARDS-TRACK]

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

This document specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers. [STANDARDS-TRACK]

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

updates: RFC2131, RFC2132, RFC3315

updated_by: RFC5494

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

Полные импортированные сведения карточки
{
  "id": "RFC4361",
  "number": 4361,
  "title_en": "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)",
  "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 specifies the format that is to be used for encoding Dynamic Host Configuration Protocol Version Four (DHCPv4) client identifiers, so that those identifiers will be interchangeable with identifiers used in the DHCPv6 protocol. This document also addresses and corrects some problems in RFC 2131 and RFC 2132 with respect to the handling of DHCP client identifiers. [STANDARDS-TRACK]",
  "authors": [
    "T. Lemon",
    "B. Sommerfeld"
  ],
  "organizations": [],
  "publication_date": "2006-02-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-3315id-for-v4-05",
  "page_count": 12,
  "doi": "10.17487/RFC4361",
  "keywords": [
    "dhcpv6"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC2131",
      "RFC2132",
      "RFC3315"
    ],
    "updated_by": [
      "RFC5494"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4361/",
    "html": "https://www.rfc-editor.org/rfc/rfc4361.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4361.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4361/"
  }
}