<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pim-rfc8736bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-pim-rfc8736bis-00">
   <front>
      <title>PIM Message Type Space Extension and Reserved Bits</title>
      <author initials="S." surname="Venaas" fullname="Stig Venaas">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="A." surname="Retana" fullname="Alvaro Retana">
         <organization>Futurewei Technologies, Inc.</organization>
      </author>
      <date month="March" day="2" year="2023" />
      <abstract>
	 <t>   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 8736.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pim-rfc8736bis-00" />
   
</reference>
