Hello, I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft. Document: draft-ietf-pim-null-register-packing Reviewer: Tal Mizrahi Review Date: February 28th, 2023 Intended Status: Standards Track Summary: This document is basically ready for publication but has nits that should be considered prior to publication. Comments: This document is clear and straightforward, and is almost ready for publication. Nits: - "This draft" => "This document" - "The draft" => "The document" - Section 2 - please mention that you are referring to the 'P' bit in Figure 1. - Section 3 and Section 4: please describe explicitly what happens with the Subtype. It looks like you are not asking for an allocation, so is this field going to have a constant value? Please describe this in the document. - Section 9: it would help if this section was more explicit in defining the rows that you would like to add to the table in the PIM Message Types registry. In addition, it looks like for each of the two types you want to allocate a 'P' flag, right? Please describe this explicitly. Cheers, Tal. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
