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

Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 02 June 2016 09:04 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 6F80912D668; Thu, 2 Jun 2016 02:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=loCE6Lwz; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=BWl2ofY3
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 4ljwKOncCvBv; Thu, 2 Jun 2016 02:04:51 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 888D412B029; Thu, 2 Jun 2016 02:04:51 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CFC0D20347; Thu, 2 Jun 2016 05:04:50 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Thu, 02 Jun 2016 05:04:50 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=fFhH5oZYIvqHRkfkZW4syRWjKqE=; b=loCE6L wzX0u3EDzBkk9mLVWO36jw9FTAKVCVhoegE63eLOLh+aCkiOJWqB1uJYbFXTkHB/ O2EREwdYVt50NnKRUNC0oRLYbM4lhqnxKrCMqzAjNmELRyvSI1DF7PVHQ4uk19QK YeFgLd1cYC9LFdo3d3VDZYFne1JXUxavT2WnE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=fFhH5oZYIvqHRkf kZW4syRWjKqE=; b=BWl2ofY3PUGt8Uvp0UbpRK9u7IZQyLurxAQtQU25ToXP4dZ KTQe7z8hZ5txLweWTob3o4PYtGghO2yC0mf+MwJGx2QlEUniLnAzp3I7iilzW4To r/0nI3IiaSXQZKJMNejKl9+zp4CSBLxOgt79KFm7lQbL4c5QVtib6dmGVUpQ=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 993B5A849C; Thu, 2 Jun 2016 05:04:50 -0400 (EDT)
Message-Id: <1464858290.1234564.625673017.7541014D@webmail.messagingengine.com>
X-Sasl-Enc: VMhPubpqjXBD0iO8dXx8bQF6wIpsf7mvhlPdIKWmsGi1 1464858290
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "Roman D. Danyliw" <rdd@cert.org>, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-38f217ef
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD974F85C@marathon>
References: <20160601073339.16171.59393.idtracker@ietfa.amsl.com> <359EC4B99E040048A7131E0F4E113AFCD974F85C@marathon>
Date: Thu, 02 Jun 2016 10:04:50 +0100
Archived-At: <http://mailarchive.ietf.org/arch/msg/mile/GYWOfr7bDf12oRs0FoqEykuG39Y>
Cc: mile@ietf.org, draft-ietf-mile-rfc5070-bis@ietf.org, mile-chairs@ietf.org, mile-chairs@tools.ietf.org
Subject: Re: [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
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, 02 Jun 2016 09:04:53 -0000

Hi Roman,

On Thu, Jun 2, 2016, at 06:15 AM, Roman D. Danyliw wrote:
> Hi Alexey,
> 
> Thanks for the review.  Responses to the DISCUSS and COMMENTs are inline
> ...
> 
> > -----Original Message-----
> > From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> > Sent: Wednesday, June 1, 2016 3:34 AM
> > To: The IESG <iesg@ietf.org>;
> > Cc: draft-ietf-mile-rfc5070-bis@ietf.org; Roman D. Danyliw <rdd@cert.org>;;
> > mile-chairs@tools.ietf.org; mile@ietf.org; mile-chairs@ietf.org;
> > takeshi_takahashi@nict.go.jp; mile@ietf.org
> > Subject: Alexey Melnikov's Discuss on draft-ietf-mile-rfc5070-bis-22: (with
> > DISCUSS and COMMENT)
> > 

 [snip]

> > ----------------------------------------------------------------------
> > 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.
> 
> A response to Robert's review can be found here:
> 
> https://mailarchive.ietf.org/arch/msg/mile/hSH9Ot6L_VTb9zYcJNZzO_c-7dc
> 
> Note: I posed a few questions back to the working group, so not
> everything is resolved.

Ok, I replied to that message.

> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > In 3.29.3.1: there is still a reference to RFC 822 (should be RFC 5322)
> 
> Actually, per Stephen's COMMENT on EAI
> (https://mailarchive.ietf.org/arch/msg/mile/N52_1W9aXRw6gZSEqu0Y_vFuFh0),
> this likely needs to be RFC5336. 

Yes. Maybe keep both references?

> I'll make the change and also make it a
> real reference.  It's hard coded text now.

Good idea.

> > 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.
> 
> Makes sense.  I'd actually prefer to remove the specific examples and
> just cite reference.

Works for me.