[pim] Éric Vyncke's No Objection on draft-ietf-pim-assert-packing-10: (with COMMENT)

[Éric Vyncke via Datatracker <[e-mail]>]

Éric Vyncke has entered the following ballot position for
draft-ietf-pim-assert-packing-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pim-assert-packing/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Éric Vyncke, INT AD, comments for draft-ietf-pim-assert-packing-10
CC @evyncke

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points (but replies would be
appreciated even if only for my own education), and one nit.

Special thanks to Stig Venaas for the shepherd's detailed write-up including
the WG consensus **but** it lacks the justification of the intended status.

I hope that this review helps to improve the document,

Regards,

-éric

## COMMENTS

### Section 1

`there is typically more than one upstream router` unsure whether it is really
the common case... Suggest to s/there is typically/Sometimes there is/

### Section 2

Should there be references for assertions such as `something not possible
equally with an L3 subnet based ring`?

### Section 4.2

*Strongly* suggest to add a reference to section 4.9.1 of RFC 7761 for the
`encoded-* format` (as my heart missed a beat when seeing a 32-bit field).

## NITS

### Units

s/100msec/100 msec/ and other similar issues.

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues.

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments