Skip to main content

TERENA'S Incident Object Description and Exchange Format Requirements

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3067.
Authors Jimmy Arvidsson , Jan Meijer , Andrew Cormack , Yuri Demchenko
Last updated 2013-03-02 (Latest revision 2000-11-15)
RFC stream Legacy stream
Intended RFC status Informational
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3067 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3067

        Title:      TERENA'S Incident object Description and Exchange
                    Format Requirements
        Author(s):  J. Arvidsson, A. Cormack, Y. Demchenko, J. Meijer
        Status:     Informational
        Date:       February 2001
        Pages:      17
        Characters: 36836
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-terena-itdwg-iodef-requirements-00.txt


The purpose of the Incident Object Description and Exchange Format is
to define a common data format for the description, archiving and
exchange of information about incidents between CSIRTs (Computer
Security Incident Response Teams) (including alert, incident in
investigation, archiving, statistics, reporting, etc.).  This document
describes the high-level requirements for such a description and
exchange format, including the reasons for those requirements.
Examples are used to illustrate the requirements where necessary.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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

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.