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

IETF · RFC · RFC8736

RFC8736 · PIM Message Type Space Extension and Reserved Bits

PIM Message Type Space Extension and Reserved Bits

The PIM version 2 messages share a common message header format. The common header definition contains eight reserved bits. This document specifies how these bits may be used by individual message types and creates a registry containing the per-message-type usage. This document also extends the PIM type space by defining three new message types. For each of the new types, four of the previously reserved bits are used to form an extended type range. This document updates RFCs 7761 and 3973 by defining the use of the currently Reserved field in the PIM common header. This document further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754, and 8364, by specifying the use of the currently reserved bits for each PIM message. This document obsoletes RFC 6166.

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

The PIM version 2 messages share a common message header format. The common header definition contains eight reserved bits. This document specifies how these bits may be used by individual message types and creates a registry containing the per-message-type usage. This document also extends the PIM type space by defining three new message types. For each of the new types, four of the previously reserved bits are used to form an extended type range. This document updates RFCs 7761 and 3973 by defining the use of the currently Reserved field in the PIM common header. This document further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754, and 8364, by specifying the use of the currently reserved bits for each PIM message. This document obsoletes RFC 6166.

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

obsoletes: RFC6166

obsoleted_by: RFC9436

updates: RFC3973, RFC5015, RFC5059, RFC6754, RFC7761, RFC8364

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

Полные импортированные сведения карточки
{
  "id": "RFC8736",
  "number": 8736,
  "title_en": "PIM Message Type Space Extension and Reserved Bits",
  "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 version 2 messages share a common message header format. The common header definition contains eight reserved bits. This document specifies how these bits may be used by individual message types and creates a registry containing the per-message-type usage. This document also extends the PIM type space by defining three new message types. For each of the new types, four of the previously reserved bits are used to form an extended type range. This document updates RFCs 7761 and 3973 by defining the use of the currently Reserved field in the PIM common header. This document further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754, and 8364, by specifying the use of the currently reserved bits for each PIM message. This document obsoletes RFC 6166.",
  "authors": [
    "S. Venaas",
    "A. Retana"
  ],
  "organizations": [],
  "publication_date": "2020-02-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "superseded",
  "lifecycle_ru": "Заменён",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rtg",
  "area_ru": "Маршрутизация",
  "working_group": "pim",
  "source_draft": "draft-ietf-pim-reserved-bits-04",
  "page_count": 8,
  "doi": "10.17487/RFC8736",
  "keywords": [
    "Multicast"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [
      "RFC6166"
    ],
    "obsoleted_by": [
      "RFC9436"
    ],
    "updates": [
      "RFC3973",
      "RFC5015",
      "RFC5059",
      "RFC6754",
      "RFC7761",
      "RFC8364"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8736/",
    "html": "https://www.rfc-editor.org/rfc/rfc8736.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8736.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8736/"
  }
}