[trill] Eric Rescorla's No Objection on draft-ietf-trill-p2mp-bfd-08: (with COMMENT)

[Eric Rescorla <[e-mail]>]

Eric Rescorla has entered the following ballot position for
draft-ietf-trill-p2mp-bfd-08: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-trill-p2mp-bfd/



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

I'm hoping this can be resolved quickly, as it's probably just a missing
cite. If it turns out that there's actually missing content, this
may turn into a DISCUSS.

   Multipoint BFD provides its own authentication but does not provide
   encryption (see Security Considerations in [I-D.ietf-bfd-
   multipoint]). As specified in this document, the point-to-multipoint

I skimmed the reference here, but wasn't able to figure out what the
authentication was. In particular, the document says:

      If the A bit is set, the packet MUST be authenticated under the
      rules of section 6.7, based on the authentication type in use
      (bfd.AuthType.)  This may cause the packet to be discarded.

But there is no 6.7. So, this makes me worry that I don't understand
any of this.