IKEv2 Rekeying of IKE_SA using CREATE_CHILD_SA message

こ雲淡風輕ζ 提交于 2019-12-06 11:19:58

I think the underlying SAs are not rekeyed -- they are just inherited by the newly established IKE SA (i.e. they will be managed using this new IKE SA).

Citing RFC 7296:

To rekey an IKE SA, establish a new equivalent IKE SA (see Section 2.18 below) with the peer to whom the old IKE SA is shared using a CREATE_CHILD_SA within the existing IKE SA. An IKE SA so created inherits all of the original IKE SA's Child SAs, and the new IKE SA is used for all control messages needed to maintain those Child SAs. After the new equivalent IKE SA is created, the initiator deletes the old IKE SA, and the Delete payload to delete itself MUST be the last request sent over the old IKE SA.

The SA keys must be fixed during the whole SA lifetime -- there would be a gap when packets belonging to the same SA would be refused (packets sent before the rekeying took place that arrived after the rekeying finished would fail the integrity check).

Desclaimer: It has been some time since I was dealing with this, so please do validate my thoughts.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!