[secdir] secdir review of draft-ietf-ipsecme-rfc7321bis-05

[Tero Kivinen <[e-mail]>]

Christian Huitema writes:
> The second set of nits contains manual keying. According to the
> draft, anyone using manual keying is punished for doing so, and will
> only be able to use ENCR_AES_CBC. I assume that there is WG
> consensus on that, but the justification that other algorithms
> really require IKEv2 is a bit weak. If there is an API to configure
> encryption with the results of an IKEv2 negotiation, it could just
> as well be used with the results of a manual configuration. Not sure
> that the definition of algorithms is the best place to deprecate
> manual configuration, even if there are some pretty good reasons to
> do that.

Using API to configure keying material to the IPsec is not manual
keying.

There are two options in RFC4301 for key management, section 4.5.1
manual techniques, and 4.5.2 automated key management. Anything that
creates keys on the fly (i.e., IKEv2, or API) is automated key
management.

When using manual techniques the "person manually configures each
system with keying material and SA management data relevant to secure
communication with other systems." (section 4.5.1 of RFC4301).

As there might not be person manually configuring the next keys when
the device is rebooted, and when the counters start again from zero,
manual keying cannot be used with algorithms like CCM, GCM or CHACHA20
etc.
-- 
[e-mail]