Warren Kumari has entered the following ballot position for draft-ietf-ace-key-groupcomm-17: 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-ace-key-groupcomm/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for writing this document - I found it both useful, and an easy read. I do have a nit / readability suggestion: "New keying material is generated and distributed to the group upon membership changes (rekeying), if the application requires backward security (i.e., new group members must be prevented from accessing communications in the group prior to their joining) and forward security (i.e., former group members must be prevented from accessing communications in the group after their leaving)." I found this wording confusing - I think that it is the comma after "upon membership changes (rekeying)". This initially sounds like "new keys are generated on every membership change. If the application requires backward security then [something else / something additional". I *think* that just dropping the comma fixes it... You also have a typo: "It is REQUIRED of application profiles of this specificaton to" - specification. _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
