[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-ietf-inch-iodef-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Extended Incident Handling Working Group of the IETF.

	Title		: Incident Object Description and Exchange Format Data 
                          Model and Extensible Markup Language (XML)
                          Document Type Definition
	Author(s)	: J. Meijer et al.
	Filename	: draft-ietf-inch-iodef-00.txt
	Pages		: 0
	Date		: 2002-10-29
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.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-inch-iodef-00.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-inch-iodef-00.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the