[Ipsec] RFC 4868 on Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec

[[e-mail]]

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


         RFC 4868

         Title:      Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512
                     with IPsec
         Author:     S. Kelly, S. Frankel
         Status:     Standards Track
         Date:       May 2007
         Mailbox:    [e-mail],
                     [e-mail]
         Pages:      21
         Characters: 41432
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-kelly-ipsec-ciph-sha2-01.txt

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

This specification describes the use of Hashed Message Authentication
Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512
algorithms in IPsec.  These algorithms may be used as the basis for
data origin authentication and integrity verification mechanisms for
the Authentication Header (AH), Encapsulating Security Payload (ESP),
Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also
as Pseudo-Random Functions (PRFs) for IKE and IKEv2.  Truncated
output lengths are specified for the authentication-related variants,
with the corresponding algorithms designated as HMAC-SHA-256-128,
HMAC-SHA-384-192, and HMAC-SHA-512-256.  The PRF variants are not
truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and
PRF-HMAC-SHA-512.  [STANDARDS TRACK]

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body

help: ways_to_get_rfcs. For example:

         To: [e-mail]
From [e-mail] Fri May 04 19:43:49 2007
Return-path: <[e-mail]>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hk7Qs-0006qy-Dg; Fri, 04 May 2007 19:43:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hk7Qr-0006qs-6C
	for [e-mail]; Fri, 04 May 2007 19:43:25 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hk7Qp-00011J-Pg
	for [e-mail]; Fri, 04 May 2007 19:43:25 -0400
Received: from [10.20.30.108] (dsl-63-249-108-169.cruzio.com [63.249.108.169])
	(authenticated bits=0)
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l44NhLxx054587
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <[e-mail]>; Fri, 4 May 2007 16:43:23 -0700 (MST)
	(envelope-from [e-mail])
Mime-Version: 1.0
Message-Id: <p06240822c26175699f3d@[10.20.30.108]>
Date: Fri, 4 May 2007 16:42:54 -0700
To: IPsec WG <[e-mail]>
From: [e-mail]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.8 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Subject: [Ipsec] RFC 4868 on Using HMAC-SHA-256, HMAC-SHA-384,
 and HMAC-SHA-512 with IPsec
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Security <ipsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:[e-mail]?subject=unsubscribe>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipsec>,
	<mailto:[e-mail]?subject=subscribe>
Errors-To: [e-mail]


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


         RFC 4868

         Title:      Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512
                     with IPsec
         Author:     S. Kelly, S. Frankel
         Status:     Standards Track
         Date:       May 2007
         Mailbox:    [e-mail],
                     [e-mail]
         Pages:      21
         Characters: 41432
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-kelly-ipsec-ciph-sha2-01.txt

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

This specification describes the use of Hashed Message Authentication
Mode (HMAC) in conjunction with the SHA-256, SHA-384, and SHA-512
algorithms in IPsec.  These algorithms may be used as the basis for
data origin authentication and integrity verification mechanisms for
the Authentication Header (AH), Encapsulating Security Payload (ESP),
Internet Key Exchange Protocol (IKE), and IKEv2 protocols, and also
as Pseudo-Random Functions (PRFs) for IKE and IKEv2.  Truncated
output lengths are specified for the authentication-related variants,
with the corresponding algorithms designated as HMAC-SHA-256-128,
HMAC-SHA-384-192, and HMAC-SHA-512-256.  The PRF variants are not
truncated, and are called PRF-HMAC-SHA-256, PRF-HMAC-SHA-384, and
PRF-HMAC-SHA-512.  [STANDARDS TRACK]

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body

help: ways_to_get_rfcs. For example:

         To: [e-mail]
         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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...

_______________________________________________
Ipsec mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ipsec