Re: [Stox] AD Evaluation of draft-ietf-stox-7248bis-05

Peter Saint-Andre <stpeter@stpeter.im> Wed, 22 June 2016 02:44 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B27E412D89F; Tue, 21 Jun 2016 19:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 iwpWyPm3oi-S; Tue, 21 Jun 2016 19:44:23 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 50FDF12D896; Tue, 21 Jun 2016 19:44:23 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C7524E8288; Tue, 21 Jun 2016 20:57:19 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>
References: <CC605F0B-9B8E-4FE0-9DEC-79A3E1162ED5@nostrum.com> <56036577.3000204@andyet.net> <1794408B-8BE1-4F24-8A26-F40B1A0804EF@nostrum.com> <5609F9D5.2080306@andyet.net> <BD08A7FA-9722-4444-B5B7-3640D4AC2D56@nostrum.com> <56EF2815.8050407@stpeter.im> <57221AA1.5000609@stpeter.im> <B6D0869C-3E60-425E-827F-66A6BD8C6DA8@nostrum.com> <29063029-3EC9-476A-A8CA-2EF7B6BA9984@stpeter.im> <57225AAF.8060007@stpeter.im> <FBCF24A9-9E39-4A6D-970D-49C6E0EFE4F9@nostrum.com> <57460522.4030600@stpeter.im> <4BE36129-280C-475C-9C5A-6E9D0D770D90@nostrum.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <ee5c285c-5176-4646-c333-990d52892d0f@stpeter.im>
Date: Tue, 21 Jun 2016 20:44:21 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <4BE36129-280C-475C-9C5A-6E9D0D770D90@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/i1YR0QZXnBUQudUFsQcV9MhrUi4>
Cc: stox@ietf.org, draft-ietf-stox-7248bis.all@ietf.org
Subject: Re: [Stox] AD Evaluation of draft-ietf-stox-7248bis-05
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Wed, 22 Jun 2016 02:44:25 -0000

Hi Ben, thanks for your comments. My apologies for the delayed reply.

On 6/9/16 4:37 PM, Ben Campbell wrote:
> Hi Peter,
>
>
> I have a couple of questions about the implications of the new "presence
> authorization" concept, and a couple of editorial nits. Otherwise, I
> think this is ready for IETF last call. It might make sense to go ahead
> with the last call, and address these with any last call comments--but
> I'd like to have an initial round of conversation about the presence
> authorization first.
>
> - in 5.2.3, whose "authorization" is canceled?

The use cases in §5.2 originate on the XMPP side and the use cases in 
§5.3 originate on the SIP side, so §5.2.3 describes what happens when 
the XMPP user no longer wishes to receive presence notifications from 
the SIP contact.

> If the SIP contact has a
> reciprocal subscription back to the xmpp contact’s presence, is that
> impacted by this unsubscribe action?

It shouldn't be, because we're not assuming that authorization to 
receive presence notifications needs to be bidirectional. So this flow 
results in the XMPP user (here, Juliet) no longer receiving presence 
notifications from the SIP contact (here, Romeo); however, Romeo can 
still happily receive presence notifications from Juliet.

> Or is the SIP user expected to
> remove the authorization for the xmpp user to see her presence info?

Romeo would also need to inform Juliet that he no longer wishes to 
receive presence notifications from her, i.e., he would need to complete 
the flow in §5.3.3.

I can see that the phrasing in §5.2.3 and §5.3.3 is confusing, i.e.:

   5.2.3

     cancelling an XMPP user's presence authorization to a SIP contact

   5.3.3

     cancel the presence authorization

That wording doesn't make the directionality clear. I'll rephrase these 
sentences to clarify matters.

> - in 5.3.1, I _think_ the flow creates both an authorization and a
> notification dialog.

To prevent confusion, we're now using the term "notification dialog" for 
SIP->XMPP and "presence authorization" for XMPP->SIP. When you say 
"authorization" here, are you referring to a presence authorization from 
the XMPP user to the SIP user? If so, how would the notification dialog 
from the SIP user to the XMPP trigger that? If not, then let's make sure 
we're on the same page about what's happening here.

(Yes, I know, presence state machines are horribly complicated!)

> If the SIP user unsubscribes, and resubscribes
> (that is, tears down the notification dialog and creates a new one),

That is, completes the flow in §5.3.1, then completes the flow in 
§5.3.3, then initiates the flow in §5.3.1 again - correct?

> is
> there any difference in the flow due to the fact the XMPP server has
> authorization state for the SIP user? (Would F29 and F30 still happen?)

You are correct - the XMPP server would still consider the SIP user to 
be authorized, and so it would not prompt the XMPP client for approval 
of an authorization request. See §3.1.3, point #2, of RFC 6121.

> Nits:
>
> - 1, 5th paragraph: s/specfic/specific/
>
> - 5.2.2, first paragraph, last sentence: I suspect "whenever" should be
> "... sufficiently in advance of when..."

Good catch.

After we settle on a common understanding of the foregoing points, I'll 
submit -09 so that we have clean text ready for IETF Last Call.

Thanks again,

Peter