RFC - 4305

Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)

Original:	ftp://ftp.isi.edu/in-notes/rfc4305.txt
Authors:	D. Eastlake 3rd [Motorola Laboratories]
Date:	December 2005
Category:	Informational
This specification has been !!! obsoleted !!!

---

Obsoleted by:
RFC-4835prop	Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)

Obsoletes:
RFC-2406	IP Encapsulating Security Payload (ESP) (Obsoleted by RFC-4303prop, RFC-4305 -> RFC-4835prop)
RFC-2402	IP Authentication Header (Obsoleted by RFC-4302prop, RFC-4305 -> RFC-4835prop)

Referred by:	8 RFC
Refers to:	18 RFC

---

Status

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.

Copyright Notice

Copyright (C) The Internet Society (2005).

Abstract

The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Encapsulating Security Payload (ESP) and the Authentication Header (AH) provide two mechanisms for protecting data being sent over an IPsec Security Association (SA). 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 mandatory-to-implement algorithms for ESP and AH as well as specifying algorithms that should be implemented because they may be promoted to mandatory at some future time.

---