IETF Logo Mail Archive

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

"Panos Kampanakis (pkampana)" <pkampana@cisco.com> Thu, 07 September 2017 17:39 UTC

Return-Path: <pkampana@cisco.com>
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 E41FB132F99; Thu, 7 Sep 2017 10:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 w4gMYxKXG7Dm; Thu, 7 Sep 2017 10:39:57 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40C17132F83; Thu, 7 Sep 2017 10:39:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2956; q=dns/txt; s=iport; t=1504805997; x=1506015597; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=cbh/E7fnuDpsU1LnDOyPs9CwjEtwA4aEfnHXlpPXdbc=; b=iuJZnUBzzGpmkGID7PjDoR4URqa0LK6pHTKBLUI/iJ5uifZP0LFx53XB bVc3MswrHXM2VJ10sCt38VpaRhdghg61niQvvCft9AFaR/CYHOa9jX54s sgSHPXtP47AnG3R7wdBf2X4I/4WrYqZz4TVKj2rQGbgTMboRiyeWVovxy 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AiAQDcg7FZ/4QNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1pkbicHjhGQIYFxliiCEgoYC4UbAoQDPxgBAgEBAQEBAQFrHQuFGAEBAQQBATg0CwwEAgEIEQQBAR8JBycLFAkIAgQOBQiKKRCwOIs7AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYMqggKBToFjgyiDJodDBaB0AodZjG2CHFqFDYp3lH4CERkBgTgBHziBDXcVHyqHG3aJGoEPAQEB
X-IronPort-AV: E=Sophos;i="5.42,359,1500940800"; d="scan'208";a="292581308"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Sep 2017 17:39:56 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v87HduCp024531 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 7 Sep 2017 17:39:56 GMT
Received: from xch-aln-010.cisco.com (173.36.7.20) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 7 Sep 2017 12:39:55 -0500
Received: from xch-aln-010.cisco.com ([173.36.7.20]) by XCH-ALN-010.cisco.com ([173.36.7.20]) with mapi id 15.00.1263.000; Thu, 7 Sep 2017 12:39:55 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
CC: "mile@ietf.org" <mile@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mile-iodef-guidance@ietf.org" <draft-ietf-mile-iodef-guidance@ietf.org>
Thread-Topic: [mile] I-D Action: draft-ietf-mile-iodef-guidance-11.txt
Thread-Index: AQHTJ/7CUR4wGt8PDESJLfWE4CGe8aKprjQQ
Date: Thu, 07 Sep 2017 17:39:55 +0000
Message-ID: <51d747dcf46749c496f4ed94401f39c9@XCH-ALN-010.cisco.com>
References: <150480529516.8033.6404431491813730506@ietfa.amsl.com>
In-Reply-To: <150480529516.8033.6404431491813730506@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.108.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/DgVXkcdCVgkuWKUmO7AWjw_zsXY>
Subject: Re: [mile] I-D Action: draft-ietf-mile-iodef-guidance-11.txt
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 07 Sep 2017 17:40:00 -0000

This submission addresses all reviews from the IESG Last call.

Thank you to all the reviewers. 

We updated normative language to have an Informational draft tones. 
We fixed figures and the minimal class figures. 
We fixed multiple nits, clarifications and text issues found by reviewers.
We also addressed the id-nits nits that made sense except for the ones that complain about long lines.

The draft should be ready now. 

Please let us know if there are more nits that need addressing. 

Regards,
Panos


-----Original Message-----
From: mile [mailto:mile-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Thursday, September 07, 2017 1:28 PM
To: i-d-announce@ietf.org
Cc: mile@ietf.org
Subject: [mile] I-D Action: draft-ietf-mile-iodef-guidance-11.txt


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 WG of the IETF.

        Title           : Incident Object Description Exchange Format Usage Guidance
        Authors         : Panos Kampanakis
                          Mio Suzuki
	Filename        : draft-ietf-mile-iodef-guidance-11.txt
	Pages           : 32
	Date            : 2017-09-07

Abstract:
   The Incident Object Description Exchange Format (IODEF) v2 (RFC7970)
   defines a data representation that provides a framework for sharing
   information about computer security incidents commonly exchanged by
   Computer Security Incident Response Teams (CSIRTs) .  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 practitioners to develop tools that leverage IODEF for
   incident sharing.  This document provides guidelines for IODEF
   implementers.  It addresses how common security indicators can be
   represented in IODEF and use-cases of how IODEF is being used.  This
   document aims to make IODEF's adoption by vendors easier and
   encourage faster and wider adoption of the model by CSIRTs around the
   world.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mile-iodef-guidance-11
https://datatracker.ietf.org/doc/html/draft-ietf-mile-iodef-guidance-11

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


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

v2.23.0 | Report a Bug | By Email