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

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 14 September 2017 19:37 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 089921241F3; Thu, 14 Sep 2017 12:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DUOO33Ca64I1; Thu, 14 Sep 2017 12:37:26 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BE40132EBB; Thu, 14 Sep 2017 12:37:26 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id v66so213569pgb.5; Thu, 14 Sep 2017 12:37:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=chJlXzH71FDnWwWbKzN6CHCU9VrhlatxR/afN3Ut1LI=; b=GicOsMUP0Qx4FygZkRitbMlu+VSLON8WK2UzXFtNknQaJzHGciF5PmpMEYGqr1ukpJ bnlxSEKpSDxt6b6Oeu2nibFLQgWZrSq0dN5RwgHYof39jC6DhVFsbNJOaoRBtFDURTH1 lqniSMIaZMV99XC+kTx6fyuE7T9HjU8srIPOKSH3yvP76K03ULsKDBQEgrFZmQfVDApM 0+x/AEaFiZ1s1Ts6l9YT2Nsah6XrYK/QbGVqtM9DV8Dch+BT1W+JISzZLmHhSlWq1ilG /Mbw5/u2IRXUSjA8ulXntG/QxiMlzQH3L3yhEkJCHyHDVrIYomWbhpieth/LJTgjz3OW ROrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=chJlXzH71FDnWwWbKzN6CHCU9VrhlatxR/afN3Ut1LI=; b=I28sPLEK86XffhXM75kQk+j4lWZeWoRvbkV8nIIRhXD747MCUFvv6RMxmNBcFlMAJR KNv3opawbeX4vqHJ6Z3UNLRsD/VllEvRmIKSnJ0KrYw0nLguCyeKKzkUm7c+wyr30SdS IZP7xQwYE9qwV6r9rMwlUVfvajYUa+rIAGPpHG+h/Bx9vHluLXCbhtT/FZmx/aNF0YWX NFBg78GH2DBe2Ep3kSb1LpDW5CKP0pdY80f/GUspUHgUL4zldRPYBuviAGV1VU3WFwel kCy5JZhPX6w1yGWUoNoel+2HLH7TWALrAyzDW17b12dYvQQJn+FrGulwXip3foF7RqYd gnJA==
X-Gm-Message-State: AHPjjUgmmyRk2z5F79S+XzhjgzSYqFumo8w8G1ZsiMDATbeTDgzGpCqc NAD3sJ0pn6N4eQIAoewEmSEgxR3dGaI/HJtobxU=
X-Google-Smtp-Source: ADKCNb575fj7v1ox1G6ZEtiaOdDOGcg1jolKdaXKO8IrPdMCMh18FbHNQaiC9le4S6p63oT12ukG9Ret4+Yefks5aVU=
X-Received: by 10.98.68.206 with SMTP id m75mr22744717pfi.163.1505417845837; Thu, 14 Sep 2017 12:37:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.144.1 with HTTP; Thu, 14 Sep 2017 12:36:45 -0700 (PDT)
In-Reply-To: <CAHbuEH7gAF1xE9vAd5OrSKH8Rq=bg9KWjXLHxTisQnX8arf50g@mail.gmail.com>
References: <150480529516.8033.6404431491813730506@ietfa.amsl.com> <51d747dcf46749c496f4ed94401f39c9@XCH-ALN-010.cisco.com> <CAHbuEH7gAF1xE9vAd5OrSKH8Rq=bg9KWjXLHxTisQnX8arf50g@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 14 Sep 2017 15:36:45 -0400
Message-ID: <CAHbuEH5h9+VHon_TmniNgY0zZDn1k+akXEZE3c9RvAm1Bzfmaw@mail.gmail.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
Cc: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "mile@ietf.org" <mile@ietf.org>, "draft-ietf-mile-iodef-guidance@ietf.org" <draft-ietf-mile-iodef-guidance@ietf.org>, The IESG <iesg@ietf.org>, "mile-chairs@ietf.org" <mile-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/YLIU1f3jcYaEM7CX1Y5lGmQKqGs>
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, 14 Sep 2017 19:37:35 -0000

Hello,

I read the draft again and think it reads very well now, thank you for
your work on it Panos.  The normative language has been removed as
requested.  I don't have a strong opinion as to whether this should go
forward as informational or as a BCP.  The IESG hasn't weighed in any
further (but are of course welcome to do so), do the chairs have a
strong opinion here?

Another last call would be required if it were to be switched to a
BCP, but that's not too big of a deal if it is the preferred path
forward.  I'm happy to have a call with the chairs and author if it's
helpful to walk through this so we can decide on the go forward plan.
We can coordinate that without the full list copied on this message
and just report back.

Thank you,
Kathleen

On Thu, Sep 7, 2017 at 1:55 PM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:
> 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



-- 

Best regards,
Kathleen