PIM reserved bits and type space extension
draft-ietf-pim-reserved-bits-00
| Document | Type | Expired Internet-Draft (pim WG) | |
|---|---|---|---|
| Authors | Stig Venaas , Alvaro Retana | ||
| Last updated | 2019-04-21 (Latest revision 2018-10-18) | ||
| Replaces | draft-venaas-pim-reserved-bits | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
OPSDIR Last Call review
(of
-03)
Has Issues
GENART Last Call review
(of
-03)
Ready with Issues
SECDIR Last Call review
(of
-03)
Has Nits
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-pim-reserved-bits-00.txt
Abstract
The currently defined 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 RFC7761 and RFC3973 by defining the use of the currently Reserved field in the PIM common header. This document further updates RFC7761 and RFC3973, along with RFC5015, RFC6754 and RFC8364, by specifying the use of the currently Reserved bits for each PIM message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)