Gorry Fairhurst has entered the following ballot position for draft-ietf-bfd-secure-sequence-numbers-23: 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-bfd-secure-sequence-numbers/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for preparing this I-D, and the careful text around how this provides an experimental change to BFD. The I-D seems related to I-D.ietf-bfd-optimizing-authentication. Whereas the current I-D in general is carefully constructed around the wording of security properties, the words here do not explain "optimizing" or "optimized" - which appear not to relate to security properties. For example, the following text states: "When the bfd.SessionState value is Up, packets MAY use an optimized authentication method (Optimizing BFD Authentication..." - As noted to the Editors of I-D.ietf-bfd-optimizing-authentication, I do wonder if this would be better described as lightweight/reduced processing requirements. I do not have any additional transport-related comments for this I-D. Best wishes, Gorry
