Hi Yoav, > I don’t even know what “proper alignment” means for a cipher such as > this. If anything is proper alignment, then the value that fulfills the > SHOULD requirement is zero (with no padding bytes). For section 3, I > could add a text that echoes the second bullet: > > The sender SHOULD include no padding and set the Pad Length field to > zero. The receiver MUST accept any length of padding.
I agree, and think that text is fine. > > So I think Next Payload should be Notify (0x29). > > Yes, you’re right. I’ve fixed this in my working draft. I should > publish again in a day or two. Great. I can confirm that both the ESP and the IKEv2 examples in -06 now match the output of my test cases. I think the draft looks fine now, and I support to go on with it. Kind regards Martin _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
