%% You should probably cite rfc8274 instead of this I-D.
@techreport{ietf-mile-iodef-guidance-00,
    number =    {draft-ietf-mile-iodef-guidance-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/00/},
    author =    {Panos Kampanakis},
    title =     {{IODEF Usage Guidance}},
    pagetotal = 7,
    year =      2013,
    month =     apr,
    day =       30,
    abstract =  {The Incident Object Description Exchange Format {[}RFC5070{]} defines a data representation that provides a framework for sharing information commonly exchanged by Computer Security Incident Response Teams (CSIRTs) about computer security incidents. Since the IODEF model includes a wealth of available options that can be used to describe a security incident or issue, it can be challenging for implementers to develop tools that can Leverage IODEF for incident sharing. This document provides guidelines for IODEF users and implementers. It will also address how common security indicators can be represented in IODEF. The goal of this document is to make IODEF's adoption by vendors easier and encourage faster and wider adoption of the model by Computer Security Incident Response Teams (CSIRTs) around the world.},
}