<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-inch-iodef-rfc3067bis-requirements" target="https://datatracker.ietf.org/doc/html/draft-ietf-inch-iodef-rfc3067bis-requirements-00">
   <front>
      <title>Incident Object Description and Exchange Format 
Requirements</title>
      <author initials="Y." surname="Demchenko" fullname="Yuri Demchenko">
         <organization>TERENA</organization>
      </author>
      <date month="November" day="4" year="2002" />
      <abstract>
	 <t>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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-inch-iodef-rfc3067bis-requirements-00" />
   
</reference>
