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

IETF · RFC · RFC4389

RFC4389 · Neighbor Discovery Proxies (ND Proxy)

Neighbor Discovery Proxies (ND Proxy)

Bridging multiple links into a single entity has several operational advantages. A single subnet prefix is sufficient to support multiple physical links. There is no need to allocate subnet numbers to the different networks, simplifying management. Bridging some types of media requires network-layer support, however. This document describes these cases and specifies the IP-layer support that enables bridging under these circumstances. This memo defines an Experimental Protocol for the Internet community.

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

Bridging multiple links into a single entity has several operational advantages. A single subnet prefix is sufficient to support multiple physical links. There is no need to allocate subnet numbers to the different networks, simplifying management. Bridging some types of media requires network-layer support, however. This document describes these cases and specifies the IP-layer support that enables bridging under these circumstances. This memo defines an Experimental Protocol for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC4389",
  "number": 4389,
  "title_en": "Neighbor Discovery Proxies (ND Proxy)",
  "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": "Bridging multiple links into a single entity has several operational advantages. A single subnet prefix is sufficient to support multiple physical links. There is no need to allocate subnet numbers to the different networks, simplifying management. Bridging some types of media requires network-layer support, however. This document describes these cases and specifies the IP-layer support that enables bridging under these circumstances. This memo defines an Experimental Protocol for the Internet community.",
  "authors": [
    "D. Thaler",
    "M. Talwar",
    "C. Patel"
  ],
  "organizations": [],
  "publication_date": "2006-04-01",
  "current_status": "EXPERIMENTAL",
  "current_status_ru": "Экспериментальный",
  "publication_status": "EXPERIMENTAL",
  "publication_status_ru": "Экспериментальный",
  "lifecycle": "experimental",
  "lifecycle_ru": "Экспериментальный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "int",
  "area_ru": "Интернет",
  "working_group": "ipv6",
  "source_draft": "draft-ietf-ipv6-ndproxy-04",
  "page_count": 18,
  "doi": "10.17487/RFC4389",
  "keywords": [
    "ndproxy"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4389/",
    "html": "https://www.rfc-editor.org/rfc/rfc4389.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4389.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4389/"
  }
}