RFC 5996 on Internet Key Exchange Protocol Version 2 (IKEv2)

rfc-editor@rfc-editor.org Tue, 14 September 2010 19:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8AA53A6B3E; Tue, 14 Sep 2010 12:39:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.057
X-Spam-Level:
X-Spam-Status: No, score=-102.057 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6MavpZpjmetC; Tue, 14 Sep 2010 12:39:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 141C33A6B38; Tue, 14 Sep 2010 12:38:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9FC05E06FA; Tue, 14 Sep 2010 12:38:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5996 on Internet Key Exchange Protocol Version 2 (IKEv2)
From: rfc-editor@rfc-editor.org
Message-Id: <20100914193859.9FC05E06FA@rfc-editor.org>
Date: Tue, 14 Sep 2010 12:38:59 -0700 (PDT)
Cc: ipsec@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Sep 2010 19:40:39 -0000

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

        
        RFC 5996

        Title:      Internet Key Exchange Protocol Version 
                    2 (IKEv2) 
        Author:     C. Kaufman, P. Hoffman,
                    Y. Nir, P. Eronen
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2010
        Mailbox:    charliek@microsoft.com, 
                    paul.hoffman@vpnc.org, 
                    ynir@checkpoint.com,  pe@iki.fi
        Pages:      138
        Characters: 346466
        Obsoletes:  RFC4306, RFC4718

        I-D Tag:    draft-ietf-ipsecme-ikev2bis-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5996.txt

This document describes version 2 of the Internet Key Exchange (IKE)
protocol.  IKE is a component of IPsec used for performing mutual
authentication and establishing and maintaining Security Associations
(SAs).  This document replaces and updates RFC 4306, and includes all
of the clarifications from RFC 4718.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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