[mile] Stephen Farrell's Abstain on draft-ietf-mile-implementreport-09: (with COMMENT)
"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Wed, 29 June 2016 13:29 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 CA74712D107; Wed, 29 Jun 2016 06:29:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160629132958.18857.3496.idtracker@ietfa.amsl.com>
Date: Wed, 29 Jun 2016 06:29:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/l6hnMObdfm-u6yf-vCj6SCcRsRg>
Cc: mile@ietf.org, mile-chairs@tools.ietf.org, draft-ietf-mile-implementreport@ietf.org, mile-chairs@ietf.org
Subject: [mile] Stephen Farrell's Abstain on draft-ietf-mile-implementreport-09: (with COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.17
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, 29 Jun 2016 13:29:59 -0000
Stephen Farrell has entered the following ballot position for draft-ietf-mile-implementreport-09: Abstain 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-implementreport/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I concur with Alvaro and Ben on this one. There is too much that is too close to marketing text and that would not really help an implementer or someone investigating these RFCs, or someone further developing those RFCs. It seems to me that only sections 7.1 and 7.4 contain the kind of information that I'd expect to find in an RFC like this. As far as I can see only those two sections actually refer to sections of, or content from, the RFCs concerned in a way that is useful to document in an RFC. I also could not access the URL in section 1. That seems like it really would need fixing. (I will admit that I may be somewhat biased here - IMO any document with 26+ occurrences of the string "cyber" is likely not a good candidate for an RFC;-)
- [mile] Stephen Farrell's Abstain on draft-ietf-mi… Stephen Farrell