We just submitted a draft to be able to specify a reason and ETA for why an IKE SA or Child SA(s) are being deleted.
We got this request from the community, where operators often see a tunnel going down but have no idea why it is going down and whether humans should be brought into the loop. This optional reason and eta message hopes to give more visibility to peers about this. The draft includes some example messages. Let us know what you think. I think the document is easy enough not to need a presentation or face to face time at IETF-118 :) Paul On Mon, Oct 23, 2023 at 10:47 AM <internet-dra...@ietf.org> wrote: > A new version of Internet-Draft draft-pwouters-ipsecme-delete-info-00.txt > has > been successfully submitted by Paul Wouters and posted to the > IETF repository. > > Name: draft-pwouters-ipsecme-delete-info > Revision: 00 > Title: IKEv2 support for specifying a Delete notify reason > Date: 2023-10-23 > Group: Individual Submission > Pages: 6 > URL: > https://www.ietf.org/archive/id/draft-pwouters-ipsecme-delete-info-00.txt > Status: > https://datatracker.ietf.org/doc/draft-pwouters-ipsecme-delete-info/ > HTMLized: > https://datatracker.ietf.org/doc/html/draft-pwouters-ipsecme-delete-info > > > Abstract: > > This document defines the DELETE_REASON Notify Message Status Type > Payload for the Internet Key Exchange Protocol Version 2 (IKEv2) to > support adding a reason for the deletion of the IKE or Child SA(s). > > > >
_______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
