Moving IKEv1, ISAKMP and IPsec DOI to Historic
status-change-ikev1-to-historic-00

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    draft-ietf-ipsec-ipsec-doi@ietf.org,
    draft-ietf-ipsec-isakmp-oakley@ietf.org,
    draft-ietf-ipsec-isakmp@ietf.org,
    iana@iana.org,
    ipsec-chairs@ietf.org,
    rdd@cert.org,
    rfc-editor@rfc-editor.org
Subject: Protocol Action: Internet Security Association and Key Management Protocol (ISAKMP) to Historic

The IESG has approved changing the status of the following document:
- Internet Security Association and Key Management Protocol (ISAKMP)
  (rfc2408) to Historic

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-ikev1-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc2408/

Status Change Details:

IKEv1 [RFC2409] and its related documents for ISAKMP [RFC2408] and IPsec DOI
[RFC2407] were obsoleted by IKEv2 [RFC4306] in December 2005.  IKEv2 has now
seen wide deployment and provides a full replacement for all IKEv1
functionality.  No new modifications or new algorithms have been accepted for
IKEv1 for at least a decade.  IKEv2 addresses various issues present in
IKEv1, such as IKEv1 being vulnerable to amplification attacks. It is
therefore timely to mark these IKEv1 specifications as Historic.

Upon approval and its publication as an RFC,
draft-ietf-ipsecme-ikev1-algo-to-historic should replace this status change
document as the reference for the status change event.

Personnel

  Roman Danyliw is the responsible Area Director.

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    draft-ietf-ipsec-ipsec-doi@ietf.org,
    draft-ietf-ipsec-isakmp-oakley@ietf.org,
    draft-ietf-ipsec-isakmp@ietf.org,
    iana@iana.org,
    ipsec-chairs@ietf.org,
    rdd@cert.org,
    rfc-editor@rfc-editor.org
Subject: Protocol Action: The Internet IP Security Domain of Interpretation for ISAKMP to Historic

The IESG has approved changing the status of the following document:
- The Internet IP Security Domain of Interpretation for ISAKMP
  (rfc2407) to Historic

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-ikev1-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc2407/

Status Change Details:

IKEv1 [RFC2409] and its related documents for ISAKMP [RFC2408] and IPsec DOI
[RFC2407] were obsoleted by IKEv2 [RFC4306] in December 2005.  IKEv2 has now
seen wide deployment and provides a full replacement for all IKEv1
functionality.  No new modifications or new algorithms have been accepted for
IKEv1 for at least a decade.  IKEv2 addresses various issues present in
IKEv1, such as IKEv1 being vulnerable to amplification attacks. It is
therefore timely to mark these IKEv1 specifications as Historic.

Upon approval and its publication as an RFC,
draft-ietf-ipsecme-ikev1-algo-to-historic should replace this status change
document as the reference for the status change event.

Personnel

  Roman Danyliw is the responsible Area Director.

The following approval message was sent
From: The IESG
To: IETF-Announce 
Cc: The IESG ,
    draft-ietf-ipsec-ipsec-doi@ietf.org,
    draft-ietf-ipsec-isakmp-oakley@ietf.org,
    draft-ietf-ipsec-isakmp@ietf.org,
    iana@iana.org,
    ipsec-chairs@ietf.org,
    rdd@cert.org,
    rfc-editor@rfc-editor.org
Subject: Protocol Action: The Internet Key Exchange (IKE) to Historic

The IESG has approved changing the status of the following document:
- The Internet Key Exchange (IKE)
  (rfc2409) to Historic

This protocol action is documented at:
https://datatracker.ietf.org/doc/status-change-ikev1-to-historic/

A URL of the affected document is:
https://datatracker.ietf.org/doc/rfc2409/

Status Change Details:

IKEv1 [RFC2409] and its related documents for ISAKMP [RFC2408] and IPsec DOI
[RFC2407] were obsoleted by IKEv2 [RFC4306] in December 2005.  IKEv2 has now
seen wide deployment and provides a full replacement for all IKEv1
functionality.  No new modifications or new algorithms have been accepted for
IKEv1 for at least a decade.  IKEv2 addresses various issues present in
IKEv1, such as IKEv1 being vulnerable to amplification attacks. It is
therefore timely to mark these IKEv1 specifications as Historic.

Upon approval and its publication as an RFC,
draft-ietf-ipsecme-ikev1-algo-to-historic should replace this status change
document as the reference for the status change event.

Personnel

  Roman Danyliw is the responsible Area Director.

[Ballot comment]
Not that it matters, but I'm not sure whether Paul needs to recuse from this.  To me this seems to fall well into the technical remit of a Sec AD, and hence he should be able to ballot Yes on this.

[Ballot comment]
Not that it matters, but I'm not sure whether Paul needs to recluse from this.  To me this seems to fall well into the technical remit of a Sec AD, and hence he should be able to ballot Yes on this.

The following Last Call announcement was sent out (ends 2022-11-18):

From: The IESG
To: IETF-Announce
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call: Moving IKEv1, ISAKMP and IPsec DOI to Historic


The IESG has received a request from an individual participant to make the
following status changes:

- RFC2409 from Proposed Standard to Historic
    (The Internet Key Exchange (IKE))

- RFC2407 from Proposed Standard to Historic
    (The Internet IP Security Domain of Interpretation for ISAKMP)

- RFC2408 from Proposed Standard to Historic
    (Internet Security Association and Key Management Protocol (ISAKMP))

The supporting document for this request can be found here:

https://datatracker.ietf.org/doc/status-change-ikev1-to-historic/

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-11-18. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

The affected documents can be obtained via
https://datatracker.ietf.org/doc/rfc2409/
https://datatracker.ietf.org/doc/rfc2407/
https://datatracker.ietf.org/doc/rfc2408/

IESG discussion of this request can be tracked via
https://datatracker.ietf.org/doc/status-change-ikev1-to-historic/ballot/