Erik Kline has entered the following ballot position for draft-ietf-bfd-secure-sequence-numbers-24: 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: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-bfd-secure-sequence-numbers-24 CC @ekline * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md * "Handling Ballot Positions": - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ ## Comments ### S3.1 * "and the numbers produced by it are secure" Claiming "are secure" seems a bit imprecise. Perhaps "are sufficiently secure for the BFD authentication purposes here" or something? ### S8 * "makes these attacks unfeasable" Should this be more like "computationally infeasible" or "computationally intractable" or something? ## Nits ### S1 * "therefore define a Optimized" -> "therefore defines an Optimized" ### S3.1 * "rates of hundred of packets per second" -> "rates of hundreds of packets per second" ?
