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

IETF · RFC · RFC7891

RFC7891 · Explicit Reverse Path Forwarding (RPF) Vector

Explicit Reverse Path Forwarding (RPF) Vector

The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496 can be included in a PIM Join Attribute such that the RPF neighbor is selected based on the unicast reachability of the RPF Vector instead of the source or Rendezvous Point associated with the multicast tree. This document defines a new RPF Vector Attribute type such that an explicit RPF neighbor list can be encoded in the PIM Join Attribute, thus bypassing the unicast route lookup.

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

The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496 can be included in a PIM Join Attribute such that the RPF neighbor is selected based on the unicast reachability of the RPF Vector instead of the source or Rendezvous Point associated with the multicast tree. This document defines a new RPF Vector Attribute type such that an explicit RPF neighbor list can be encoded in the PIM Join Attribute, thus bypassing the unicast route lookup.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC7891",
  "number": 7891,
  "title_en": "Explicit Reverse Path Forwarding (RPF) Vector",
  "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": "The PIM Reverse Path Forwarding (RPF) Vector TLV defined in RFC 5496 can be included in a PIM Join Attribute such that the RPF neighbor is selected based on the unicast reachability of the RPF Vector instead of the source or Rendezvous Point associated with the multicast tree. This document defines a new RPF Vector Attribute type such that an explicit RPF neighbor list can be encoded in the PIM Join Attribute, thus bypassing the unicast route lookup.",
  "authors": [
    "J. Asghar",
    "IJ. Wijnands",
    "S. Krishnaswamy",
    "A. Karan",
    "V. Arya"
  ],
  "organizations": [],
  "publication_date": "2016-06-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": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "pim",
  "source_draft": "draft-ietf-pim-explicit-rpf-vector-09",
  "page_count": 9,
  "doi": "10.17487/RFC7891",
  "keywords": [
    "Path diversity",
    "MoFRR",
    "Maximally redundant paths"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7891/",
    "html": "https://www.rfc-editor.org/rfc/rfc7891.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7891.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7891/"
  }
}