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

IETF · RFC · RFC7788

RFC7788 · Home Networking Control Protocol

Home Networking Control Protocol

This document describes the Home Networking Control Protocol (HNCP), an extensible configuration protocol, and a set of requirements for home network devices. HNCP is described as a profile of and extension to the Distributed Node Consensus Protocol (DNCP). HNCP enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address.

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

This document describes the Home Networking Control Protocol (HNCP), an extensible configuration protocol, and a set of requirements for home network devices. HNCP is described as a profile of and extension to the Distributed Node Consensus Protocol (DNCP). HNCP enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address.

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

updated_by: RFC8375

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

Полные импортированные сведения карточки
{
  "id": "RFC7788",
  "number": 7788,
  "title_en": "Home Networking Control Protocol",
  "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 the Home Networking Control Protocol (HNCP), an extensible configuration protocol, and a set of requirements for home network devices. HNCP is described as a profile of and extension to the Distributed Node Consensus Protocol (DNCP). HNCP enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address.",
  "authors": [
    "M. Stenberg",
    "S. Barth",
    "P. Pfister"
  ],
  "organizations": [],
  "publication_date": "2016-04-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": "homenet",
  "source_draft": "draft-ietf-homenet-hncp-10",
  "page_count": 40,
  "doi": "10.17487/RFC7788",
  "keywords": [
    "IPv6",
    "Homenet",
    "DNCP"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8375"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7788/",
    "html": "https://www.rfc-editor.org/rfc/rfc7788.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7788.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7788/"
  }
}