Re: [pim] I-D Action: draft-venaas-pim-rfc8736bis-00.txt

Hi Alvaro,

Makes sense and thanks to you both for posting this update quickly. Please
submit your draft as a wg document and I will approve and then will ask for
publication next week.

WG, please speak up if you have any concerns with this process. This bis
document we are expediting is to fix a bug in 8736.
draft-ietf-pim-null-register-packing
is currently under iesg review and needs this change to progress.

Thanks,

mike

On Wed, Mar 1, 2023 at 8:43 AM Alvaro Retana <alvaro.retana@futurewei.com>
wrote:

>
> [Individual Contributor hat.]
>
>
> Mike:
>
> Hi!
>
> Stig and I just published this draft to address a bug in rfc8736.
>
> The problem is that Flag Bits (for all the PIM messages) are marked as
> Reserved, but they should have been Unassigned.  It is a problem because
> drafts like draft-ietf-pim-null-register-packing need a bit allocated.
>
> rfc8736 (PIM Message Type Space Extension and Reserved Bits) updated
> rfc7761 (and others) with the intent of reallocating the reserved bits --
> from the Abstract:
>
>    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.
>
>
> *But* we focused too much on the type extension and overlooked the change
> from Reserved to Unassigned. :-(
>
> Considering that draft-ietf-pim-null-register-packing should now
> Normatively depend on rfc8736bis (and not rfc8736) [1], we would like to as
> for "expedited processing" to avoid significant delays.
>
> The link to the diff of rfc8736bis-00 with respect to rfc8736 is below [2].
>
> Thanks!
>
> Alvaro.
>
>
> [1] https://mailarchive.ietf.org/arch/msg/pim/aaJ3uugshOspS0Ri0vg8sz66g90/
>
> [2]
> https://author-tools.ietf.org/iddiff?url1=rfc8736&url2=draft-venaas-pim-rfc8736bis-00&difftype=--html
>
>
>
> On March 1, 2023 at 10:04:13 AM, internet-drafts@ietf.org (
> internet-drafts@ietf.org) wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title : PIM Message Type Space Extension and Reserved Bits
> Authors : Stig Venaas
> Alvaro Retana
> Filename : draft-venaas-pim-rfc8736bis-00.txt
> Pages : 8
> Date : 2023-03-01
>
> Abstract:
> 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.
>
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-venaas-pim-rfc8736bis/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-venaas-pim-rfc8736bis-00.html
>
>
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>
>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>