RFC 4109 on Algorithms for Internet Key Exchange version 1 (IKEv1)

rfc-editor@rfc-editor.org Thu, 26 May 2005 00:27 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Db6Dv-0004Vf-9R; Wed, 25 May 2005 20:27:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Db6Dt-0004Va-Ci for ietf-announce@megatron.ietf.org; Wed, 25 May 2005 20:27:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11785 for <ietf-announce@ietf.org>; Wed, 25 May 2005 20:27:40 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Db6WN-0007Mj-Mp for ietf-announce@ietf.org; Wed, 25 May 2005 20:46:48 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j4Q0QqL24237; Wed, 25 May 2005 17:26:52 -0700 (PDT)
Message-Id: <200505260026.j4Q0QqL24237@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 25 May 2005 17:26:52 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4109 on Algorithms for Internet Key Exchange version 1 (IKEv1)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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


        RFC 4109

        Title:      Algorithms for Internet Key Exchange version 1
                    (IKEv1)
        Author(s):  P. Hoffman
        Status:     Standards Track
        Date:       May 2005
        Mailbox:    paul.hoffman@vpnc.org
        Pages:      5
        Characters: 9491
        Updates:    2409

        I-D Tag:    draft-hoffman-ikev1-algorithms-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4109.txt


The required and suggested algorithms in the original Internet Key
Exchange version 1 (IKEv1) specification do not reflect the current
reality of the IPsec market requirements.  The original specification
allows weak security and suggests algorithms that are thinly
implemented.  This document updates RFC 2409, the original
specification, and is intended for all IKEv1 implementations deployed
today.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc4109.txt"><ftp://ftp.isi.edu/in-notes/rfc4109.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce