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

Thank you, Panos.

I'll take a look through the document.  Some on the IESG felt this
should be a BCP and it didn't have that feel to me, but when I read it
again, I'll consider this and get back to you.  If others on the IESG
have shifted their opinion, please do let me know.

Best regards,
Kathleen

On Thu, Sep 7, 2017 at 1:39 PM, Panos Kampanakis (pkampana)
<pkampana@cisco.com> wrote:
> 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
>

-- 

Best regards,
Kathleen