JSON binding of IODEF
draft-ietf-mile-jsoniodef-01

Document Type Active Internet-Draft (mile WG)
Last updated 2017-11-11
Replaces draft-takahashi-mile-jsoniodef
Stream IETF
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
MILE                                                        T. Takahashi
Internet-Draft                                                 M. Suzuki
Intended status: Standards Track                                    NICT
Expires: May 14, 2018                                  November 10, 2017

                         JSON binding of IODEF
                      draft-ietf-mile-jsoniodef-01

Abstract

   RFC 7970 [RFC7970] provides XML-based data representation on incident
   information, but the use of the IODEF data model is not limited to
   XML.  JSON representation is sometimes preferred since it is easy to
   handle from certain programming environments.  This draft represents
   the IODEF data model in JSON.

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 https://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 May 14, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (https://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Takahashi & Suzuki        Expires May 14, 2018                  [Page 1]
Internet-Draft                 JSON-IODEF                  November 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  IODEF Data Types  . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Integers  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Real Numbers  . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Characters and Strings  . . . . . . . . . . . . . . . . .   4
     2.4.  Multilingual Strings  . . . . . . . . . . . . . . . . . .   5
     2.5.  Binary Strings  . . . . . . . . . . . . . . . . . . . . .   5
       2.5.1.  Base64 Bytes  . . . . . . . . . . . . . . . . . . . .   5
       2.5.2.  Hexadecimal Bytes . . . . . . . . . . . . . . . . . .   5
     2.6.  Enumerated Types  . . . . . . . . . . . . . . . . . . . .   5
     2.7.  Date-Time String  . . . . . . . . . . . . . . . . . . . .   5
     2.8.  Timezone String . . . . . . . . . . . . . . . . . . . . .   6
     2.9.  Port Lists  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.10. Postal Address  . . . . . . . . . . . . . . . . . . . . .   6
     2.11. Telephone Number  . . . . . . . . . . . . . . . . . . . .   6
     2.12. Email String  . . . . . . . . . . . . . . . . . . . . . .   6
     2.13. Uniform Resource Locator Strings  . . . . . . . . . . . .   6
     2.14. Identifiers and Identifier References . . . . . . . . . .   7
     2.15. Software  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.16. StructuredInfo  . . . . . . . . . . . . . . . . . . . . .   7
   3.  The IODEF Information Model in JSON . . . . . . . . . . . . .   8
     3.1.  IODEF-Document Class  . . . . . . . . . . . . . . . . . .   8
     3.2.  Incident Class  . . . . . . . . . . . . . . . . . . . . .   8
     3.3.  Common Attributes . . . . . . . . . . . . . . . . . . . .   9
       3.3.1.  restriction Attribute . . . . . . . . . . . . . . . .   9
       3.3.2.  observable-id Attribute . . . . . . . . . . . . . . .   9
     3.4.  IncidentID Class  . . . . . . . . . . . . . . . . . . . .   9
     3.5.  AlternativeID Class . . . . . . . . . . . . . . . . . . .  10
     3.6.  RelatedActivity Class . . . . . . . . . . . . . . . . . .  10
     3.7.  ThreatActor Class . . . . . . . . . . . . . . . . . . . .  11
     3.8.  Campaign Class  . . . . . . . . . . . . . . . . . . . . .  11
     3.9.  Contact Class . . . . . . . . . . . . . . . . . . . . . .  11
       3.9.1.  RegistryHandle Class  . . . . . . . . . . . . . . . .  12
       3.9.2.  PostalAddress Class . . . . . . . . . . . . . . . . .  12
Show full document text