John Scudder has entered the following ballot position for draft-ietf-lisp-pubsub-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-lisp-pubsub/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this well-crafted (albeit dense) document. I have one question. While I don't think it needs to be a blocking issue, I'd still appreciate discussion. In Section 7.1, you write, If PubSub is being used in an environment where replay attacks might occur, then the Map-Server MUST verify that the OTK has not been used before. I strained to think of a realistic deployment where the threat model was one where security was required, but replay protection was NOT required. Can you provide an example of one? _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
