John Scudder has entered the following ballot position for draft-ietf-ipsecme-ikev2-intermediate-09: 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-ipsecme-ikev2-intermediate/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this. I have just a couple minor questions/suggestions. 1. Section 3.2, “these exchanges MUST follow each other”. I suppose what is meant is, “these exchanges MUST be sequential” (this hardly seems to need to be mandated, but OK). Or is something else intended, in which case, what is it? 2. In Section 3.4, there is: not all error notifications may ever appear in the IKE_INTERMEDIATE exchange (for example, errors concerning authentication are generally only applicable to the IKE_AUTH exchange). I can’t make sense of what the word “ever” is doing there. It makes sense to me if I remove “ever” to make it “not all error notifications may appear”. It’s OK if I change “ever” to “even”. But I don’t get it, as written. Am I missing something, or would one of my edits be appropriate? _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
