RFC 2857 on HMAC-RIPEMD-160-96 within ESP and AH
RFC Editor <rfc-ed@ISI.EDU> Fri, 16 June 2000 15:55 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id IAA15950; Fri, 16 Jun 2000 08:55:45 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id KAA10509 Fri, 16 Jun 2000 10:15:35 -0400 (EDT)
Message-Id: <200006152215.PAA22277@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2857 on HMAC-RIPEMD-160-96 within ESP and AH
Cc: rfc-ed@ISI.EDU, ipsec@lists.tislabs.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 15 Jun 2000 15:15:53 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
A new Request for Comments is now available in online RFC libraries.
RFC 2857
Title: The Use of HMAC-RIPEMD-160-96 within ESP and AH
Author(s): A. Keromytis, N. Provos
Status: Standards Track
Date: June 2000
Mailbox: angelos@dsl.cis.upenn.edu, provos@citi.umich.edu
Pages: 7
Characters: 13544
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsec-auth-hmac-ripemd-160-96-04.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2857.txt
This memo describes the use of the HMAC algorithm [RFC 2104] in
conjunction with the RIPEMD-160 algorithm [RIPEMD-160] as an
authentication mechanism within the revised IPSEC Encapsulating
Security Payload [ESP] and the revised IPSEC Authentication Header
[AH]. HMAC with RIPEMD-160 provides data origin authentication and
integrity protection.
Further information on the other components necessary for ESP and AH
implementations is provided by [Thayer97a].
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 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.echo
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.