[pim] Roman Danyliw's No Objection on draft-ietf-pim-3376bis-11: (with COMMENT)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-pim-3376bis-11: 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-3376bis/



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

Thank you to Stewart Bryant for the GENART review.

** Consider explicitly naming the registries in question:

-- Section 4., “IGMP message types are registered per [I-D.ietf-pim-3228bis].”
-- Section 4.1.4.  Flags, “The Flags field is a bitstring managed by an IANA
registry defined in [I-D.ietf-pim-3228bis].” -- Section 4.2.3.  Flags, “The
Flags field is a bitstring managed by an IANA registry defined in
[I-D.ietf-pim-3228bis].”

** Section 10
   All IGMP types described in this document are managed via
   [I-D.ietf-pim-3228bis].

Does this imply that there is no IANA action in this document?  Consider just
saying that.

** Idnits reported the following:

  -- The document seems to contain a disclaimer for pre-RFC5378 work, and may
     have content which was first submitted before 10 November 2008.  The
     disclaimer is necessary when there are original authors that you have
     been unable to contact, or if some do not wish to grant the BCP78 rights
     to the IETF Trust.  If you are able to get all authors (current and
     original) to grant those rights, you can and should remove the
     disclaimer; otherwise, the disclaimer is needed and you can ignore this
     comment. (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

Has one of the original authors of RFC3376 been approached to file the
appropriate paperwork with the Trust to assign the new rights?