Re: [mile] Alissa Cooper's No Objection on draft-ietf-mile-xmpp-grid-09: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Thu, 24 January 2019 14:42 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 17F54127598; Thu, 24 Jan 2019 06:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=BWzUKAIx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XCo2Q9vb
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 5GUnwNqJWXKs; Thu, 24 Jan 2019 06:42:52 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEB59124BE5; Thu, 24 Jan 2019 06:42:51 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 568C6236D0; Thu, 24 Jan 2019 09:42:49 -0500 (EST)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Thu, 24 Jan 2019 09:42:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:date:references:subject:in-reply-to; s=fm2; bh=Hvy Ez3yScoOsGzrnMa3DZHb3EyIF3nTGy1Rzn3dP4GI=; b=BWzUKAIxmTqt6ivjwEx YtgvHY+NPt2q2Zy/+qJIIQM2yOkACM4J9t6/yEr9arZi3o4RO5yqvHAVoieArCu5 WyNsnGuwtixzSAnd0awdzi1TP5CIpNNKNBab4P72ql+7b93pLmayj031U/dGSna2 GSwI0Cawl23q9Pxbdl+VKE3Ms8VH621U5INXfCGuXwVk0A1zPoXyLB4ttMK8R3c9 Ul06mgTUuyKPnPh1SDRpw+DciPeGPblhcH6u1CCYu7YmgrPA3fjS1L3H27IG6ztT hOa+Kg2P2lpHSgqi25g/7FHax/5NuK3EbChSu5Q/2kLJK9CSu0Loy///ES+IHpnj fsA==
DKIM-Signature: v=1; a=rsa-sha256; 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-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=HvyEz3yScoOsGzrnMa3DZHb3EyIF3nTGy1Rzn3dP4 GI=; b=XCo2Q9vbXbXB70XGTNBWTimrtbKSxyttxP4w2hXPjkMcL4v1gPj8J8TPR AhDSUqd8p15OGauWjDu11o/9+dmUoLk880B5vUMWnccoFamDiGho5lUSsWOsLiEO rQ5VTkG9yT9x1Fn6UxjGwOmj4zMRfhbDEK+IUMgBnMXO999LOnGOK8lK5SWzm2H0 /+vMiPf1Zt5R+CJPUMMtAQwabviJxvVVLxO1SCeyUMYvF0zOswbV0g7uy/QxmHBU nDu5+Yb5ZadF8mWb6tjmIZDiGBx8ueWoH0moV8wm2xrdWfamyl7PBA8b7zBYY+b0 IbftPZyBpw8lirQQMQMbayenO5z6A==
X-ME-Sender: <xms:585JXKtGHF_A2xy5nG2Jgw1xM5jcGk0E3Q7Z-ZJ9hcjZ4mXcEc2n3w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledriedvgdeijecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepkffhvfgggfgtof fffhfujgesthejredtredtjeenucfhrhhomheptehlvgigvgihucfovghlnhhikhhovhcu oegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmheqnecurfgrrhgrmhepmhgrih hlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmhenucevlhhushht vghrufhiiigvpedt
X-ME-Proxy: <xmx:585JXKXC_sN9UcSRxgMIAkSticcxDqj0KHR-jDXrvYwXhh_8OT1uGQ> <xmx:585JXNneoz8L6OjCsqKOKKAhWf0ZwjPacItn54B06xebrDH6Fdb6sA> <xmx:585JXDbm8l7LDSHZ5E2SehkzTi6ymUip9lfNO6hk2-YJ-r5vSUETLg> <xmx:6c5JXAneIS3sQLYGnjw6PLuCwuB9CASn3YK30rylh7gssxySuXrkWQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9033D9E123; Thu, 24 Jan 2019 09:42:47 -0500 (EST)
Message-Id: <1548340967.409238.1642607568.6FAA1ADF@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Cc: mile@ietf.org, mile-chairs@tools.ietf.org, takeshi_takahashi@nict.go.jp, draft-ietf-mile-xmpp-grid@ietf.org, mile-chairs@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-36e4bfd3
Date: Thu, 24 Jan 2019 14:42:47 +0000
References: <154826066916.7513.16190033373417256166.idtracker@ietfa.amsl.com>
In-Reply-To: <154826066916.7513.16190033373417256166.idtracker@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/_E-x_VzkNh6sDVJzuEcPNdsjk-k>
Subject: Re: [mile] Alissa Cooper's No Objection on draft-ietf-mile-xmpp-grid-09: (with COMMENT)
X-BeenThere: mile@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Jan 2019 14:42:53 -0000

Hi Alissa,

Thank you for your comments.  Quick comments on a part of your review.

On Wed, Jan 23, 2019, at 4:24 PM, Alissa Cooper wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Please respond to the Gen-ART review.

Yes, I will chase that.

> I'm not quite seeing what part of this is a standards-track specification. The
> workflow in Section 4 is described as "typical" but not normative and the
> exchanges listed in sections 5 and 6 are listed as examples. For a
> standards-track specification I would have expected something more like
> "Implementations of XMPP-Grid adhere to the following workflow ..." and for
> service discovery and pub-sub to be described as *the* way to do those things
> in XMPP-Grid, not just illustrated by examples. Otherwise this seems like it
> could be an informational document.

I need to discuss this with the WG, but I think I agree that the document needs an editorial pass to make sure that it is either purely Informative or that it clearly states extra requirements as suitable for a Proposed Standard.

Thank you,
Alexey