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

The information below is for an old version of the document
Document Type Active Internet-Draft (mile WG)
Last updated 2016-05-09
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Takeshi Takahashi
Shepherd write-up Show (last changed 2016-04-21)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to rdd@cert.org, mile-chairs@tools.ietf.org, mile@ietf.org
MILE Working Group                                            R. Danyliw
Internet-Draft                                                      CERT
Obsoletes: 5070 (if approved)                                May 9, 2016
Intended status: Standards Track
Expires: November 10, 2016

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

Abstract

   The Incident Object Description Exchange Format (IODEF) defines a
   data representation for security incident reports and cyber
   indicators commonly exchanged by operational security teams for
   mitigation and watch and warning.  This document describes an updated
   information model for the IODEF and provides an associated data model
   specified with XML Schema.  This new information and data model
   obsoletes [RFC5070].

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 November 10, 2016.

Copyright Notice

   Copyright (c) 2016 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

Danyliw                 Expires November 10, 2016               [Page 1]
Internet-Draft                  IODEF v2                        May 2016

   include Simplified BSD License text as described in Section 4.e of
   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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   6
     1.2.  Notations . . . . . . . . . . . . . . . . . . . . . . . .   6
     1.3.  About the IODEF Data Model  . . . . . . . . . . . . . . .   6
     1.4.  Changelog . . . . . . . . . . . . . . . . . . . . . . . .   7
   2.  IODEF Data Types  . . . . . . . . . . . . . . . . . . . . . .   8
     2.1.  Integers  . . . . . . . . . . . . . . . . . . . . . . . .   8
     2.2.  Real Numbers  . . . . . . . . . . . . . . . . . . . . . .   8
     2.3.  Characters and Strings  . . . . . . . . . . . . . . . . .   8
     2.4.  Multilingual Strings  . . . . . . . . . . . . . . . . . .   9
     2.5.  Binary Strings  . . . . . . . . . . . . . . . . . . . . .  10
       2.5.1.  Base64 Bytes  . . . . . . . . . . . . . . . . . . . .  10
       2.5.2.  Hexadecimal Bytes . . . . . . . . . . . . . . . . . .  10
     2.6.  Enumerated Types  . . . . . . . . . . . . . . . . . . . .  10
     2.7.  Date-Time String  . . . . . . . . . . . . . . . . . . . .  10
     2.8.  Timezone String . . . . . . . . . . . . . . . . . . . . .  10
     2.9.  Port Lists  . . . . . . . . . . . . . . . . . . . . . . .  11
     2.10. Postal Address  . . . . . . . . . . . . . . . . . . . . .  11
     2.11. Telephone Number  . . . . . . . . . . . . . . . . . . . .  11
     2.12. Email String  . . . . . . . . . . . . . . . . . . . . . .  11
     2.13. Uniform Resource Locator strings  . . . . . . . . . . . .  11
     2.14. Identifiers and Identifier References . . . . . . . . . .  12
     2.15. Software  . . . . . . . . . . . . . . . . . . . . . . . .  12
       2.15.1.  SoftwareReference Class  . . . . . . . . . . . . . .  13
     2.16. Extension . . . . . . . . . . . . . . . . . . . . . . . .  14
   3.  The IODEF Information Model . . . . . . . . . . . . . . . . .  17
Show full document text