RFC 3067 on IODEF Requirements
RFC Editor <rfc-ed@ISI.EDU> Wed, 28 February 2001 01:11 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08058; Tue, 27 Feb 2001 20:11:08 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA28403 for ietf-123-outbound.10@ietf.org; Tue, 27 Feb 2001 20:05:03 -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 TAA28326 for <all-ietf@loki.ietf.org>; Tue, 27 Feb 2001 19:55:21 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA07730 for <all-ietf@ietf.org>; Tue, 27 Feb 2001 19:55:14 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f1S0tCG07058; Tue, 27 Feb 2001 16:55:12 -0800 (PST)
Message-Id: <200102280055.f1S0tCG07058@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3067 on IODEF Requirements
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 27 Feb 2001 16:55:12 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
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 Mailbox: Jimmy.J.Arvidsson@telia.se, Andrew.Cormack@ukerna.ac.uk, demch@terena.nl, jan.meijer@surfnet.nl Pages: 17 Characters: 36836 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-terena-itdwg-iodef-requirements-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3067.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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3067 on IODEF Requirements RFC Editor