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

IETF · RFC · RFC3956

RFC3956 · Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address

Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address

This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. [STANDARDS-TRACK]

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

This memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. [STANDARDS-TRACK]

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

updates: RFC3306

updated_by: RFC7371

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

Полные импортированные сведения карточки
{
  "id": "RFC3956",
  "number": 3956,
  "title_en": "Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address",
  "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 memo defines an address allocation policy in which the address of the Rendezvous Point (RP) is encoded in an IPv6 multicast group address. For Protocol Independent Multicast - Sparse Mode (PIM-SM), this can be seen as a specification of a group-to-RP mapping mechanism. This allows an easy deployment of scalable inter-domain multicast and simplifies the intra-domain multicast configuration as well. This memo updates the addressing format presented in RFC 3306. [STANDARDS-TRACK]",
  "authors": [
    "P. Savola",
    "B. Haberman"
  ],
  "organizations": [],
  "publication_date": "2004-11-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": "ops",
  "area_ru": "Эксплуатация и управление",
  "working_group": "mboned",
  "source_draft": "draft-ietf-mboned-embeddedrp-07",
  "page_count": 18,
  "doi": "10.17487/RFC3956",
  "keywords": [
    "RP",
    "Rendezvous Point",
    "internet protocol"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3306"
    ],
    "updated_by": [
      "RFC7371"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3956/",
    "html": "https://www.rfc-editor.org/rfc/rfc3956.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3956.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3956/"
  }
}