RFC 8983 on Internet Key Exchange Protocol Version 2 (IKEv2) Notification Status Types for IPv4/IPv6 Coexistence
rfc-editor@rfc-editor.org Sat, 13 February 2021 07:13 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D11C13A100A; Fri, 12 Feb 2021 23:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HtN5nGcVQxZx; Fri, 12 Feb 2021 23:13:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 897183A1001; Fri, 12 Feb 2021 23:13:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4AF16F40757; Fri, 12 Feb 2021 23:12:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8983 on Internet Key Exchange Protocol Version 2 (IKEv2) Notification Status Types for IPv4/IPv6 Coexistence
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipsec@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210213071251.4AF16F40757@rfc-editor.org>
Date: Fri, 12 Feb 2021 23:12:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/zVW2vQj6rVXDMRlOhs7T4gUxSpQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Feb 2021 07:13:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8983
Title: Internet Key Exchange Protocol Version
2 (IKEv2) Notification Status Types for
IPv4/IPv6 Coexistence
Author: M. Boucadair
Status: Standards Track
Stream: IETF
Date: February 2021
Mailbox: mohamed.boucadair@orange.com
Pages: 7
Updates: RFC 7296
I-D Tag: draft-ietf-ipsecme-ipv6-ipv4-codes-06.txt
URL: https://www.rfc-editor.org/info/rfc8983
DOI: 10.17487/RFC8983
This document specifies new Internet Key Exchange Protocol Version 2
(IKEv2) notification status types to better manage IPv4 and IPv6
coexistence by allowing the responder to signal to the initiator
which address families are allowed.
This document updates RFC 7296.
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