IKEv2 support for specifying a Delete notify reason

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 25 April 2024.¶

Copyright Notice

Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

2. DELETE_REASON Notify Status Message Payload

                    1                   2                   3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-----------------------------+-------------------------------+
! Next Payload  !C!  RESERVED   !         Payload Length        !
+---------------+---------------+-------------------------------+
!  Protocol ID  !   SPI Size    !      Notify Message Type      !
+---------------+---------------+-------------------------------+
!            Downtime           !                               !
+-------------------------------+  Reason Message               ~
~                                                               !
+-------------------------------+-------------------------------+

• Protocol ID (1 octet) - MUST be 0. MUST be ignored if not 0.¶

• SPI Size (1 octet) - MUST be 0. MUST be ignored if not 0.¶

• Notify Status Message Type (2 octets) - set to [TBD1]¶

• Downtime. A value in seconds for the expected downtime. 0 means unspecified.¶

• Reason Message. May be empty. Otherwise a non-NULL terminated UTF-8 or ASCII text.¶

3. Operational Considerations

A DELETE_REASON payload MUST be ignored if the exchange does not contain a Delete payload. If multiple Delete payloads are present, the DELETE_REASON message applies to all of these. If separate different reasons should be conveyed for different Child SAs or IKE SA, those Delete messages and their accompanied DELETE_REASON messages should be sent in separate Informational Exchange messages.¶

4. Security Considerations

Any timing information and reason should be treated as an informational "best effort" message from the peer's operator. A DELETE_REASON message SHOULD NOT change the behaviour of the IKE implementation other than logging the message or triggering an informational or alert message.¶

As with all received free-form text data, the receiver MUST treat the DELETE_REASON notify data as untrusted. It SHOULD strip or replace any characters not deemd regular text, for example the dollar sign ($), braces, backticks and backslashes. The Reason Message MUST NOT be assumed to be safe to display. It MUST NOT be assumed to be NULL terminated, which means common string operations such as strlen() MUST NOT be used without precautions. After the data has been processed and confirmed safe, it can be used for logging or as messages in notification systems.¶

5. Example Messages

This section specifies short example messages that could be used to convey common reasons that implementations might have for deleting SAs.¶

Reason Message

Meaning of the Reason Message¶

"SERVICE_SHUTDOWN"

The IKE service is being shut down¶

"SERVICE_RESTART"

The IKE service is being restarted¶

"HOST_SHUTDOWN"

The host running the IKE service is being shut down¶

"HOST_RESTART"

The host running the IKE service is being restarted¶

"CONFIGURATION_CHILD_REMOVED"

The Child SA was removed from the peer's configuration¶

"CONFIGURATION_IKE_REMOVED"

The IKE SA was removed from the peer's configuration¶

"ADMINISTRATIVELY_DOWN"

The SA was brought down by the operator¶

"IDLE_TIMEOUT"

The SA was inactive and brought down automatically by the system¶

"INITIAL_CONTACT_REPLACED"

A new IKE SA with this peer was established that signaled INITIAL_CONTACT¶

"SIMULTANEOUS_REKEY"

The peers ended up rekeying at once, and this SA lost in favour of the other¶

"RE_AUTHENTICATED"

A new IKE SA with this peer was established for re-authentication purposes¶

"REDIRECTION_ACCEPTED"

The redirection request was accepted and established, obsoleting this old SA¶

"LIFETIME_EXCEEDED"

The SA reached its local lifetime counter (bytes or seconds or packets) and was not rekeyed in time¶

6. Implementation Status

[Note to RFC Editor: Please remove this section and the reference to [RFC6982] before publication.]¶

This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.¶

According to [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".¶

Authors are requested to add a note to the RFC Editor at the top of this section, advising the Editor to remove the entire section before publication, as well as the reference to [RFC7942].¶

7. IANA Considerations

This document defines one new IKEv2 Notify Message Type payload for the IANA "IKEv2 Notify Message Types - Status Types" registry.¶

      Value   Notify Type Messages - Status Types    Reference
      -----   ------------------------------    ---------------
      [TBD1]   DELETE_REASON                    [this document]

Authors' Addresses