[mile] Warren Kumari's No Objection on draft-ietf-mile-iodef-guidance-10: (with COMMENT)
Warren Kumari <warren@kumari.net> Wed, 30 August 2017 19:28 UTC
Return-Path: <warren@kumari.net>
X-Original-To: mile@ietf.org
Delivered-To: mile@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2FAE1326EA; Wed, 30 Aug 2017 12:28:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari <warren@kumari.net>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-mile-iodef-guidance@ietf.org, mile-chairs@ietf.org, ncamwing@cisco.com, mile@ietf.org, bill.wu@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150412129792.21599.7418826747975474337.idtracker@ietfa.amsl.com>
Date: Wed, 30 Aug 2017 12:28:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/B847vBJMqWuZpiiRBfCHD2Thz0U>
Subject: [mile] Warren Kumari's No Objection on draft-ietf-mile-iodef-guidance-10: (with COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 30 Aug 2017 19:28:18 -0000
Warren Kumari has entered the following ballot position for draft-ietf-mile-iodef-guidance-10: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-mile-iodef-guidance/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I'll also echo Ben / Benoit's comments and also thank Qin Wu for the OpsDir review. I've just seen that you have responded to it, thank you. I especially don't understand the: "Interoperability between RID agents and the standards, Use of [RFC6545] and [RFC6546], were also proven in this exercise." -- is the "Use of" superfluous? I *think* so, and removing it fixes it, but I'm not quite sure what was intended. Many of the nit checker things seem simply to solve (like the use of non-documentation addresses) - these should be addressed. In addition I have some nits: Section3.1. "Minimal IODEF document IODEF includes one mandatory classes. " s/classes/class/ Section 3.2. Information represented " The implementer should carefully look into the schema and decide classes to implement (or not)." -- I think this is missing a "which" between "decide" and "classes".
- [mile] Warren Kumari's No Objection on draft-ietf… Warren Kumari
- Re: [mile] Warren Kumari's No Objection on draft-… Panos Kampanakis (pkampana)
- Re: [mile] Warren Kumari's No Objection on draft-… Warren Kumari