The Incident Object Description Exchange Format v2
draft-ietf-mile-rfc5070-bis-15

The information below is for an old version of the document
Document Type Active Internet-Draft (mile WG)
Last updated 2015-10-16
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Apr 2016 - Submit an update of ... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MILE Working Group                                            R. Danyliw
Internet-Draft                                                      CERT
Obsoletes: 5070 (if approved)                                P. Stoecker
Intended status: Standards Track                                     RSA
Expires: April 18, 2016                                 October 16, 2015

           The Incident Object Description Exchange Format v2
                     draft-ietf-mile-rfc5070-bis-15

Abstract

   The Incident Object Description Exchange Format (IODEF) defines a
   data representation for sharing information commonly exchanged by
   Computer Security Incident Response Teams (CSIRTs) about computer
   security incidents.  This document describes the information model
   for the IODEF and provides an associated data model specified with
   XML Schema.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 18, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Danyliw & Stoecker       Expires April 18, 2016                 [Page 1]
Internet-Draft                   IODEFv2                    October 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.1.  Changes from 5070 . . . . . . . . . . . . . . . . . . . .   6
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   7
     1.3.  Notations . . . . . . . . . . . . . . . . . . . . . . . .   8
     1.4.  About the IODEF Data Model  . . . . . . . . . . . . . . .   8
     1.5.  About the IODEF Implementation  . . . . . . . . . . . . .   9
   2.  IODEF Data Types  . . . . . . . . . . . . . . . . . . . . . .   9
     2.1.  Integers  . . . . . . . . . . . . . . . . . . . . . . . .   9
     2.2.  Real Numbers  . . . . . . . . . . . . . . . . . . . . . .   9
     2.3.  Characters and Strings  . . . . . . . . . . . . . . . . .  10
     2.4.  Multilingual Strings  . . . . . . . . . . . . . . . . . .  10
     2.5.  Bytes . . . . . . . . . . . . . . . . . . . . . . . . . .  11
     2.6.  Hexadecimal Bytes . . . . . . . . . . . . . . . . . . . .  11
     2.7.  Enumerated Types  . . . . . . . . . . . . . . . . . . . .  11
     2.8.  Date-Time Strings . . . . . . . . . . . . . . . . . . . .  11
     2.9.  Timezone String . . . . . . . . . . . . . . . . . . . . .  11
     2.10. Port Lists  . . . . . . . . . . . . . . . . . . . . . . .  12
     2.11. Postal Address  . . . . . . . . . . . . . . . . . . . . .  12
     2.12. Person or Organization  . . . . . . . . . . . . . . . . .  12
     2.13. Telephone and Fax Numbers . . . . . . . . . . . . . . . .  12
     2.14. Email String  . . . . . . . . . . . . . . . . . . . . . .  12
     2.15. Uniform Resource Locator strings  . . . . . . . . . . . .  13
     2.16. Identifiers and Identifier References . . . . . . . . . .  13
   3.  The IODEF Data Model  . . . . . . . . . . . . . . . . . . . .  13
     3.1.  IODEF-Document Class  . . . . . . . . . . . . . . . . . .  13
     3.2.  Incident Class  . . . . . . . . . . . . . . . . . . . . .  14
Show full document text