RFC 9593 on Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Tue, 23 July 2024 17:32 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB4E9C151061; Tue, 23 Jul 2024 10:32:12 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 177E17FA61; Tue, 23 Jul 2024 10:32:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9593 on Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240723173212.177E17FA61@rfcpa.rfc-editor.org>
Date: Tue, 23 Jul 2024 10:32:12 -0700
Message-ID-Hash: VU65LKS53BMNFUV43G2EUJTXAQY3E4EO
X-Message-ID-Hash: VU65LKS53BMNFUV43G2EUJTXAQY3E4EO
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lix3w7B1xoTDZWLCn9YtylA8P94>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9593

        Title:      Announcing Supported Authentication Methods in the
                    Internet Key Exchange Protocol Version 2 (IKEv2) 
        Author:     V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2024
        Mailbox:    svan@elvis.ru
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-ikev2-auth-announce-10.txt

        URL:        https://www.rfc-editor.org/info/rfc9593

        DOI:        10.17487/RFC9593

This specification defines a mechanism that allows implementations of
the Internet Key Exchange Protocol Version 2 (IKEv2) to indicate the
list of supported authentication methods to their peers while
establishing IKEv2 Security Associations (SAs).  This mechanism
improves interoperability when IKEv2 partners are configured with
multiple credentials of different types for authenticating each
other.

This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC