Using Isakmp Message Ids for Replay Protection
draft-ietf-ipsec-antireplay-00
| Document | Type |
Expired Internet-Draft
(ipsec WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Krywaniuk | ||
| Last updated | 2001-07-17 (Latest revision 2001-07-13) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a method for adding explicit replay protection to IKE messages by altering the use of the message id in the ISAKMP header. We suggest that this change could be applied as part of the next revision of IKE.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)