[mile] I-D Action: draft-ietf-mile-iodef-guidance-07.txt

internet-drafts@ietf.org Tue, 15 November 2016 10:21 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5457C129400; Tue, 15 Nov 2016 02:21:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147920530534.10367.16282534584431920719.idtracker@ietfa.amsl.com>
Date: Tue, 15 Nov 2016 02:21:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/khr8hyqWJWVTRgJB3mqtUBnBNEY>
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-07.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "Managed Incident Lightweight Exchange, IODEF extensions and RID exchanges" <mile.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mile>, <mailto:mile-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mile/>
List-Post: <mailto:mile@ietf.org>
List-Help: <mailto:mile-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mile>, <mailto:mile-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2016 10:21:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Managed Incident Lightweight Exchange of the IETF.

        Title           : IODEF Usage Guidance
        Authors         : Panos Kampanakis
                          Mio Suzuki
	Filename        : draft-ietf-mile-iodef-guidance-07.txt
	Pages           : 31
	Date            : 2016-11-15

Abstract:
   The Incident Object Description Exchange Format v2
   [I-D.ietf-mile-rfc5070-bis] 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 security practicioners to develop
   tools that can leverage IODEF for incident sharing.  This document
   provides guidelines for IODEF practicioners.  It also addresses how
   common security indicators can be represented in IODEF and use-cases
   of how IODEF is being used so far.  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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mile-iodef-guidance-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/