Re: [Stox] AD evaluation: draft-ietf-stox-im-10

Peter Saint-Andre - &yet <> Mon, 02 February 2015 16:23 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 76CF11A86FA for <>; Mon, 2 Feb 2015 08:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pf2_vXr3UNMD for <>; Mon, 2 Feb 2015 08:23:14 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9C8981A86F2 for <>; Mon, 2 Feb 2015 08:23:07 -0800 (PST)
Received: by with SMTP id at20so18580056iec.3 for <>; Mon, 02 Feb 2015 08:23:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=B+H2YGoNag/+1gR8hyl+s24TdW9+D+ZYyHsmH8elwhw=; b=eRXMzmd2tE1RI+0k/EszNsMR81YGiHiXzsCLS+UN7pATS9CIO43Kt0IWJ4MOuDC35k jrNYHTdqz6GjOvjco3RiObux5GGM9SMcq8Gq/C6q1ba1Efoetk7G1zPS5QZ7bqqNOTpz ku66Scvd2GTCnROoq8MBv01w/R8D9lsFevcJ2c8B2DsT956uZtISlIvgImLfONyUB/i+ WjDHSHraiOu3FhoxB6lAmeHG/mfbp+XPqTuXlhvi9nCv+1yYJEk+aNxzgvqaWwdnZBZm u7sjAANq6S7KwDmYFvKvAz9xR/5Kfp9UDq5O/OTkstR3pHciXEUDnEVDoy69/BOjJ1JX +u9w==
X-Gm-Message-State: ALoCoQmCIj6uNuZJqMFYKygo6O9Pt8Djj1d74f+33g/sU1RHeJRGQ4vqiKjE8scPfRP7RiCYO1Rt
X-Received: by with SMTP id j88mr23135440ioi.91.1422894187027; Mon, 02 Feb 2015 08:23:07 -0800 (PST)
Received: from aither.local ([2601:1:8202:a280:3df3:7ca3:bc84:ffd3]) by with ESMTPSA id k9sm6283809ige.6.2015. (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 08:23:06 -0800 (PST)
Message-ID: <>
Date: Mon, 02 Feb 2015 09:23:04 -0700
From: Peter Saint-Andre - &yet <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Alissa Cooper <>,
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [Stox] AD evaluation: draft-ietf-stox-im-10
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 02 Feb 2015 16:23:20 -0000

Hi Alissa, thanks for the review. Comments inline.

On 1/31/15 5:09 PM, Alissa Cooper wrote:
> I have reviewed this draft in preparation for IETF LC, along with the
> -chat and -groupchat drafts. Overall the document appears in good
> shape. I have a comment I’d like to discuss before proceeding to IETF
> LC, along with an editorial nit to be addressed with any LC
> comments.
> You will note some commonality across my comments on all three
> drafts. In general, these drafts could do a better job of precisely
> specifying what is minimally required (normatively) for
> interoperability, versus what is optional or likely to differ between
> implementations. I think if at least the syntax mappings are
> normatively specified that should be sufficient, but the authors and
> WG might want to consider doing another pass at these documents to
> see if they could be more clear about which protocol exchanges the
> various gateways must support for STOX to work at all, versus which
> ones are suggested or optional.
> Comment:
> To achieve minimal interoperability, I think the syntax mappings in
> Section 4 need to be MUST-level requirements rather than SHOULD. Or,
> if there are cases envisioned in which different implementations
> might map the elements differently, those should be explained. But I
> assume there are not.

That seems reasonable.

Would you like the authors to complete this review and cleanup (with 
revised I-Ds for all three documents) before IETF Last Call?

> Nit:
> If GRUUs are generally not human-readable in use, I would suggest
> changing the ones in Section 4 to random identifiers.

Good point. Will fix.


Peter Saint-Andre