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

Alissa Cooper <alissa@cooperw.in> Wed, 23 January 2019 16:24 UTC

Return-Path: <alissa@cooperw.in>
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 28B91130E7D; Wed, 23 Jan 2019 08:24:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mile-xmpp-grid@ietf.org, mile@ietf.org, mile-chairs@tools.ietf.org, Takeshi Takahashi <takeshi_takahashi@nict.go.jp>, mile-chairs@ietf.org, takeshi_takahashi@nict.go.jp, mile@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.90.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154826066916.7513.16190033373417256166.idtracker@ietfa.amsl.com>
Date: Wed, 23 Jan 2019 08:24:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mile/O7T20sXQ6N1UD4ANr8CpZrAN4IA>
Subject: [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
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, 23 Jan 2019 16:24:29 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-mile-xmpp-grid-09: 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:


Please respond to the Gen-ART review.

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.

In the subsections of Section 8.3 I can't readily discern why some of the
requirements that relate to protections outside the protocol stack are listed
with normative keywords and some are not. It seems like none of them having
normative weight would make more sense, or perhaps there is an explanation I'm