idnits 2.17.1 draft-terena-itdwg-iodef-requirements-00.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3067 5 Title: TERENA'S Incident object Description and Exchange 6 Format Requirements 7 Author(s): J. Arvidsson, A. Cormack, Y. Demchenko, J. Meijer 8 Status: Informational 9 Date: February 2001 10 Mailbox: Jimmy.J.Arvidsson@telia.se, 11 Andrew.Cormack@ukerna.ac.uk, demch@terena.nl, 12 jan.meijer@surfnet.nl 13 Pages: 17 14 Characters: 36836 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-terena-itdwg-iodef-requirements-00.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3067.txt 21 The purpose of the Incident Object Description and Exchange Format is 22 to define a common data format for the description, archiving and 23 exchange of information about incidents between CSIRTs (Computer 24 Security Incident Response Teams) (including alert, incident in 25 investigation, archiving, statistics, reporting, etc.). This document 26 describes the high-level requirements for such a description and 27 exchange format, including the reasons for those requirements. 28 Examples are used to illustrate the requirements where necessary. 30 This memo provides information for the Internet community. It does 31 not specify an Internet standard of any kind. Distribution of this 32 memo is unlimited. 34 This announcement is sent to the IETF list and the RFC-DIST list. 35 Requests to be added to or deleted from the IETF distribution list 36 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 37 added to or deleted from the RFC-DIST distribution list should 38 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 40 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 41 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 42 help: ways_to_get_rfcs. For example: 44 To: rfc-info@RFC-EDITOR.ORG 45 Subject: getting rfcs 47 help: ways_to_get_rfcs 49 Requests for special distribution should be addressed to either the 50 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 51 specifically noted otherwise on the RFC itself, all RFCs are for 52 unlimited distribution.echo 53 Submissions for Requests for Comments should be sent to 54 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 55 Authors, for further information.