Re: [mile] AD review of Implementation draft
Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp> Mon, 23 May 2016 12:22 UTC
Return-Path: <daisu-mi@nc.u-tokyo.ac.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 4308812D7E0 for <mile@ietfa.amsl.com>; Mon, 23 May 2016 05:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level:
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 33bIcK7gB8eD for <mile@ietfa.amsl.com>; Mon, 23 May 2016 05:22:56 -0700 (PDT)
Received: from skyblue2.nc.u-tokyo.ac.jp (skyblue2.nc.u-tokyo.ac.jp [133.11.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id 4452512D7DB for <mile@ietf.org>; Mon, 23 May 2016 05:22:55 -0700 (PDT)
Received: from [IPv6:2001:200:180:305:a5ea:59d5:177d:7182] (unknown [IPv6:2001:200:180:305:a5ea:59d5:177d:7182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by skyblue2.nc.u-tokyo.ac.jp (Postfix) with ESMTPSA id E4EF6B9CC070; Mon, 23 May 2016 21:22:53 +0900 (JST)
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, MILE IETF <mile@ietf.org>
References: <CAHbuEH7vJsYb53+LxVF_fprwLzLevUKn5FgfGeujjMu8YWk9yQ@mail.gmail.com>
From: Daisuke MIYAMOTO <daisu-mi@nc.u-tokyo.ac.jp>
Message-ID: <820564a3-9a9c-0c91-fc3c-e358970809a2@nc.u-tokyo.ac.jp>
Date: Mon, 23 May 2016 21:23:15 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAHbuEH7vJsYb53+LxVF_fprwLzLevUKn5FgfGeujjMu8YWk9yQ@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="wnLUGfqRDlcMvojEhsolTL9DAXiWLPAPB"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/13zayVkO_qcwC7_lrsb5Ut3inOE>
Subject: Re: [mile] AD review of Implementation draft
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: Mon, 23 May 2016 12:22:58 -0000
Dear Kathleen, Thank you very much for your support. I will amend our draft until the end of the month. Kind regards, Daisuke On 2016/05/20 4:47, Kathleen Moriarty wrote: > Hello, > > Thank you for your work on the implementation report, it looks great! > I have some comments, which are mostly nits that should be addressed > before I initiate the IETF last call. I also need to look into the > links included as informative references as they may not be considered > stable, so I'll get back to you on that as well. > > Section 1: > > We'll have trouble with http://siis.realmv6.org/implementations/ as a > stable reference, but I'm not sure what to do about that and will get > back to you. > > Section 2.3 > nit: > s/fro/for/ > Research and Education Networking Information Sharing and Analysis > Center (REN-ISAC) is a private community of the research and higher > education members fro sharing > > Consider changing from: > REN-ISAC also recommends to use of the IODEF attachment provided with > the notification email be processed rather than relying on parsing of > the email body text. The interface provided by REN-ISAC are designed > for dealing with such email. > To: > REN-ISAC also recommends to use an IODEF attachment provided with > a notification email for processing rather than relying on parsing of > the email body text. The interface provided by REN-ISAC are designed > to handle such email. > > Section 3.1 > > Probably not necessary to include "Internet Engineering Task Force", > just IETF is enough as it's a well known acronym. > > Section 6.2 > Is IDMEF expanded anywhere? What is SNML? > > Section 6.3 > s/IODEf/IODEF/ > and > s/IODef/IODEF/ > > > Thank you! >
- [mile] AD review of Implementation draft Kathleen Moriarty
- Re: [mile] AD review of Implementation draft Daisuke MIYAMOTO
- Re: [mile] AD review of Implementation draft Daisuke MIYAMOTO
- Re: [mile] AD review of Implementation draft Kathleen Moriarty