[Stox] Alissa Cooper's No Objection on draft-ietf-stox-7248bis-13: (with COMMENT)

"Alissa Cooper" <alissa@cooperw.in> Tue, 01 November 2016 13:48 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: stox@ietf.org
Delivered-To: stox@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8631294EA; Tue, 1 Nov 2016 06:48:39 -0700 (PDT)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147800811917.23892.1662525206263233255.idtracker@ietfa.amsl.com>
Date: Tue, 01 Nov 2016 06:48:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/gHohzZ9n1dsdywsUgFg8fhzGNfc>
Cc: draft-ietf-stox-7248bis@ietf.org, stox@ietf.org, stox-chairs@ietf.org, saul@ag-projects.com
Subject: [Stox] Alissa Cooper's No Objection on draft-ietf-stox-7248bis-13: (with COMMENT)
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.17
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2016 13:48:39 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-stox-7248bis-13: 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:
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/



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

Below is a small suggested edit for text in Section 9.2. I think the
normative "MUST honor data about ..." construction is vague.

OLD
Therefore, a gateway MUST honor data about
   the intended recipient of a presence notification (as represented by
   the 'to' address for XMPP and by the Request-URI for SIP) and it MUST
   NOT route or deliver a presence notification to any other entities,
   because it does not possess information about authorization to
   receive presence notifications for such entities - that information
   resides at the user's home service, not at the receiving gateway).

NEW
Therefore, a gateway MUST
   NOT route or deliver a presence notification to any entity other than
the intended recipient (as represented by
   the 'to' address for XMPP and by the Request-URI for SIP),
   because it does not possess information about authorization to
   receive presence notifications for such entities - that information
   resides at the user's home service, not at the receiving gateway).