[mpls] Paul Wouters' No Objection on draft-ietf-mpls-bfd-directed-30: (with COMMENT)

[Paul Wouters via Datatracker <[e-mail]>]

Paul Wouters has entered the following ballot position for
draft-ietf-mpls-bfd-directed-30: 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-mpls-bfd-directed/



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

The Security Considerations doesn't say _anything_ about something that could
apply to this documents feature? Is there really nothing at all to consider?

        Group communication for CoAP has been enabled in
        [I-D.ietf-core-groupcomm-bis]

Maybe say "has been defined in" ?

        Reverse Path field MAY contain none, one, or more sub-TLVs.

Remove the "MAY" here? Or explain what not following the MAY means?

Similar for:

         None, one or more sub-TLVs MAY be included in the BFD Reverse Path TLV.

Related:

        an implementation MAY be able to control that limit