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

IETF · RFC · RFC8638

RFC8638 · IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Networks

IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Networks

During the transition to IPv6, there are scenarios where a backbone network internally running one IP address family (referred to as the internal IP or I-IP family) connects client networks running another IP address family (referred to as the external IP or E-IP family). In such cases, the I-IP backbone needs to offer both unicast and multicast transit services to the client E-IP networks. This document describes a mechanism for supporting multicast across backbone networks where the I-IP and E-IP protocol families differ. The document focuses on the IPv4-over-IPv6 scenario, due to lack of real-world use cases for the IPv6-over-IPv4 scenario.

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

During the transition to IPv6, there are scenarios where a backbone network internally running one IP address family (referred to as the internal IP or I-IP family) connects client networks running another IP address family (referred to as the external IP or E-IP family). In such cases, the I-IP backbone needs to offer both unicast and multicast transit services to the client E-IP networks. This document describes a mechanism for supporting multicast across backbone networks where the I-IP and E-IP protocol families differ. The document focuses on the IPv4-over-IPv6 scenario, due to lack of real-world use cases for the IPv6-over-IPv4 scenario.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC8638",
  "number": 8638,
  "title_en": "IPv4 Multicast over an IPv6 Multicast in Softwire Mesh Networks",
  "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": "During the transition to IPv6, there are scenarios where a backbone network internally running one IP address family (referred to as the internal IP or I-IP family) connects client networks running another IP address family (referred to as the external IP or E-IP family). In such cases, the I-IP backbone needs to offer both unicast and multicast transit services to the client E-IP networks. This document describes a mechanism for supporting multicast across backbone networks where the I-IP and E-IP protocol families differ. The document focuses on the IPv4-over-IPv6 scenario, due to lack of real-world use cases for the IPv6-over-IPv4 scenario.",
  "authors": [
    "M. Xu",
    "Y. Cui",
    "J. Wu",
    "S. Yang",
    "C. Metz"
  ],
  "organizations": [],
  "publication_date": "2019-09-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": "softwire",
  "source_draft": "draft-ietf-softwire-mesh-multicast-25",
  "page_count": 19,
  "doi": "10.17487/RFC8638",
  "keywords": [
    "Multicast",
    "Mesh",
    "SSM",
    "ASM"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8638/",
    "html": "https://www.rfc-editor.org/rfc/rfc8638.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8638.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8638/"
  }
}