A new Request for Comments is now available in online RFC libraries.
RFC 4307
Title: Cryptographic Algorithms for Use in the
Internet Key Exchange Version 2 (IKEv2)
Author(s): J. Schiller
Status: Standards Track
Date: December 2005
Mailbox: [EMAIL PROTECTED]
Pages: 6
Characters: 12985
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsec-ikev2-algorithms-05.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc4307.txt
The IPsec series of protocols makes use of various cryptographic
algorithms in order to provide security services. The Internet Key
Exchange (IKE (RFC 2409) and IKEv2) provide a mechanism to
negotiate which algorithms should be used in any given association.
However, to ensure interoperability between disparate implementations,
it is necessary to specify a set of mandatory-to-implement algorithms
to ensure that there is at least one algorithm that all
implementations will have available. This document defines the
current set of algorithms that are mandatory to implement as part of
IKEv2, as well as algorithms that should be implemented because they
may be promoted to mandatory at some future time.
This document is a product of the IP Security Protocol Working Group
of the IETF.
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 [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] 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/rfc4307.txt>
-
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
