[mile] Alexey Melnikov's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and COMMENT)

"Alexey Melnikov" <aamelnikov@fastmail.fm> Wed, 01 June 2016 07:33 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 13F7C12B03D; Wed, 1 Jun 2016 00:33:39 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160601073339.16171.59393.idtracker@ietfa.amsl.com>
Date: Wed, 01 Jun 2016 00:33:39 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/pHw6Y62DdkejaMI6ByuGb_Q3Iis>
Cc: mile-chairs@tools.ietf.org, mile-chairs@ietf.org, mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org
Subject: [mile] Alexey Melnikov's Discuss on draft-ietf-mile-rfc5070-bis-22: (with DISCUSS and 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, 01 Jun 2016 07:33:39 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-mile-rfc5070-bis-22: Discuss

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-rfc5070-bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I will move to yes when the following issue is discussed.

Robert Sparks' SecDir review reminded me: I am concerned by the
requirement to automatically download updates from IANA. If many devices
or software programs implement IODEF and start doing schema validation,
this can cause DDoS attack on IANA infrastructure.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In 3.29.3.1: there is still a reference to RFC 822 (should be RFC 5322)

In 4.1: it would be good to point to the W3C XML document about rules for
escaping special characters. Otherwise readers might just think that all
cases are covered in this section.