Content Requirements for ISAKMP Notify Messages
draft-ietf-ipsec-notifymsg-04
| Document | Type | Expired Internet-Draft (ipsec WG) | |
|---|---|---|---|
| Authors | Scott G. Kelly , Tero Kivinen | ||
| Last updated | 2000-11-29 (Latest revision 2000-07-06) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-ietf-ipsec-notifymsg-04.txt
Abstract
The ISAKMP and DOI RFCs [RFC2408, RFC2407] specify error and status message types for use in ISAKMP NOTIFY messages, but in some cases do not specify that any additional clarifying data be carried in the messages. In these cases, it is difficult to determine which SA corresponds to the received NOTIFY message. While the DOI RFC specifies content and formats for additional data in the currently defined IPSEC status messages, no such requirements are currently specified for ISAKMP NOTIFY messages. This document provides content and format recommendations for those messages.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)