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

Internet-Drafts@ietf.org Tue, 05 November 2002 13:24 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17372; Tue, 5 Nov 2002 08:24:54 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA00885 for ietf-123-outbound.10@ietf.org; Tue, 5 Nov 2002 08:25:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA28755 for <all-ietf@loki.ietf.org>; Tue, 5 Nov 2002 06:07:04 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09990; Tue, 5 Nov 2002 06:04:35 -0500 (EST)
Message-Id: <200211051104.GAA09990@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: inch@nic.surfnet.nl
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-inch-iodef-rfc3067bis-requirements-00.txt
Date: Tue, 05 Nov 2002 06:04:35 -0500
Sender: nsyracus@cnri.reston.va.us

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 
                          Requirements
	Author(s)	: Y. Demchenko
	Filename	: draft-ietf-inch-iodef-rfc3067bis-requirements-00.txt
	Pages		: 15
	Date		: 2002-11-4
	
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:
http://www.ietf.org/internet-drafts/draft-ietf-inch-iodef-rfc3067bis-requirements-00.txt

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-rfc3067bis-requirements-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-inch-iodef-rfc3067bis-requirements-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
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-inch-iodef-rfc3067bis-requirements-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-inch-iodef-rfc3067bis-requirements-00.txt>