Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-07.txt
Mio Suzuki <mio@nict.go.jp> Tue, 15 November 2016 11:13 UTC
Return-Path: <mio@nict.go.jp>
X-Original-To: mile@ietfa.amsl.com
Delivered-To: mile@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72F41294DA for <mile@ietfa.amsl.com>; Tue, 15 Nov 2016 03:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id upLATXHs_2LD for <mile@ietfa.amsl.com>; Tue, 15 Nov 2016 03:13:12 -0800 (PST)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:df0:232:300::2]) by ietfa.amsl.com (Postfix) with ESMTP id B2EA91293DA for <mile@ietf.org>; Tue, 15 Nov 2016 03:13:11 -0800 (PST)
Received: from gw2.nict.go.jp (gw2.nict.go.jp [133.243.18.251]) by ns2.nict.go.jp with ESMTP id uAFBDAGw091680 for <mile@ietf.org>; Tue, 15 Nov 2016 20:13:10 +0900 (JST)
Received: from mail1.nict.go.jp (mail1.nict.go.jp [133.243.18.14]) by gw2.nict.go.jp with ESMTP id uAFBD9hQ091671; Tue, 15 Nov 2016 20:13:09 +0900 (JST)
Received: from [127.0.0.1] (ssh1.nict.go.jp [133.243.3.49]) by mail1.nict.go.jp (NICT Mail Spool Server1) with ESMTP id 7A025822C; Tue, 15 Nov 2016 20:13:09 +0900 (JST)
From: Mio Suzuki <mio@nict.go.jp>
Message-Id: <0909F8CB-7A9D-4DA6-BA36-E569BF47533B@nict.go.jp>
Content-Type: multipart/signed; boundary="Apple-Mail=_8642DD14-7618-4BC2-AAD8-E44E41EFFC21"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Date: Tue, 15 Nov 2016 20:13:07 +0900
In-Reply-To: <147920530534.10367.16282534584431920719.idtracker@ietfa.amsl.com>
To: MILE IETF <mile@ietf.org>
References: <147920530534.10367.16282534584431920719.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3251)
X-Virus-Scanned: clamav-milter 0.98.7 at zenith2
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/82Mqrn-ceGfwtMTqwoXmoBqudCs>
Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-07.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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 11:13:14 -0000
Hello, I’ve modified all examples of our draft to fit v2 schema. But I don’t have much confidence that the examples are contextually correct even after they have passed schema validation. Could you give me some comments? Regards, Mio > 2016/11/15 19:21、internet-drafts@ietf.org: > > > 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/ > > _______________________________________________ > mile mailing list > mile@ietf.org > https://www.ietf.org/mailman/listinfo/mile
- [mile] I-D Action: draft-ietf-mile-iodef-guidance… internet-drafts
- Re: [mile] I-D Action: draft-ietf-mile-iodef-guid… Mio Suzuki