PIM Message Type Space Extension and Reserved Bits
draft-ietf-pim-rfc8736bis-04

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pim-rfc8736bis@ietf.org, james.n.guichard@futurewei.com, mmcbride7@gmail.com, pim-chairs@ietf.org, pim@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'PIM Message Type Space Extension and Reserved Bits' to Proposed Standard (draft-ietf-pim-rfc8736bis-04.txt)

The IESG has approved the following document:
- 'PIM Message Type Space Extension and Reserved Bits'
  (draft-ietf-pim-rfc8736bis-04.txt) as Proposed Standard

This document is the product of the Protocols for IP Multicast Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-rfc8736bis/

Ballot Text

Technical Summary

   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 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, RFC5059,
   RFC6754, and RFC8364, by specifying the use of the currently reserved
   bits for each PIM message.

   This document obsoletes RFC8736.

Working Group Summary

   The purpose of this document is to fix a bug in RFC 8736 that is holding up other drafts. 
   WG consensus was reached and no issues highlighted.

Personnel

   The Document Shepherd for this document is Mike McBride. The Responsible
   Area Director is Jim Guichard.

RFC Editor Note