Incident Object Description and Exchange Format
Requirements
draft-ietf-inch-iodef-rfc3067bis-requirements-00
| Document | Type |
Expired Internet-Draft
(inch WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Yuri Demchenko | ||
| Last updated | 2004-08-24 (Latest revision 2002-11-04) | ||
| 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
The purpose of the Incident Object Description and Exchange Format is to define a common data format for describing and exchanging incident information between collaborating Computer Security Incident Response Teams (CSIRTs). The specific goals and requirements of the IODEF are described in [2]. One of the design principles in the IODEF is compatibility with the Intrusion Detection Message Exchange Format (IDMEF) [3] developed for intrusion detection systems. For this reason, IODEF is heavily based on the IDMEF and provides upward compatibility with it.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)