RFC9436 · 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 extends the PIM type space. This document updates RFCs 7761 and 3973 by defining the use of the 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 bits for each PIM message. This document obsoletes RFC 8736.
IETF · RFCОфициальная английская аннотация
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 extends the PIM type space. This document updates RFCs 7761 and 3973 by defining the use of the 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 bits for each PIM message. This document obsoletes RFC 8736.
{
"id": "RFC9436",
"number": 9436,
"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 extends the PIM type space. This document updates RFCs 7761 and 3973 by defining the use of the 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 bits for each PIM message. This document obsoletes RFC 8736.",
"authors": [
"S. Venaas",
"A. Retana"
],
"organizations": [],
"publication_date": "2023-08-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-rfc8736bis-04",
"page_count": 7,
"doi": "10.17487/RFC9436",
"keywords": [
"Multicast PIM"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [
"RFC8736"
],
"obsoleted_by": [],
"updates": [
"RFC3973",
"RFC5015",
"RFC5059",
"RFC6754",
"RFC7761",
"RFC8364"
],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc9436/",
"html": "https://www.rfc-editor.org/rfc/rfc9436.html",
"txt": "https://www.rfc-editor.org/rfc/rfc9436.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc9436/"
}
}