On Fri, 9 Oct 2015, Daniel Migault wrote:
Especially thinking of constrained devices. AES-GCM with 8 octet SHOULD : the reason for not having SHOULD+ is that most IoT devices seems to use CCM AES-CCM with 8 octet SHOULD+
I would prefer that constrained devices put their specs in draft-ietf-lwig-ikev2-minimal https://tools.ietf.org/html/draft-ietf-lwig-ikev2-minimal-03 Or that we list that those versions should only be used if the server is talking to constrained devices. But maybe that's too much text, and we should stick to SHOULD (as most implementations handle all octet sizes anyway)
I would have thought of 3DES with similar or slightly less weight as CHACHA20_POLY1025 so
Without actual interop and deployment experience, I would not yet want to officially prefer CHACHA20_POLY1025 over 3DES. Paul _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
