
From nobody Fri Sep  2 15:23:57 2016
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 557BF12B005 for <stox@ietfa.amsl.com>; Fri,  2 Sep 2016 15:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, 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 3_Nb5U1E4sE5 for <stox@ietfa.amsl.com>; Fri,  2 Sep 2016 15:23:54 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D1896127735 for <stox@ietf.org>; Fri,  2 Sep 2016 15:23:54 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 624A940FC8; Fri,  2 Sep 2016 16:23:57 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im>
Date: Fri, 2 Sep 2016 16:23:53 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/dV4zaLfZPZ09fi0x03zunnz7Gh0>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Fri, 02 Sep 2016 22:23:56 -0000

On 8/29/16 9:43 PM, Peter Saint-Andre wrote:
> On 8/29/16 4:56 PM, Ben Campbell wrote:
>> Hi Peter,
>>
>> I'm going to try to be more responsive on this, and break the apology
>> loop :-)
>
> Likewise!
>
>> I agree we are zeroing in on things here. I think, with this version, I
>> can better clarify my remaining concern. (I think it's the only thing
>> left.)
>>
>> 5.2.3 talks about canceling a presence authorization. But from Romeo's
>> perspective, it does do that; it only cancels the notification session.
>> SIP has no way for Juliet to explicitly say "I want my permission to see
>> Romeo's presence info to go away". If Juliet never wants to be notified
>> again, she simply doesn't subscribe again. Maybe Romeo's system has some
>> policy that ages out such authorizations over time, but that's not
>> really relevant to this draft. (It's also possible for Romeo to
>> unilaterally cancel that authorization, but that's probably more detail
>> than is needed here.) In simpler terms, Romeo's presence server asks him
>> if he wants to let Juliet subscribe the first time she tries. For future
>> subscriptions, it won't ask. If Romeo later decides he prefers less
>> star-crossed relationships, he can withdraw that permission. Other than
>> than the initial subscription request, Juliet has no say in the matter.
>>
>> This is also true for _requesting_ authorization. For example, the only
>> thing that makes 5.2.1 into a request for authorization (on the SIP
>> side) is the fact that Juliet is subscribing for the first time. (I'm
>> not saying 5.2.1 needs to change; I just mention this for background).
>>
>> Likewise in 5.3.3, Romeo is not asking to be deauthorized. He's just
>> asking to end the notification session. Now that may not matter, he just
>> gets re-authorized next time hie sends a SUBSCRIBE request. But he might
>> be surprised to find that Juliet thought he had requested to be
>> deauthorized. (Not to mention, that Juliet might feel, well,
>> "unfriended" :-)  )
>>
>> This all goes counter to the statement in the 2nd to last paragraph of
>> 5.1 that SIP presence authorizations are managed with SUBSCRIBE
>> requests. The real situation is that the watcher (Juliet) doesn't manage
>> these authorizations at all--they are unilaterally managed by the
>> presentity (Romeo). A SUBSCRIBE request from Juliet may cause Romeo to
>> be notified that he needs to make an authorization decision if he has
>> not previously given permission.
>
> Your description really clarified things for me, so thanks!

Looking at the I-D more closely, I think that the protocol flow diagram 
in §5.2.3 is fine, but that some clarifying text would help. I propose 
the following change to the first paragraph of that section.

OLD

    The following diagram illustrates the protocol flow by which an XMPP
    user cancels her outbound presence authorization to a SIP contact
    (i.e., indicates that she no longer wishes to be authorized to see
    the SIP contact's presence), as further explained in the text and
    examples after the diagram.

NEW

    The following diagram illustrates the protocol flow by which an XMPP
    user cancels her outbound presence authorization to a SIP contact
    (i.e., indicates that she no longer wishes to be authorized to see
    the SIP contact's presence).  As can be seen, because SIMPLE does not
    have a construct that enables a contact to cancel her presence
    authorization, this flow instead results in cancellation of the
    contact's notification dialog (with the implication on the XMPP side
    that the contact will not request a subsequent notification dialog).
    Additional details are explained in the text and examples after the
    diagram.

Similarly in §5.3.3...

OLD

    At any time, the SIP user can cancel his outbound presence
    authorization to the XMPP contact (i.e., indicate that he no longer
    wishes to be authorized to receive presence notifications from the
    XMPP contact) by sending a SUBSCRIBE message whose Expires header is
    set to a value of zero ("0"):

NEW

    SIP does not directly have a construct for cancelling an outbound
    presence authorization.  Instead, the SIP user would terminate his
    outbound notification dialog by sending a SUBSCRIBE message whose
    Expires header is set to a value of zero ("0"), and then never renew
    it:

>> So, how to fix this? I'm not sure I have the answer. But one approach
>> might be to extend 5.1 to be more clear about the difference in
>> authorization models, then have sections 5.2.x and 5.3.x talk more about
>> notification sessions than authorization, but mention authorization
>> state changes in the commentary about the message detail as needed.
>
> Yes, that seems sensible. I will work on an updated I-D along those
> lines very soon.

Given the changes proposed above, do you think we also need to modify 
§5.1? We could add a sentence or clause there, too, but I'm not sure 
it's really necessary.

Thanks!

Peter



From nobody Fri Sep  2 19:19:39 2016
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 B73CD12D5C9 for <stox@ietfa.amsl.com>; Fri,  2 Sep 2016 19:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, 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 v1Zx6-t2PVqX for <stox@ietfa.amsl.com>; Fri,  2 Sep 2016 19:19:37 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 8D95312D5C4 for <stox@ietf.org>; Fri,  2 Sep 2016 19:19:37 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D3BFC4159F; Fri,  2 Sep 2016 20:19:39 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im>
Date: Fri, 2 Sep 2016 20:19:35 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/AZyocGr_K2RKdDWCtCzmOfCfYz4>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Sat, 03 Sep 2016 02:19:38 -0000

On 9/2/16 4:23 PM, Peter Saint-Andre wrote:
> On 8/29/16 9:43 PM, Peter Saint-Andre wrote:
>> On 8/29/16 4:56 PM, Ben Campbell wrote:
>>> Hi Peter,
>>>
>>> I'm going to try to be more responsive on this, and break the apology
>>> loop :-)
>>
>> Likewise!
>>
>>> I agree we are zeroing in on things here. I think, with this version, I
>>> can better clarify my remaining concern. (I think it's the only thing
>>> left.)
>>>
>>> 5.2.3 talks about canceling a presence authorization. But from Romeo's
>>> perspective, it does do that; it only cancels the notification session.
>>> SIP has no way for Juliet to explicitly say "I want my permission to see
>>> Romeo's presence info to go away". If Juliet never wants to be notified
>>> again, she simply doesn't subscribe again. Maybe Romeo's system has some
>>> policy that ages out such authorizations over time, but that's not
>>> really relevant to this draft. (It's also possible for Romeo to
>>> unilaterally cancel that authorization, but that's probably more detail
>>> than is needed here.) In simpler terms, Romeo's presence server asks him
>>> if he wants to let Juliet subscribe the first time she tries. For future
>>> subscriptions, it won't ask. If Romeo later decides he prefers less
>>> star-crossed relationships, he can withdraw that permission. Other than
>>> than the initial subscription request, Juliet has no say in the matter.
>>>
>>> This is also true for _requesting_ authorization. For example, the only
>>> thing that makes 5.2.1 into a request for authorization (on the SIP
>>> side) is the fact that Juliet is subscribing for the first time. (I'm
>>> not saying 5.2.1 needs to change; I just mention this for background).
>>>
>>> Likewise in 5.3.3, Romeo is not asking to be deauthorized. He's just
>>> asking to end the notification session. Now that may not matter, he just
>>> gets re-authorized next time hie sends a SUBSCRIBE request. But he might
>>> be surprised to find that Juliet thought he had requested to be
>>> deauthorized. (Not to mention, that Juliet might feel, well,
>>> "unfriended" :-)  )
>>>
>>> This all goes counter to the statement in the 2nd to last paragraph of
>>> 5.1 that SIP presence authorizations are managed with SUBSCRIBE
>>> requests. The real situation is that the watcher (Juliet) doesn't manage
>>> these authorizations at all--they are unilaterally managed by the
>>> presentity (Romeo). A SUBSCRIBE request from Juliet may cause Romeo to
>>> be notified that he needs to make an authorization decision if he has
>>> not previously given permission.
>>
>> Your description really clarified things for me, so thanks!
>
> Looking at the I-D more closely, I think that the protocol flow diagram
> in §5.2.3 is fine, but that some clarifying text would help. I propose
> the following change to the first paragraph of that section.
>
> OLD
>
>    The following diagram illustrates the protocol flow by which an XMPP
>    user cancels her outbound presence authorization to a SIP contact
>    (i.e., indicates that she no longer wishes to be authorized to see
>    the SIP contact's presence), as further explained in the text and
>    examples after the diagram.
>
> NEW
>
>    The following diagram illustrates the protocol flow by which an XMPP
>    user cancels her outbound presence authorization to a SIP contact
>    (i.e., indicates that she no longer wishes to be authorized to see
>    the SIP contact's presence).  As can be seen, because SIMPLE does not
>    have a construct that enables a contact to cancel her presence
>    authorization, this flow instead results in cancellation of the
>    contact's notification dialog (with the implication on the XMPP side
>    that the contact will not request a subsequent notification dialog).
>    Additional details are explained in the text and examples after the
>    diagram.
>
> Similarly in §5.3.3...
>
> OLD
>
>    At any time, the SIP user can cancel his outbound presence
>    authorization to the XMPP contact (i.e., indicate that he no longer
>    wishes to be authorized to receive presence notifications from the
>    XMPP contact) by sending a SUBSCRIBE message whose Expires header is
>    set to a value of zero ("0"):
>
> NEW
>
>    SIP does not directly have a construct for cancelling an outbound
>    presence authorization.  Instead, the SIP user would terminate his
>    outbound notification dialog by sending a SUBSCRIBE message whose
>    Expires header is set to a value of zero ("0"), and then never renew
>    it:
>
>>> So, how to fix this? I'm not sure I have the answer. But one approach
>>> might be to extend 5.1 to be more clear about the difference in
>>> authorization models, then have sections 5.2.x and 5.3.x talk more about
>>> notification sessions than authorization, but mention authorization
>>> state changes in the commentary about the message detail as needed.
>>
>> Yes, that seems sensible. I will work on an updated I-D along those
>> lines very soon.
>
> Given the changes proposed above, do you think we also need to modify
> §5.1? We could add a sentence or clause there, too, but I'm not sure
> it's really necessary.

Actually I think the following changes would help to clarify matters.

OLD

    As described in [RFC3856], SIP notification dialogs and presence
    authorizations are managed through the use of SIP SUBSCRIBE events
    sent from a SIP User Agent or Presence Server to an intended
    recipient who is most generally referenced by a Presence URI of the
    form <pres:user@domain> but who might be referenced by a SIP or SIPS
    (Session Initiation Protocol Secure) URI of the form
    <sip:user@domain> or <sips:user@domain>.  In practice, 'pres' URIs
    are rarely used, which is why the examples in this document use 'sip'
    URIs.

NEW

    As described in [RFC3856], SIP presence authorizations are
    effectively implicit: when a SIP user receives an initial SIP
    SUBSCRIBE event from a contact, the recipient's SIP User Agent will
    prompt the user to approve or deny the request.  This decision is
    recorded in the User Agent or in a Presence Server, so that in the
    future any notification dialogs from the contact are automatically
    approved.  (Note that addresses for SIP users and contacts are most
    generally referenced by a Presence URI of the form <pres:user@domain>
    but might be referenced by a SIP or SIPS (Session Initiation Protocol
    Secure) URI of the form <sip:user@domain> or <sips:user@domain>;
    because in practice 'pres' URIs are rarely used, the examples in this
    document use 'sip' URIs.)

I'm going to submit a revised I-D with these changes and we'll take it 
from there. :-)

Peter



From nobody Fri Sep  2 19:22:20 2016
Return-Path: <internet-drafts@ietf.org>
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 508EE12D189; Fri,  2 Sep 2016 19:22:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147286933932.24877.18226352282736190521.idtracker@ietfa.amsl.com>
Date: Fri, 02 Sep 2016 19:22:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/TkdxZtqNKcabMfaJoytmQMb32Jw>
Cc: stox@ietf.org
Subject: [Stox] I-D Action: draft-ietf-stox-7248bis-10.txt
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: Sat, 03 Sep 2016 02:22:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP-TO-XMPP of the IETF.

        Title           : Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
        Author          : Peter Saint-Andre
	Filename        : draft-ietf-stox-7248bis-10.txt
	Pages           : 31
	Date            : 2016-09-02

Abstract:
   This document defines a bidirectional protocol mapping for the
   exchange of presence information between the Session Initiation
   Protocol (SIP) and the Extensible Messaging and Presence Protocol
   (XMPP).  This document obsoletes RFC 7248.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-stox-7248bis-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-stox-7248bis-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep  7 13:39:50 2016
Return-Path: <ben@nostrum.com>
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 83A8E12B029 for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 549FD7e05eP9 for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:39:47 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBD2712B213 for <stox@ietf.org>; Wed,  7 Sep 2016 13:39:47 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u87KdiuE000224 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 7 Sep 2016 15:39:46 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
Date: Wed, 07 Sep 2016 15:39:44 -0500
Message-ID: <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com>
In-Reply-To: <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/nMsrCDBxHR6qUaDsU9uwHGQ4ApU>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 07 Sep 2016 20:39:49 -0000

Hi Peter,

I think version 10 is very close to ready. I have two minor comments; 
for the most part these don't change the interaction. I've actually 
suggested text this time :-)

-4, list item 1:

OLD:
   Instead of forwarding a SUBSCRIBE message to the SIP user, the 
Presence Server
   would act on the basis of a policy set by the SIP User Agent using 
the â€™
   presence.winfoâ€™ event package, for which the SIP user would receive 
events.
NEW:
   Instead of forwarding a SUBSCRIBE message to the SIP user, the 
Presence Server
   would inform the user of subscription activity using the 
â€™presence.winfoâ€™
   event package.

-5.1, paragraph after bullet list:
OLD:
    As described in [RFC3856], SIP presence authorizations are
    effectively implicit: when a SIP user receives an initial SIP
    SUBSCRIBE event from a contact, the recipientâ€™s SIP User Agent 
will
    prompt the user to approve or deny the request.
NEW:
    As described in [RFC3856], in SIP the subscriber does not explicitly
    request the creation or removal of presence authorizations. Rather,
    the authorizations are triggered by subscription activity. When a
    SIP user receives an initial SIP SUBSCRIBE event from a contact,
    the recipientâ€™s SIP User Agent or presence server notifies the
    user to make an authorization policy decision.


Thanks!

Ben.



On 2 Sep 2016, at 21:19, Peter Saint-Andre wrote:

> On 9/2/16 4:23 PM, Peter Saint-Andre wrote:
>> On 8/29/16 9:43 PM, Peter Saint-Andre wrote:
>>> On 8/29/16 4:56 PM, Ben Campbell wrote:
>>>> Hi Peter,
>>>>
>>>> I'm going to try to be more responsive on this, and break the 
>>>> apology
>>>> loop :-)
>>>
>>> Likewise!
>>>
>>>> I agree we are zeroing in on things here. I think, with this 
>>>> version, I
>>>> can better clarify my remaining concern. (I think it's the only 
>>>> thing
>>>> left.)
>>>>
>>>> 5.2.3 talks about canceling a presence authorization. But from 
>>>> Romeo's
>>>> perspective, it does do that; it only cancels the notification 
>>>> session.
>>>> SIP has no way for Juliet to explicitly say "I want my permission 
>>>> to see
>>>> Romeo's presence info to go away". If Juliet never wants to be 
>>>> notified
>>>> again, she simply doesn't subscribe again. Maybe Romeo's system has 
>>>> some
>>>> policy that ages out such authorizations over time, but that's not
>>>> really relevant to this draft. (It's also possible for Romeo to
>>>> unilaterally cancel that authorization, but that's probably more 
>>>> detail
>>>> than is needed here.) In simpler terms, Romeo's presence server 
>>>> asks him
>>>> if he wants to let Juliet subscribe the first time she tries. For 
>>>> future
>>>> subscriptions, it won't ask. If Romeo later decides he prefers less
>>>> star-crossed relationships, he can withdraw that permission. Other 
>>>> than
>>>> than the initial subscription request, Juliet has no say in the 
>>>> matter.
>>>>
>>>> This is also true for _requesting_ authorization. For example, the 
>>>> only
>>>> thing that makes 5.2.1 into a request for authorization (on the SIP
>>>> side) is the fact that Juliet is subscribing for the first time. 
>>>> (I'm
>>>> not saying 5.2.1 needs to change; I just mention this for 
>>>> background).
>>>>
>>>> Likewise in 5.3.3, Romeo is not asking to be deauthorized. He's 
>>>> just
>>>> asking to end the notification session. Now that may not matter, he 
>>>> just
>>>> gets re-authorized next time hie sends a SUBSCRIBE request. But he 
>>>> might
>>>> be surprised to find that Juliet thought he had requested to be
>>>> deauthorized. (Not to mention, that Juliet might feel, well,
>>>> "unfriended" :-)  )
>>>>
>>>> This all goes counter to the statement in the 2nd to last paragraph 
>>>> of
>>>> 5.1 that SIP presence authorizations are managed with SUBSCRIBE
>>>> requests. The real situation is that the watcher (Juliet) doesn't 
>>>> manage
>>>> these authorizations at all--they are unilaterally managed by the
>>>> presentity (Romeo). A SUBSCRIBE request from Juliet may cause Romeo 
>>>> to
>>>> be notified that he needs to make an authorization decision if he 
>>>> has
>>>> not previously given permission.
>>>
>>> Your description really clarified things for me, so thanks!
>>
>> Looking at the I-D more closely, I think that the protocol flow 
>> diagram
>> in Â§5.2.3 is fine, but that some clarifying text would help. I 
>> propose
>> the following change to the first paragraph of that section.
>>
>> OLD
>>
>>    The following diagram illustrates the protocol flow by which an 
>> XMPP
>>    user cancels her outbound presence authorization to a SIP contact
>>    (i.e., indicates that she no longer wishes to be authorized to see
>>    the SIP contact's presence), as further explained in the text and
>>    examples after the diagram.
>>
>> NEW
>>
>>    The following diagram illustrates the protocol flow by which an 
>> XMPP
>>    user cancels her outbound presence authorization to a SIP contact
>>    (i.e., indicates that she no longer wishes to be authorized to see
>>    the SIP contact's presence).  As can be seen, because SIMPLE does 
>> not
>>    have a construct that enables a contact to cancel her presence
>>    authorization, this flow instead results in cancellation of the
>>    contact's notification dialog (with the implication on the XMPP 
>> side
>>    that the contact will not request a subsequent notification 
>> dialog).
>>    Additional details are explained in the text and examples after 
>> the
>>    diagram.
>>
>> Similarly in Â§5.3.3...
>>
>> OLD
>>
>>    At any time, the SIP user can cancel his outbound presence
>>    authorization to the XMPP contact (i.e., indicate that he no 
>> longer
>>    wishes to be authorized to receive presence notifications from the
>>    XMPP contact) by sending a SUBSCRIBE message whose Expires header 
>> is
>>    set to a value of zero ("0"):
>>
>> NEW
>>
>>    SIP does not directly have a construct for cancelling an outbound
>>    presence authorization.  Instead, the SIP user would terminate his
>>    outbound notification dialog by sending a SUBSCRIBE message whose
>>    Expires header is set to a value of zero ("0"), and then never 
>> renew
>>    it:
>>
>>>> So, how to fix this? I'm not sure I have the answer. But one 
>>>> approach
>>>> might be to extend 5.1 to be more clear about the difference in
>>>> authorization models, then have sections 5.2.x and 5.3.x talk more 
>>>> about
>>>> notification sessions than authorization, but mention authorization
>>>> state changes in the commentary about the message detail as needed.
>>>
>>> Yes, that seems sensible. I will work on an updated I-D along those
>>> lines very soon.
>>
>> Given the changes proposed above, do you think we also need to modify
>> Â§5.1? We could add a sentence or clause there, too, but I'm not sure
>> it's really necessary.
>
> Actually I think the following changes would help to clarify matters.
>
> OLD
>
>    As described in [RFC3856], SIP notification dialogs and presence
>    authorizations are managed through the use of SIP SUBSCRIBE events
>    sent from a SIP User Agent or Presence Server to an intended
>    recipient who is most generally referenced by a Presence URI of the
>    form <pres:user@domain> but who might be referenced by a SIP or 
> SIPS
>    (Session Initiation Protocol Secure) URI of the form
>    <sip:user@domain> or <sips:user@domain>.  In practice, 'pres' URIs
>    are rarely used, which is why the examples in this document use 
> 'sip'
>    URIs.
>
> NEW
>
>    As described in [RFC3856], SIP presence authorizations are
>    effectively implicit: when a SIP user receives an initial SIP
>    SUBSCRIBE event from a contact, the recipient's SIP User Agent will
>    prompt the user to approve or deny the request.  This decision is
>    recorded in the User Agent or in a Presence Server, so that in the
>    future any notification dialogs from the contact are automatically
>    approved.  (Note that addresses for SIP users and contacts are most
>    generally referenced by a Presence URI of the form 
> <pres:user@domain>
>    but might be referenced by a SIP or SIPS (Session Initiation 
> Protocol
>    Secure) URI of the form <sip:user@domain> or <sips:user@domain>;
>    because in practice 'pres' URIs are rarely used, the examples in 
> this
>    document use 'sip' URIs.)
>
> I'm going to submit a revised I-D with these changes and we'll take it 
> from there. :-)
>
> Peter
>
> _______________________________________________
> stox mailing list
> stox@ietf.org
> https://www.ietf.org/mailman/listinfo/stox


From nobody Wed Sep  7 13:45:14 2016
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 48C1F12B2EC for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, 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 vilsmHU6cr5z for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:45:12 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 40DA712B213 for <stox@ietf.org>; Wed,  7 Sep 2016 13:45:12 -0700 (PDT)
Received: from aither.local (unknown [98.245.40.52]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 303E2416BD; Wed,  7 Sep 2016 14:45:35 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im>
Date: Wed, 7 Sep 2016 14:45:11 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/F57MMqRyVl-vh2T1VwQ7RGD6gu0>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 07 Sep 2016 20:45:13 -0000

On 9/7/16 2:39 PM, Ben Campbell wrote:
> Hi Peter,
>
> I think version 10 is very close to ready. I have two minor comments;
> for the most part these don't change the interaction. I've actually
> suggested text this time :-)
>
> -4, list item 1:
>
> OLD:
>   Instead of forwarding a SUBSCRIBE message to the SIP user, the
> Presence Server
>   would act on the basis of a policy set by the SIP User Agent using the â€™
>   presence.winfoâ€™ event package, for which the SIP user would receive
> events.
> NEW:
>   Instead of forwarding a SUBSCRIBE message to the SIP user, the
> Presence Server
>   would inform the user of subscription activity using the â€™presence.winfoâ€™
>   event package.
>
> -5.1, paragraph after bullet list:
> OLD:
>    As described in [RFC3856], SIP presence authorizations are
>    effectively implicit: when a SIP user receives an initial SIP
>    SUBSCRIBE event from a contact, the recipientâ€™s SIP User Agent will
>    prompt the user to approve or deny the request.
> NEW:
>    As described in [RFC3856], in SIP the subscriber does not explicitly
>    request the creation or removal of presence authorizations. Rather,
>    the authorizations are triggered by subscription activity. When a
>    SIP user receives an initial SIP SUBSCRIBE event from a contact,
>    the recipientâ€™s SIP User Agent or presence server notifies the
>    user to make an authorization policy decision.

Definite improvements. Would you like me to submit a revised I-D? Easy 
enough. :-)

Peter


From nobody Wed Sep  7 13:47:57 2016
Return-Path: <ben@nostrum.com>
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 5BAA112B0A0 for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 RMXe-FU8M0Hi for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:47:55 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ACE712B08F for <stox@ietf.org>; Wed,  7 Sep 2016 13:47:55 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u87KlsMA001097 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 7 Sep 2016 15:47:55 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
Date: Wed, 07 Sep 2016 15:47:53 -0500
Message-ID: <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com>
In-Reply-To: <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/wNX8iW-HmaLIyN4Ujjb_mYQ1gJ8>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 07 Sep 2016 20:47:56 -0000

On 7 Sep 2016, at 15:45, Peter Saint-Andre wrote:

> Definite improvements. Would you like me to submit a revised I-D? Easy 
> enough. :-)

If you agree to the changes, please do. Am I correct to assume that 
there are no more outstanding issues? If so, I think we can take that 
version to IETF last call.

Thanks!

Ben.


From nobody Wed Sep  7 13:50:37 2016
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 5EDD012B118 for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, 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 ahr85dbXfCwT for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 13:50:35 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0924E12B0A0 for <stox@ietf.org>; Wed,  7 Sep 2016 13:50:35 -0700 (PDT)
Received: from aither.local (unknown [98.245.40.52]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2FA7A416BC; Wed,  7 Sep 2016 14:50:58 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im>
Date: Wed, 7 Sep 2016 14:50:33 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/I19jHfqQsluy87b53WzmoGz1s6g>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 07 Sep 2016 20:50:36 -0000

On 9/7/16 2:47 PM, Ben Campbell wrote:
> On 7 Sep 2016, at 15:45, Peter Saint-Andre wrote:
>
>> Definite improvements. Would you like me to submit a revised I-D? Easy
>> enough. :-)
>
> If you agree to the changes, please do.

Submitting now.

> Am I correct to assume that
> there are no more outstanding issues?

That's how I see it.

> If so, I think we can take that
> version to IETF last call.

Great! The document shepherd might need to update his writeup.

Peter



From nobody Wed Sep  7 13:53:44 2016
Return-Path: <internet-drafts@ietf.org>
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 5312812B283; Wed,  7 Sep 2016 13:53:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147328162333.22402.10228564819339790378.idtracker@ietfa.amsl.com>
Date: Wed, 07 Sep 2016 13:53:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/g-wSXH8ydU2gBL4kaXk7ykDBozw>
Cc: stox@ietf.org
Subject: [Stox] I-D Action: draft-ietf-stox-7248bis-11.txt
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: Wed, 07 Sep 2016 20:53:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP-TO-XMPP of the IETF.

        Title           : Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
        Author          : Peter Saint-Andre
	Filename        : draft-ietf-stox-7248bis-11.txt
	Pages           : 31
	Date            : 2016-09-07

Abstract:
   This document defines a bidirectional protocol mapping for the
   exchange of presence information between the Session Initiation
   Protocol (SIP) and the Extensible Messaging and Presence Protocol
   (XMPP).  This document obsoletes RFC 7248.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-stox-7248bis-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-stox-7248bis-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Sep  7 14:00:12 2016
Return-Path: <ben@nostrum.com>
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 5A30712B3E9 for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 14:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 ZVdUuH-0d6cZ for <stox@ietfa.amsl.com>; Wed,  7 Sep 2016 14:00:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23A3C12B283 for <stox@ietf.org>; Wed,  7 Sep 2016 14:00:10 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u87L05DS002320 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 7 Sep 2016 16:00:06 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>, "=?utf-8?q?Sa=C3=BAl?= Ibarra =?utf-8?q?Corretg=C3=A9?=" <saul@ag-projects.com>
Date: Wed, 07 Sep 2016 16:00:04 -0500
Message-ID: <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com>
In-Reply-To: <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/xkIUSdq_lLuRf6ARVyrRpEJUIIs>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 07 Sep 2016 21:00:11 -0000

(+ shepherd)

On 7 Sep 2016, at 15:50, Peter Saint-Andre wrote:

> If so, I think we can take that
>> version to IETF last call.
>
> Great! The document shepherd might need to update his writeup.

On a quick scan, I think the shepherd writeup is okay, but we should let 
Saul verify that (and also confirm that he agrees this is ready to go to 
last call.)

Saul, do you agree on on both (or either)?

Thanks!

Ben.


From nobody Fri Sep  9 02:57:25 2016
Return-Path: <saul@ag-projects.com>
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 6DD1C12B3A9 for <stox@ietfa.amsl.com>; Fri,  9 Sep 2016 02:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 78GCyu0hxwip for <stox@ietfa.amsl.com>; Fri,  9 Sep 2016 02:57:21 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 511D012B3C5 for <stox@ietf.org>; Fri,  9 Sep 2016 02:55:57 -0700 (PDT)
Received: from [192.168.0.35] (unknown [90.209.144.173]) by mail.sipthor.net (Postfix) with ESMTPSA id E68C914AC036; Fri,  9 Sep 2016 11:55:48 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_F38826C8-7F5D-4A07-BE09-D7788F66CB95"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: =?utf-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
In-Reply-To: <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com>
Date: Fri, 9 Sep 2016 10:55:46 +0100
Message-Id: <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/7lcHK7F_KKKLj_6GzGZs6oOuj9A>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Fri, 09 Sep 2016 09:57:23 -0000

--Apple-Mail=_F38826C8-7F5D-4A07-BE09-D7788F66CB95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 07 Sep 2016, at 22:00, Ben Campbell <ben@nostrum.com> wrote:
>=20
> (+ shepherd)
>=20
> On 7 Sep 2016, at 15:50, Peter Saint-Andre wrote:
>=20
>> If so, I think we can take that
>>> version to IETF last call.
>>=20
>> Great! The document shepherd might need to update his writeup.
>=20
> On a quick scan, I think the shepherd writeup is okay, but we should =
let Saul verify that (and also confirm that he agrees this is ready to =
go to last call.)
>=20
> Saul, do you agree on on both (or either)?
>=20

Hi,

I just came across this, sorry! I=E2=80=99ll take a look on Monday since =
I=E2=80=99ll be ask the new couple of days, sorry about that!


Cheers!

--
Sa=C3=BAl Ibarra Corretg=C3=A9
AG Projects






--Apple-Mail=_F38826C8-7F5D-4A07-BE09-D7788F66CB95
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX0ocmAAoJEN2cyH9ENwiq1AsP/iT2XX+YbdJE6VmBNZL3zMgF
UopNtKGFseBqNmDcZ7GdTI7urFbSAP4AfZY7y1bwcOJWo6EC2UBhl73W3ZcEZ4nb
SMuC67Yw6y+E2BqOYsouX3CHdImxCzFDLA7M78GS7vD36hT7/U6y2xl3NWZTWG7J
KkiJJrQ79UDkvelozwhZOBE9bm2GqLiGogyRXyil3stKbnAWs9t1yWIBHuqOl9vM
8UYBUI1dVT14stuT3SIDPnG+rcF48L2irSSlAwHtfkBWn0Q6ue9sr1+uo3O7f7PC
DJgBi5BVY118bav3rsBejER8zPkob5M+XQ4chfM7rjoy/juJ7SM3u4xuQC76aFnZ
UZqJ7nvvr5vAmm5zGUd/hgNgAOSKlq31N1wV6fkpiPVAOpxa+/z4X6uSy/T5VIn1
QZYA/RuZB2mMRlfsXHdDP+Avod6KTCb8wjPURhRrSJKWklUcpDG22p/bY4OWq2ns
1mXDRq21V8dmE8unZX1ojKibMJvTxJzndh4iYbiS3PC7SwxOjliZj2LzEPoQYYFw
BmTDealIKhldx4WYiA9lcI3rj1FC0uWIkOSW1H8S0AR0lMGRHoq0v0h1IBHdnt83
OU+kOPinDELV7pO+9gB+tsIJFKjGwpgYQY/yDeguCFfkPdfh1Y5W6YvQrULrtRlA
5SXTp4KUKcs3UdhNxsvR
=N+9I
-----END PGP SIGNATURE-----

--Apple-Mail=_F38826C8-7F5D-4A07-BE09-D7788F66CB95--


From nobody Mon Sep 12 02:42:42 2016
Return-Path: <saul@ag-projects.com>
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 9B8CD12B1DB for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 02:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 kO3iX8iCHfpV for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 02:42:38 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A88C12B1E0 for <stox@ietf.org>; Mon, 12 Sep 2016 02:42:36 -0700 (PDT)
Received: from [192.168.0.11] (unknown [51.179.151.35]) by mail.sipthor.net (Postfix) with ESMTPSA id 3552814AC05D; Mon, 12 Sep 2016 11:42:33 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A4CA0D0E-0E57-4E86-9BF5-CDDBA8C71F3F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: =?utf-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
In-Reply-To: <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com>
Date: Mon, 12 Sep 2016 10:42:44 +0100
Message-Id: <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/NnurOH86wZAaA2H9oBxPj7c3xMU>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Mon, 12 Sep 2016 09:42:40 -0000

--Apple-Mail=_A4CA0D0E-0E57-4E86-9BF5-CDDBA8C71F3F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Review time!

Page 10: " As described in Section 6
, the XMPP-to-SIP gateway also generates a
   presence notification addressed to the XMPP user:
=E2=80=9C

Should we say =E2=80=9Cif the NOTIFY contains a body=E2=80=9D or is it =
obvious enough? It=E2=80=99s possible the SIP user is offline, but the =
XMPP is user is already authorised, so the NOTIFY will contain =
Subscription-State: active, but no body.

Page 11: "As can be seen, because SIMPLE does not
   have a construct that enables a contact to cancel her presence
   authorization,=E2=80=9D

There is: remove the user from the corresponding XCAP rule.  Next time =
presence is requested, it will be denied.  (the SUBSCRIBE dialog still =
needs to be terminated though).

Page 14: example 10

Since the Content-Length is 0, maybe omit Content-Type?

Page 15: flow example

Add a NOTIFY with state as =E2=80=9Cpending=E2=80=9D before sending the =
subscribe stanza to the XMPP server?

Page 19: [RFC6121] defines how XMPP

Missing RFC link?

Page 27: " As described in [RFC3856
], this cancels any notification dialog but
   causes a NOTIFY to be sent to the subscriber, just as a presence
   probe does (the transformation rules for presence notifications have
   been previously described in
Section 6.2 of this document).=E2=80=9D

A probe would be implemented as a new SUBSCRIBE dialog with expires 0, =
which does=E2=80=99t cancel all other dialogs.  So while the mechanism =
is the same, using a *new* SUBSCRIBE request with Expires: 0 would just =
be a probe, not a cancellation.

General note: the examples with "<show =
xmlns=3D'jabber:client'>away</show>=E2=80=9D lack the XML namespace =
declaration for =E2=80=9Cjabber=E2=80=9D.


These are all quite minor things, I think we are good to go for WGLC =
after small fixes for those.


Cheers!

--
Sa=C3=BAl Ibarra Corretg=C3=A9
AG Projects






--Apple-Mail=_A4CA0D0E-0E57-4E86-9BF5-CDDBA8C71F3F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX1niXAAoJEN2cyH9ENwiqEo8QAKQA1FRmmu7x0JlYaCHrB5Kc
fiEPIXYofZ6STetZaak/rZ24Q+FLSoVmLY+e+WFi5DmpDhAE9rAPBvaJp3VFyqsQ
4UqKrd+uotLYMsRcrn9aYFGxX+Y1mVZSE/9EO4YEBRgN48XtXqAsA6oWIMIb9yF0
e+s6sAgxFz8WchgGapaizvbYh7RhA1lGOtdeNtQKv96keSNZp/RTlZqZh968l2Hj
l/c7fNgZQcQR/fU+bmtzLI3wpXu0CwX5LsB6IJx3kvRcC9/4R4ua2Olfz6lco0/O
oMvKOhxGy76IPSw4XtRYCyWLouwTv07DCNMkjZqOYHEdjex26JeO7mfKFSHxW0Am
4o84vSx2G1nBaalIPvlS7pxiwV1bFEwHhwJmWO4KSOQPOdK/qn8RSnpeaId8c1v4
nP+W0j+irUUFzVITjUU+O4D/WSaGRbR3nnYSVOK/t03d0QKOF9Fqp/CenbpR6fis
PyP5DIBvPgpITp9Oo0yI+sNYUlwfIpzxI2ap35Gr4YBrDy9S3eFfZnr4A5Z8UGxs
N3EIB+eieuAoT0lT/uxkSPRdAeK/9qp3MVNVIvk6i6qZTHLovvLi9GNB/7jJQggN
kUOKHux1YcgyOqhzO+EyIDHLrpcYbFz5O91KZj6luu+GrnpHH3yshj+0SZWkGchh
cB6vczbaz3DQz6Zbx07P
=GiOI
-----END PGP SIGNATURE-----

--Apple-Mail=_A4CA0D0E-0E57-4E86-9BF5-CDDBA8C71F3F--


From nobody Mon Sep 12 07:43:43 2016
Return-Path: <ben@nostrum.com>
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 0965312B73F for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 07:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.407
X-Spam-Level: 
X-Spam-Status: No, score=-3.407 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.508] 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 EArhW6Q84G5V for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 07:43:38 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BAF112B2F8 for <stox@ietf.org>; Mon, 12 Sep 2016 07:26:40 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.86]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8CEQX8Y057607 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 12 Sep 2016 09:26:34 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.86] claimed to be [10.10.1.2]
From: "Ben Campbell" <ben@nostrum.com>
To: "=?utf-8?q?Sa=C3=BAl?= Ibarra =?utf-8?q?Corretg=C3=A9?=" <saul@ag-projects.com>
Date: Mon, 12 Sep 2016 10:26:32 -0400
Message-ID: <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com>
In-Reply-To: <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_CD30BDFE-B7F8-44D0-AFED-17469C37C0BB_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/agr8BIWRc7i3pXyCEYmTGvQi5II>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Mon, 12 Sep 2016 14:43:43 -0000

--=_MailMate_CD30BDFE-B7F8-44D0-AFED-17469C37C0BB_=
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

A few comments inline.

Thanks!

Ben.

On 12 Sep 2016, at 5:42, SaĂşl Ibarra CorretgĂ© wrote:

> Review time!
>
> Page 10: " As described in Section 6
> , the XMPP-to-SIP gateway also generates a
>    presence notification addressed to the XMPP user:
> â€ś
>
> Should we say â€śif the NOTIFY contains a bodyâ€ť or is it obvious 
> enough? Itâ€™s possible the SIP user is offline, but the XMPP is user 
> is already authorised, so the NOTIFY will contain Subscription-State: 
> active, but no body.

It's probably worth adding an example of how the the gateway might 
interpret an empty body. I assume that if this is the first NOTIFY in 
the dialog (notification session), the gateway would interpret that as 
unknown or possibly "closed". If previous NOTIFYs have in the same 
notification session, it should probably mean "no change".

>
> Page 11: "As can be seen, because SIMPLE does not
>    have a construct that enables a contact to cancel her presence
>    authorization,â€ť
>
> There is: remove the user from the corresponding XCAP rule.  Next time 
> presence is requested, it will be denied.  (the SUBSCRIBE dialog still 
> needs to be terminated though).

The text is about the subscriber, not the presentity. So if Juliet 
subscribes to Romeo's presence, Romeo can change the authorization rule 
(via xcap or otherwise). But _Juliet_ cannot.

I suppose "her authorization" can be a bit ambiguous. (If Romeo 
authorizes Juliet, whose authorization is it?)

>
> Page 14: example 10
>
> Since the Content-Length is 0, maybe omit Content-Type?
>
> Page 15: flow example
>
> Add a NOTIFY with state as â€śpendingâ€ť before sending the subscribe 
> stanza to the XMPP server?

That's a good question for the xmpp side. Is there an equivalent to the 
pending state? It's not really illegal to go directly to active. It 
might look unusual from the SIP side--but it's no different than 
subscribing to something you are already authorized to see.

>
> Page 19: [RFC6121] defines how XMPP
>
> Missing RFC link?
>
> Page 27: " As described in [RFC3856
> ], this cancels any notification dialog but
>    causes a NOTIFY to be sent to the subscriber, just as a presence
>    probe does (the transformation rules for presence notifications 
> have
>    been previously described in
> Section 6.2 of this document).â€ť
>
> A probe would be implemented as a new SUBSCRIBE dialog with expires 0, 
> which doesâ€™t cancel all other dialogs.  So while the mechanism is 
> the same, using a *new* SUBSCRIBE request with Expires: 0 would just 
> be a probe, not a cancellation.
>
> General note: the examples with "<show 
> xmlns='jabber:client'>away</show>â€ť lack the XML namespace 
> declaration for â€śjabberâ€ť.
>
> These are all quite minor things, I think we are good to go for WGLC 
> after small fixes for those.
>
> Cheers!
>
> --
> SaĂşl Ibarra CorretgĂ©
> AG Projects
>

--=_MailMate_CD30BDFE-B7F8-44D0-AFED-17469C37C0BB_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Hi,</p>

<p dir=3D"auto">A few comments inline.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">Ben.</p>

<p dir=3D"auto">On 12 Sep 2016, at 5:42, Sa=C3=BAl Ibarra Corretg=C3=A9 w=
rote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">Review time!
</div><div dir=3D"auto">
</div><div dir=3D"auto">Page 10: " As described in Section 6
</div><div dir=3D"auto">, the XMPP-to-SIP gateway also generates a
</div><div dir=3D"auto">   presence notification addressed to the XMPP us=
er:
</div><div dir=3D"auto">=E2=80=9C
</div><div dir=3D"auto">
</div><div dir=3D"auto">Should we say =E2=80=9Cif the NOTIFY contains a b=
ody=E2=80=9D or is it obvious enough? It=E2=80=99s possible the SIP user =
is offline, but the XMPP is user is already authorised, so the NOTIFY wil=
l contain Subscription-State: active, but no body.
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">It's probably worth adding an example of how the the gate=
way might interpret an empty body. I assume that if this is the first NOT=
IFY in the dialog (notification session), the gateway would interpret tha=
t as unknown or possibly "closed". If previous NOTIFYs have in the same n=
otification session, it should probably mean "no change".</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">
</div><div dir=3D"auto">Page 11: "As can be seen, because SIMPLE does not=

</div><div dir=3D"auto">   have a construct that enables a contact to can=
cel her presence
</div><div dir=3D"auto">   authorization,=E2=80=9D
</div><div dir=3D"auto">
</div><div dir=3D"auto">There is: remove the user from the corresponding =
XCAP rule.  Next time presence is requested, it will be denied.  (the SUB=
SCRIBE dialog still needs to be terminated though).
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">The text is about the subscriber, not the presentity. So =
if Juliet subscribes to Romeo's presence, Romeo can change the authorizat=
ion rule (via xcap or otherwise). But <em>Juliet</em> cannot.</p>

<p dir=3D"auto">I suppose "her authorization" can be a bit ambiguous. (If=
 Romeo authorizes Juliet, whose authorization is it?)</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">
</div><div dir=3D"auto">Page 14: example 10
</div><div dir=3D"auto">
</div><div dir=3D"auto">Since the Content-Length is 0, maybe omit Content=
-Type?
</div><div dir=3D"auto">
</div><div dir=3D"auto">Page 15: flow example
</div><div dir=3D"auto">
</div><div dir=3D"auto">Add a NOTIFY with state as =E2=80=9Cpending=E2=80=
=9D before sending the subscribe stanza to the XMPP server?
</div></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">That's a good question for the xmpp side. Is there an equ=
ivalent to the pending state? It's not really illegal to go directly to a=
ctive. It might look unusual from the SIP side--but it's no different tha=
n subscribing to something you are already authorized to see.</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:pre-wrap"><blockquote style=3D"border-left:2px =
solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div dir=3D"aut=
o">
</div><div dir=3D"auto">Page 19: [RFC6121] defines how XMPP
</div><div dir=3D"auto">
</div><div dir=3D"auto">Missing RFC link?
</div><div dir=3D"auto">
</div><div dir=3D"auto">Page 27: " As described in [RFC3856
</div><div dir=3D"auto">], this cancels any notification dialog but
</div><div dir=3D"auto">   causes a NOTIFY to be sent to the subscriber, =
just as a presence
</div><div dir=3D"auto">   probe does (the transformation rules for prese=
nce notifications have
</div><div dir=3D"auto">   been previously described in
</div><div dir=3D"auto">Section 6.2 of this document).=E2=80=9D
</div><div dir=3D"auto">
</div><div dir=3D"auto">A probe would be implemented as a new SUBSCRIBE d=
ialog with expires 0, which does=E2=80=99t cancel all other dialogs.  So =
while the mechanism is the same, using a *new* SUBSCRIBE request with Exp=
ires: 0 would just be a probe, not a cancellation.
</div><div dir=3D"auto">
</div><div dir=3D"auto">General note: the examples with "&lt;show xmlns=3D=
'jabber:client'&gt;away&lt;/show&gt;=E2=80=9D lack the XML namespace decl=
aration for =E2=80=9Cjabber=E2=80=9D.
</div><div dir=3D"auto">
</div><div dir=3D"auto">These are all quite minor things, I think we are =
good to go for WGLC after small fixes for those.
</div><div dir=3D"auto">
</div><div dir=3D"auto">Cheers!
</div><div dir=3D"auto">
</div><div dir=3D"auto">--
</div><div dir=3D"auto">Sa=C3=BAl Ibarra Corretg=C3=A9
</div><div dir=3D"auto">AG Projects
</div><div dir=3D"auto">
</div></blockquote></div>
<div style=3D"white-space:normal">
</div>
</div>
</body>
</html>

--=_MailMate_CD30BDFE-B7F8-44D0-AFED-17469C37C0BB_=--


From nobody Mon Sep 12 19:36:59 2016
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 EC19812B1A7 for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 19:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, 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 LyZDUUWb79FS for <stox@ietfa.amsl.com>; Mon, 12 Sep 2016 19:36:56 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C9BB312B0BF for <stox@ietf.org>; Mon, 12 Sep 2016 19:36:56 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E0A4640352; Mon, 12 Sep 2016 20:37:40 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>, =?UTF-8?Q?Sa=c3=bal_Ibarra_Corretg=c3=a9?= <saul@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <e688a48d-cdf5-aa30-9593-b4b3d6e341f5@stpeter.im>
Date: Mon, 12 Sep 2016 20:36:55 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/fDxjvaGfpxN1GatW6aXoEtO63b8>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Tue, 13 Sep 2016 02:36:59 -0000

Thanks for the feedback. Comments inline.

On 9/12/16 8:26 AM, Ben Campbell wrote:
> Hi,
>
> A few comments inline.
>
> Thanks!
>
> Ben.
>
> On 12 Sep 2016, at 5:42, Saúl Ibarra Corretgé wrote:
>
>     Review time!
>     Page 10: " As described in Section 6
>     , the XMPP-to-SIP gateway also generates a
>     presence notification addressed to the XMPP user:
>     “
>     Should we say “if the NOTIFY contains a body” or is it obvious
>     enough? It’s possible the SIP user is offline, but the XMPP is user
>     is already authorised, so the NOTIFY will contain
>     Subscription-State: active, but no body.
>
> It's probably worth adding an example of how the the gateway might
> interpret an empty body. I assume that if this is the first NOTIFY in
> the dialog (notification session), the gateway would interpret that as
> unknown or possibly "closed". If previous NOTIFYs have in the same
> notification session, it should probably mean "no change".

Good idea, will do.

>     Page 11: "As can be seen, because SIMPLE does not
>     have a construct that enables a contact to cancel her presence
>     authorization,”
>     There is: remove the user from the corresponding XCAP rule. Next
>     time presence is requested, it will be denied. (the SUBSCRIBE dialog
>     still needs to be terminated though).
>
> The text is about the subscriber, not the presentity. So if Juliet
> subscribes to Romeo's presence, Romeo can change the authorization rule
> (via xcap or otherwise). But /Juliet/ cannot.
>
> I suppose "her authorization" can be a bit ambiguous. (If Romeo
> authorizes Juliet, whose authorization is it?)

I was tempted to add "outbound" or "inbound" in all cases to make this 
crystal clear...

>     Page 14: example 10
>     Since the Content-Length is 0, maybe omit Content-Type?

Good catch.

>     Page 15: flow example
>     Add a NOTIFY with state as “pending” before sending the subscribe
>     stanza to the XMPP server?
>
> That's a good question for the xmpp side. Is there an equivalent to the
> pending state?

There are indeed pending states in XMPP:

https://tools.ietf.org/html/rfc6121#appendix-A.1

However, I excluded them in these mappings to avoid too much complexity.

> It's not really illegal to go directly to active. It
> might look unusual from the SIP side--but it's no different than
> subscribing to something you are already authorized to see.

We can make mention of them here but I'd prefer not to describe them in 
great detail. :-)

>     Page 19: [RFC6121] defines how XMPP
>     Missing RFC link?

Not really, but the wording could be improved.

>     Page 27: " As described in [RFC3856
>     ], this cancels any notification dialog but
>     causes a NOTIFY to be sent to the subscriber, just as a presence
>     probe does (the transformation rules for presence notifications have
>     been previously described in
>     Section 6.2 of this document).”
>     A probe would be implemented as a new SUBSCRIBE dialog with expires
>     0, which does’t cancel all other dialogs. So while the mechanism is
>     the same, using a *new* SUBSCRIBE request with Expires: 0 would just
>     be a probe, not a cancellation.

I will look into this. What you say sounds plausible but I'd like to 
double-check it against my reading of RFC 3856.

>     General note: the examples with "<show
>     xmlns='jabber:client'>away</show>” lack the XML namespace
>     declaration for “jabber”.

Another good catch.

>     These are all quite minor things, I think we are good to go for WGLC
>     after small fixes for those.
>     Cheers!

Great, I'll work on a slightly revised I-D this week.

Thanks!

Peter



From nobody Tue Sep 13 03:01:37 2016
Return-Path: <saul@ag-projects.com>
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 6EE5612B2B1 for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 03:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 21vVet-ZEO4J for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 03:01:34 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37BC612B2A7 for <stox@ietf.org>; Tue, 13 Sep 2016 03:01:30 -0700 (PDT)
Received: from [192.168.0.11] (unknown [51.179.151.35]) by mail.sipthor.net (Postfix) with ESMTPSA id 5DEC514AC06C; Tue, 13 Sep 2016 12:01:10 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6C39FAC1-0CA6-42C8-B5F8-FDB50A860A15"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: =?utf-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
In-Reply-To: <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com>
Date: Tue, 13 Sep 2016 11:01:06 +0100
Message-Id: <2548D475-6591-467E-A74E-8EDDA69CE184@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/IjeD9zuUa3jP1YiBkZUZJ5xjYfY>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Tue, 13 Sep 2016 10:01:36 -0000

--Apple-Mail=_6C39FAC1-0CA6-42C8-B5F8-FDB50A860A15
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>=20
>=20
> Page 11: "As can be seen, because SIMPLE does not
>=20
>    have a construct that enables a contact to cancel her presence
>=20
>    authorization,=E2=80=9D
>=20
>=20
> There is: remove the user from the corresponding XCAP rule.  Next time =
presence is requested, it will be denied.  (the SUBSCRIBE dialog still =
needs to be terminated though).
>=20
> The text is about the subscriber, not the presentity. So if Juliet =
subscribes to Romeo's presence, Romeo can change the authorization rule =
(via xcap or otherwise). But Juliet cannot.
>=20
> I suppose "her authorization" can be a bit ambiguous. (If Romeo =
authorizes Juliet, whose authorization is it?)
>=20
>=20

Ah, gotha. Maybe some clarification would help indeed.


Cheers,

--
Sa=C3=BAl Ibarra Corretg=C3=A9
AG Projects






--Apple-Mail=_6C39FAC1-0CA6-42C8-B5F8-FDB50A860A15
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX185mAAoJEN2cyH9ENwiqhSQP/1pRzvPTB7O3pYCN/SMHHhyd
K+chWplksAY9Hu/ESeNWZHF5+ZDjkUAih9VVyqeTr1aaPVH8iek/2IpT20uEmS3z
v4SZ3g5kICkyCYu/m/LaWtHvaUz1mFlVaGm4B12G8B9jnNj/oZEVbAo4gMRop1ol
jrkQOaSG2X805qBdbS04UAcCtoje/T6ocQBe5k8EEJIy068Ir5GV+WJOHfLz+/LN
b8aN/4eETT5qJPBwZNdE+ViiXYDi1i3q07kDPJL4F4o0e4FHPwSXCrLuRXmvGOUs
w41uzOVD2sMQ48u3eddzb6W8TjJU4IFzAMUabinUpbi85lIirxEf+J+qRF2GaHB0
XDQrkdam2wLWI6vjlJs1TpBou9n4n/Du58VVAGkrSacXZD+4KRcOmJH3t8igrSsz
Y1gI7RIWDtlYG4AYhOOSu3ppCVDuoaZlBsuPdkXDqJhLLbR9Z7QgfNLs31hdLAyP
lqAzJ+5tjyPNaUYxfg7pEKoP/wvYv9qiWjlHX2x34NS+H0hDdZ7jcQttp1adCVpY
sp389K81uE6ED3LDl9njhJ5PFgN3WfD+nYAU1XROsap2Ia4WA+nW6gbFsGGw+HR1
+CWTo/RV8e3Y2OL9nIOHePa6IzZyb+RVlgGREsFSEPdxIome4oFs9dnHUE0ABWzJ
LpcKuOlgCPBBPbPA1jU5
=Ip6O
-----END PGP SIGNATURE-----

--Apple-Mail=_6C39FAC1-0CA6-42C8-B5F8-FDB50A860A15--


From nobody Tue Sep 13 07:10:53 2016
Return-Path: <ben@nostrum.com>
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 8DF1212B561 for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 07:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508] 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 yrJ7eqNc1-Mz for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 07:10:47 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0386512B488 for <stox@ietf.org>; Tue, 13 Sep 2016 06:39:17 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.52]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id u8DDdBPE082464 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 13 Sep 2016 08:39:12 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.52] claimed to be [10.10.1.2]
From: "Ben Campbell" <ben@nostrum.com>
To: "=?utf-8?q?Sa=C3=BAl?= Ibarra =?utf-8?q?Corretg=C3=A9?=" <saul@ag-projects.com>
Date: Tue, 13 Sep 2016 09:39:10 -0400
Message-ID: <BA18C029-198B-4853-A0BD-6832B1AB34D5@nostrum.com>
In-Reply-To: <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5260)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/jUayycELW5jSBMVZgsMXdXOrjl0>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Tue, 13 Sep 2016 14:10:53 -0000

Oops, I missed a comment:

On 12 Sep 2016, at 5:42, SaĂşl Ibarra CorretgĂ© wrote:

> These are all quite minor things, I think we are good to go for WGLC 
> after small fixes for those.

The draft is currently in the AD Evaluation state, meaning that the WGLC 
has already completed and publication has been requested. Did you mean 
to say that we need to repeat the WGLC, or did you mean IETF last call?

There's probably enough changes that a repeat WGLC would be reasonable. 
OTOH, I am skeptical that the working group still has enough active 
participants for a repeated WGLC to add value.

Thanks!

Ben.


From nobody Tue Sep 13 09:02:55 2016
Return-Path: <saul@ag-projects.com>
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 A4A5712B551 for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 09:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 SbphCWPQS8PH for <stox@ietfa.amsl.com>; Tue, 13 Sep 2016 09:02:47 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4129012B5DC for <stox@ietf.org>; Tue, 13 Sep 2016 08:35:32 -0700 (PDT)
Received: from [192.168.0.11] (unknown [51.179.151.35]) by mail.sipthor.net (Postfix) with ESMTPSA id 414A614AC06F; Tue, 13 Sep 2016 17:35:27 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C7A37D1C-697D-454F-81AC-4CC6746652A3"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: =?utf-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
In-Reply-To: <BA18C029-198B-4853-A0BD-6832B1AB34D5@nostrum.com>
Date: Tue, 13 Sep 2016 16:35:22 +0100
Message-Id: <40AD2CAA-5A5C-41FC-BB49-88F4DEFCD07B@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <BA18C029-198B-4853-A0BD-6832B1AB34D5@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/vuCLW9mot146c8286dIGKoTkxq8>
Cc: stox@ietf.org, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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: Tue, 13 Sep 2016 16:02:53 -0000

--Apple-Mail=_C7A37D1C-697D-454F-81AC-4CC6746652A3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 13 Sep 2016, at 14:39, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Oops, I missed a comment:
>=20
> On 12 Sep 2016, at 5:42, Sa=C3=BAl Ibarra Corretg=C3=A9 wrote:
>=20
>> These are all quite minor things, I think we are good to go for WGLC =
after small fixes for those.
>=20
> The draft is currently in the AD Evaluation state, meaning that the =
WGLC has already completed and publication has been requested. Did you =
mean to say that we need to repeat the WGLC, or did you mean IETF last =
call?
>=20
> There's probably enough changes that a repeat WGLC would be =
reasonable. OTOH, I am skeptical that the working group still has enough =
active participants for a repeated WGLC to add value.
>=20

Sorry, wrong terminology :-) IETF last call.  These are not big =
structural changes, I don=E2=80=99t think we need another WGLC.


Cheers!

--
Sa=C3=BAl Ibarra Corretg=C3=A9
AG Projects






--Apple-Mail=_C7A37D1C-697D-454F-81AC-4CC6746652A3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX2By+AAoJEN2cyH9ENwiqFcEP/3diVEX4A/Nn0zcVifG2UUOg
6Ev6APyGUIchLI/fbOHKnzZYJXlSoY4E7CUTqHbmJ8YvIH48rVJGz+EaF6YpzP/9
uDlokWNKq0D+nJ7ozjn4KJCNoN5S2IW2rcBsGZhPKokIq9lWmHy9MQOH9Mi2U2md
BofyIw2N1gmouOIcLdxrtCSa26XD8foNDcu/Q7Ro4blNzEVhAIUR/E7k6CTcIAWg
wiOzTp02JQgegJk5GhxxUybYOOys4J9JTV5TwLeBCEzRPoc5DzsW1Sjly7b28+XA
mT+tq/3InCROnVsLh4t4ErkmMfi+PM1WpY73b6whc1Ug3ZPT9OkZJIoTh4GtlX1x
5Ta6KsleWVus6QwC3uwKQDd1G/lGemk9bLGX10cQmk7YTBFIeyfBsSlLz687C06W
y5AwGTdKukuAjfXLhECoaFRQBNegMSHZYTma01X7GZmq4fCjroaQk0d/t43/Ko+g
Fr70CZJ2ppt1uvzsdIlWK5TOBMRhUvW1hWYgNWup+ObJbNkbu99xf3SQF2cLHKqY
3fiTnWlOb8+8AwJCmclFJ113X0gBMeAUrMITN8MZ+ER2XJt74CXxfgaz1yCTRFVV
6u0f3g7jMQ7vS++hr5Bzv/l+QE1Ll9RLRwTWF27ZD27zbyL2Nnb5Y8G1zORn/mjz
Kwxv1PKp1a13pOEL1pgC
=beQQ
-----END PGP SIGNATURE-----

--Apple-Mail=_C7A37D1C-697D-454F-81AC-4CC6746652A3--


From nobody Wed Sep 14 08:48:09 2016
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 EA8E112B744 for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 08:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, 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 KHwEozHxwI1w for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 08:48:06 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 465BD12B748 for <stox@ietf.org>; Wed, 14 Sep 2016 08:24:05 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0624541707; Wed, 14 Sep 2016 09:24:55 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>, =?UTF-8?Q?Sa=c3=bal_Ibarra_Corretg=c3=a9?= <saul@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com> <e688a48d-cdf5-aa30-9593-b4b3d6e341f5@stpeter.im>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <5bc83063-11ad-aa70-723a-2bc9127685d8@stpeter.im>
Date: Wed, 14 Sep 2016 09:24:04 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <e688a48d-cdf5-aa30-9593-b4b3d6e341f5@stpeter.im>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/21mbDPEG-XFBjG0rbaI00W39UAY>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 14 Sep 2016 15:48:09 -0000

A few additional notes...

On 9/12/16 8:36 PM, Peter Saint-Andre wrote:
> Thanks for the feedback. Comments inline.
>
> On 9/12/16 8:26 AM, Ben Campbell wrote:
>> Hi,
>>
>> A few comments inline.
>>
>> Thanks!
>>
>> Ben.
>>
>> On 12 Sep 2016, at 5:42, Saúl Ibarra Corretgé wrote:
>>
>>     Review time!
>>     Page 10: " As described in Section 6
>>     , the XMPP-to-SIP gateway also generates a
>>     presence notification addressed to the XMPP user:
>>     “
>>     Should we say “if the NOTIFY contains a body” or is it obvious
>>     enough? It’s possible the SIP user is offline, but the XMPP is user
>>     is already authorised, so the NOTIFY will contain
>>     Subscription-State: active, but no body.
>>
>> It's probably worth adding an example of how the the gateway might
>> interpret an empty body. I assume that if this is the first NOTIFY in
>> the dialog (notification session), the gateway would interpret that as
>> unknown or possibly "closed". If previous NOTIFYs have in the same
>> notification session, it should probably mean "no change".
>
> Good idea, will do.

    As described in Section 6, if this first NOTIFY in the notification
    session contains a body then the XMPP-to-SIP gateway also generates a
    presence notification addressed to the XMPP user (if the NOTIFY does
    not contain a body then the gateway would interpret it as unknown or
    "closed"):

>>     Page 11: "As can be seen, because SIMPLE does not
>>     have a construct that enables a contact to cancel her presence
>>     authorization,”
>>     There is: remove the user from the corresponding XCAP rule. Next
>>     time presence is requested, it will be denied. (the SUBSCRIBE dialog
>>     still needs to be terminated though).
>>
>> The text is about the subscriber, not the presentity. So if Juliet
>> subscribes to Romeo's presence, Romeo can change the authorization rule
>> (via xcap or otherwise). But /Juliet/ cannot.
>>
>> I suppose "her authorization" can be a bit ambiguous. (If Romeo
>> authorizes Juliet, whose authorization is it?)
>
> I was tempted to add "outbound" or "inbound" in all cases to make this
> crystal clear...

Changed to "cancel her outbound presence authorization"

<snip/>

>>     Page 27: " As described in [RFC3856
>>     ], this cancels any notification dialog but
>>     causes a NOTIFY to be sent to the subscriber, just as a presence
>>     probe does (the transformation rules for presence notifications have
>>     been previously described in
>>     Section 6.2 of this document).”
>>     A probe would be implemented as a new SUBSCRIBE dialog with expires
>>     0, which does’t cancel all other dialogs. So while the mechanism is
>>     the same, using a *new* SUBSCRIBE request with Expires: 0 would just
>>     be a probe, not a cancellation.
>
> I will look into this. What you say sounds plausible but I'd like to
> double-check it against my reading of RFC 3856.

Yes, that looks right. I would change things as follows (note the new 
Call-ID, too):

    A SIP-to-XMPP gateway would transform the presence probe into its SIP
    equivalent, which is a SUBSCRIBE request with an Expires header value
    of zero in a new dialog:

    Example 23: SIP Transformation of XMPP Presence Probe

    |  SUBSCRIBE sip:romeo@example.net SIP/2.0
    |  Via: SIP/2.0/TCP x2s.example.com;branch=z9hG4bKna998sk
    |  From: <sip:juliet@example.com>;tag=j89d
    |  Call-ID: 2398B737-566F-4CBB-A21A-1F8EEF7AF423
    |  Event: presence
    |  Max-Forwards: 70
    |  CSeq: 1 SUBSCRIBE
    |  Contact: <sip:juliet@example.com>;gr=yn0cl4bnw0yr3vym
    |  Accept: application/pidf+xml
    |  Expires: 0
    |  Content-Length: 0

    As described in [RFC3856], this causes a NOTIFY to be sent to the
    subscriber, just as a presence probe does (the transformation rules
    for presence notifications have been previously described in
    Section 6.2 of this document).

>>     General note: the examples with "<show
>>     xmlns='jabber:client'>away</show>” lack the XML namespace
>>     declaration for “jabber”.
>
> Another good catch.

Actually, 'jabber' is not a prefix here and the namespace name is indeed 
"jabber:client" - this was defined in the very early days of XML 
namespaces and we Jabberites didn't fully understand what a namespace 
name was supposed to look like. :(

If that all looks good, I will publish a revised I-D soon.

Peter



From nobody Wed Sep 14 08:49:01 2016
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 C67D212B6FC for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 08:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.41
X-Spam-Level: 
X-Spam-Status: No, score=-3.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.508, 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 x_EYWdQhRtIZ for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 08:48:58 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E9EFA12B798 for <stox@ietf.org>; Wed, 14 Sep 2016 08:25:28 -0700 (PDT)
Received: from aither.local (unknown [73.34.202.214]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id D3FB341707; Wed, 14 Sep 2016 09:26:19 -0600 (MDT)
To: Ben Campbell <ben@nostrum.com>, =?UTF-8?Q?Sa=c3=bal_Ibarra_Corretg=c3=a9?= <saul@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com> <e688a48d-cdf5-aa30-9593-b4b3d6e341f5@stpeter.im> <5bc83063-11ad-aa70-723a-2bc9127685d8@stpeter.im>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <6cd05347-ae22-28e2-fa05-297c49711d6d@stpeter.im>
Date: Wed, 14 Sep 2016 09:25:28 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <5bc83063-11ad-aa70-723a-2bc9127685d8@stpeter.im>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/plEPN3iR9l95iXEB2y_cy4YQw6o>
Cc: stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 14 Sep 2016 15:49:01 -0000

On 9/14/16 9:24 AM, Peter Saint-Andre wrote:
> A few additional notes...
>
> On 9/12/16 8:36 PM, Peter Saint-Andre wrote:
>> Thanks for the feedback. Comments inline.
>>
>> On 9/12/16 8:26 AM, Ben Campbell wrote:
>>> Hi,
>>>
>>> A few comments inline.
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>> On 12 Sep 2016, at 5:42, Saúl Ibarra Corretgé wrote:
>>>
>>>     Review time!
>>>     Page 10: " As described in Section 6
>>>     , the XMPP-to-SIP gateway also generates a
>>>     presence notification addressed to the XMPP user:
>>>     “
>>>     Should we say “if the NOTIFY contains a body” or is it obvious
>>>     enough? It’s possible the SIP user is offline, but the XMPP is user
>>>     is already authorised, so the NOTIFY will contain
>>>     Subscription-State: active, but no body.
>>>
>>> It's probably worth adding an example of how the the gateway might
>>> interpret an empty body. I assume that if this is the first NOTIFY in
>>> the dialog (notification session), the gateway would interpret that as
>>> unknown or possibly "closed". If previous NOTIFYs have in the same
>>> notification session, it should probably mean "no change".
>>
>> Good idea, will do.
>
>    As described in Section 6, if this first NOTIFY in the notification
>    session contains a body then the XMPP-to-SIP gateway also generates a
>    presence notification addressed to the XMPP user (if the NOTIFY does
>    not contain a body then the gateway would interpret it as unknown or
>    "closed"):
>
>>>     Page 11: "As can be seen, because SIMPLE does not
>>>     have a construct that enables a contact to cancel her presence
>>>     authorization,”
>>>     There is: remove the user from the corresponding XCAP rule. Next
>>>     time presence is requested, it will be denied. (the SUBSCRIBE dialog
>>>     still needs to be terminated though).
>>>
>>> The text is about the subscriber, not the presentity. So if Juliet
>>> subscribes to Romeo's presence, Romeo can change the authorization rule
>>> (via xcap or otherwise). But /Juliet/ cannot.
>>>
>>> I suppose "her authorization" can be a bit ambiguous. (If Romeo
>>> authorizes Juliet, whose authorization is it?)
>>
>> I was tempted to add "outbound" or "inbound" in all cases to make this
>> crystal clear...
>
> Changed to "cancel her outbound presence authorization"
>
> <snip/>
>
>>>     Page 27: " As described in [RFC3856
>>>     ], this cancels any notification dialog but
>>>     causes a NOTIFY to be sent to the subscriber, just as a presence
>>>     probe does (the transformation rules for presence notifications have
>>>     been previously described in
>>>     Section 6.2 of this document).”
>>>     A probe would be implemented as a new SUBSCRIBE dialog with expires
>>>     0, which does’t cancel all other dialogs. So while the mechanism is
>>>     the same, using a *new* SUBSCRIBE request with Expires: 0 would just
>>>     be a probe, not a cancellation.
>>
>> I will look into this. What you say sounds plausible but I'd like to
>> double-check it against my reading of RFC 3856.
>
> Yes, that looks right. I would change things as follows (note the new
> Call-ID, too):
>
>    A SIP-to-XMPP gateway would transform the presence probe into its SIP
>    equivalent, which is a SUBSCRIBE request with an Expires header value
>    of zero in a new dialog:
>
>    Example 23: SIP Transformation of XMPP Presence Probe
>
>    |  SUBSCRIBE sip:romeo@example.net SIP/2.0
>    |  Via: SIP/2.0/TCP x2s.example.com;branch=z9hG4bKna998sk
>    |  From: <sip:juliet@example.com>;tag=j89d
>    |  Call-ID: 2398B737-566F-4CBB-A21A-1F8EEF7AF423
>    |  Event: presence
>    |  Max-Forwards: 70
>    |  CSeq: 1 SUBSCRIBE
>    |  Contact: <sip:juliet@example.com>;gr=yn0cl4bnw0yr3vym
>    |  Accept: application/pidf+xml
>    |  Expires: 0
>    |  Content-Length: 0
>
>    As described in [RFC3856], this causes a NOTIFY to be sent to the
>    subscriber, just as a presence probe does (the transformation rules
>    for presence notifications have been previously described in
>    Section 6.2 of this document).
>
>>>     General note: the examples with "<show
>>>     xmlns='jabber:client'>away</show>” lack the XML namespace
>>>     declaration for “jabber”.
>>
>> Another good catch.
>
> Actually, 'jabber' is not a prefix here and the namespace name is indeed
> "jabber:client" - this was defined in the very early days of XML
> namespaces and we Jabberites didn't fully understand what a namespace
> name was supposed to look like. :(
>
> If that all looks good, I will publish a revised I-D soon.

A diff is here:

https://github.com/stpeter/sip-xmpp/commit/a3ded08cbf1cc527f3f648813b3ecc46d5039094#diff-7f5e67ec097d24a4490853a1770f411b

Peter


From nobody Wed Sep 14 09:28:01 2016
Return-Path: <saul@ag-projects.com>
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 DBB3F12B33A for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 09:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 9EZH7SRhRw0d for <stox@ietfa.amsl.com>; Wed, 14 Sep 2016 09:27:56 -0700 (PDT)
Received: from mail.sipthor.net (node16.dns-hosting.info [81.23.228.161]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EDFB12B34F for <stox@ietf.org>; Wed, 14 Sep 2016 09:27:54 -0700 (PDT)
Received: from [192.168.0.35] (unknown [90.209.144.173]) by mail.sipthor.net (Postfix) with ESMTPSA id 6AB1814AC039; Wed, 14 Sep 2016 18:27:51 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7F221E24-5BFE-4461-A87A-0DAB317B7647"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: =?utf-8?Q?Sa=C3=BAl_Ibarra_Corretg=C3=A9?= <saul@ag-projects.com>
In-Reply-To: <6cd05347-ae22-28e2-fa05-297c49711d6d@stpeter.im>
Date: Wed, 14 Sep 2016 17:27:50 +0100
Message-Id: <B5010EFC-5A6D-4531-94F7-EC733B46B66C@ag-projects.com>
References: <147241625250.24476.13333521107304467910.idtracker@ietfa.amsl.com> <a139f13c-9745-0d86-853b-d5d6b8c9124c@stpeter.im> <E1C65C7E-CDFF-40BC-AF01-B2F029B64E6E@nostrum.com> <931fcd90-11c8-0b58-b3ad-eb6e7be2557e@stpeter.im> <f12534a1-bdce-925f-3358-c22975dd3bbe@stpeter.im> <512b8d52-68e1-2bdd-d153-20e24fbb73de@stpeter.im> <B197ACCC-5DB0-4C8F-8C54-1159A89B1796@nostrum.com> <969223de-c09e-eba5-a4a3-4969539c807e@stpeter.im> <87BE83BB-946B-4833-A34C-D890E783F214@nostrum.com> <76151e8b-9abf-7587-c36d-e2bf38180245@stpeter.im> <0C304BC3-0AD3-48C4-958B-AC44122892D7@nostrum.com> <5FA29740-BCD2-402D-BEB1-417A66CA7603@ag-projects.com> <81A30B28-EEDE-4BF2-8BA1-7CD148DF7ECE@ag-projects.com> <233A680F-224C-4799-B20E-E3962908E8DB@nostrum.com> <e688a48d-cdf5-aa30-9593-b4b3d6e341f5@stpeter.im> <5bc83063-11ad-aa70-723a-2bc9127685d8@stpeter.im> <6cd05347-ae22-28e2-fa05-297c49711d6d@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/lsW2D-Bi1lqLm3TgDBeCi318itk>
Cc: Ben Campbell <ben@nostrum.com>, stox@ietf.org
Subject: Re: [Stox] I-D Action: draft-ietf-stox-7248bis-09.txt
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, 14 Sep 2016 16:27:59 -0000

--Apple-Mail=_7F221E24-5BFE-4461-A87A-0DAB317B7647
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On 14 Sep 2016, at 16:25, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:
>=20
> On 9/14/16 9:24 AM, Peter Saint-Andre wrote:
>> A few additional notes...
>>=20
>> On 9/12/16 8:36 PM, Peter Saint-Andre wrote:
>>> Thanks for the feedback. Comments inline.
>>>=20
>>> On 9/12/16 8:26 AM, Ben Campbell wrote:
>>>> Hi,
>>>>=20
>>>> A few comments inline.
>>>>=20
>>>> Thanks!
>>>>=20
>>>> Ben.
>>>>=20
>>>> On 12 Sep 2016, at 5:42, Sa=FAl Ibarra Corretg=E9 wrote:
>>>>=20
>>>>    Review time!
>>>>    Page 10: " As described in Section 6
>>>>    , the XMPP-to-SIP gateway also generates a
>>>>    presence notification addressed to the XMPP user:
>>>>    =93
>>>>    Should we say =93if the NOTIFY contains a body=94 or is it =
obvious
>>>>    enough? It=92s possible the SIP user is offline, but the XMPP is =
user
>>>>    is already authorised, so the NOTIFY will contain
>>>>    Subscription-State: active, but no body.
>>>>=20
>>>> It's probably worth adding an example of how the the gateway might
>>>> interpret an empty body. I assume that if this is the first NOTIFY =
in
>>>> the dialog (notification session), the gateway would interpret that =
as
>>>> unknown or possibly "closed". If previous NOTIFYs have in the same
>>>> notification session, it should probably mean "no change".
>>>=20
>>> Good idea, will do.
>>=20
>>   As described in Section 6, if this first NOTIFY in the notification
>>   session contains a body then the XMPP-to-SIP gateway also generates =
a
>>   presence notification addressed to the XMPP user (if the NOTIFY =
does
>>   not contain a body then the gateway would interpret it as unknown =
or
>>   "closed"):
>>=20
>>>>    Page 11: "As can be seen, because SIMPLE does not
>>>>    have a construct that enables a contact to cancel her presence
>>>>    authorization,=94
>>>>    There is: remove the user from the corresponding XCAP rule. Next
>>>>    time presence is requested, it will be denied. (the SUBSCRIBE =
dialog
>>>>    still needs to be terminated though).
>>>>=20
>>>> The text is about the subscriber, not the presentity. So if Juliet
>>>> subscribes to Romeo's presence, Romeo can change the authorization =
rule
>>>> (via xcap or otherwise). But /Juliet/ cannot.
>>>>=20
>>>> I suppose "her authorization" can be a bit ambiguous. (If Romeo
>>>> authorizes Juliet, whose authorization is it?)
>>>=20
>>> I was tempted to add "outbound" or "inbound" in all cases to make =
this
>>> crystal clear...
>>=20
>> Changed to "cancel her outbound presence authorization"
>>=20
>> <snip/>
>>=20
>>>>    Page 27: " As described in [RFC3856
>>>>    ], this cancels any notification dialog but
>>>>    causes a NOTIFY to be sent to the subscriber, just as a presence
>>>>    probe does (the transformation rules for presence notifications =
have
>>>>    been previously described in
>>>>    Section 6.2 of this document).=94
>>>>    A probe would be implemented as a new SUBSCRIBE dialog with =
expires
>>>>    0, which does=92t cancel all other dialogs. So while the =
mechanism is
>>>>    the same, using a *new* SUBSCRIBE request with Expires: 0 would =
just
>>>>    be a probe, not a cancellation.
>>>=20
>>> I will look into this. What you say sounds plausible but I'd like to
>>> double-check it against my reading of RFC 3856.
>>=20
>> Yes, that looks right. I would change things as follows (note the new
>> Call-ID, too):
>>=20
>>   A SIP-to-XMPP gateway would transform the presence probe into its =
SIP
>>   equivalent, which is a SUBSCRIBE request with an Expires header =
value
>>   of zero in a new dialog:
>>=20
>>   Example 23: SIP Transformation of XMPP Presence Probe
>>=20
>>   |  SUBSCRIBE sip:romeo@example.net SIP/2.0
>>   |  Via: SIP/2.0/TCP x2s.example.com;branch=3Dz9hG4bKna998sk
>>   |  From: <sip:juliet@example.com>;tag=3Dj89d
>>   |  Call-ID: 2398B737-566F-4CBB-A21A-1F8EEF7AF423
>>   |  Event: presence
>>   |  Max-Forwards: 70
>>   |  CSeq: 1 SUBSCRIBE
>>   |  Contact: <sip:juliet@example.com>;gr=3Dyn0cl4bnw0yr3vym
>>   |  Accept: application/pidf+xml
>>   |  Expires: 0
>>   |  Content-Length: 0
>>=20
>>   As described in [RFC3856], this causes a NOTIFY to be sent to the
>>   subscriber, just as a presence probe does (the transformation rules
>>   for presence notifications have been previously described in
>>   Section 6.2 of this document).
>>=20
>>>>    General note: the examples with "<show
>>>>    xmlns=3D'jabber:client'>away</show>=94 lack the XML namespace
>>>>    declaration for =93jabber=94.
>>>=20
>>> Another good catch.
>>=20
>> Actually, 'jabber' is not a prefix here and the namespace name is =
indeed
>> "jabber:client" - this was defined in the very early days of XML
>> namespaces and we Jabberites didn't fully understand what a namespace
>> name was supposed to look like. :(
>>=20
>> If that all looks good, I will publish a revised I-D soon.
>=20
> A diff is here:
>=20
> =
https://github.com/stpeter/sip-xmpp/commit/a3ded08cbf1cc527f3f648813b3ecc4=
6d5039094#diff-7f5e67ec097d24a4490853a1770f411b
>=20

LGTM.  No objections from me!

--
Sa=FAl Ibarra Corretg=E9
AG Projects






--Apple-Mail=_7F221E24-5BFE-4461-A87A-0DAB317B7647
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX2XqGAAoJEN2cyH9ENwiq85wP/RcjVjRfaojeGsXJliV/Td+C
W1RDIT+u5PdpgcpycXZVRJIDWBhMzF17pTBFU65Qd40H5OjhFY+EHIruL4+Eronr
0jw6A6VZRblWtH3Nil9H+Eab3c7RoXoJxDwrNqIgFljZf3gy/wSmej1EAHCfYZe+
IT6k0eTba+lmJZJ0rMaMpbPRVvz82/MwI8GUz1mxyUH9IO5EDsFZtf2MhJ+zNI/g
Qxe5hNi/QvWARIRj0GXV+zrkFcwnsOPv16d3ffP9iloygpePKlpq7x/Ukglwi/uU
req45dXolNwGFd4Oih/QQx55g/kUO+I/9El+I+Yfj6s7J1rCA4/Lw5evPBu2YU2a
nIi/LTkjW7A7AxjOYqKT9IbxJeAGRjwMQobsCe7mrVeGBKDbY65y8HUf2exhDEBL
218PomhD4iJz6MOKmJ+Ddbx0AYEDe0vT3r8PLLCsGdY9Q1XyQfgX8EleTFqm3ZsM
hzneeyLBrUNi1j4UnwKspFou+r4m32HgRQx9/9u6aFWvPc9+h7l4eCawhykvSKKv
S0J451rosJeAUn6wfUuwqDsJlVkPMuqYan0jt0TXy7zZxh57e07bCNZayyU3R3Tm
oeeoXMJQJCxbIQ35pcNqHUnj/BcW1UmvC0+nhDLKddYggyEsECziX4+KMkhjL5hj
mkIKfPCEoqdrIe0PkNlW
=ZDnl
-----END PGP SIGNATURE-----

--Apple-Mail=_7F221E24-5BFE-4461-A87A-0DAB317B7647--


From nobody Wed Sep 14 18:38:06 2016
Return-Path: <internet-drafts@ietf.org>
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 9452512B111; Wed, 14 Sep 2016 18:38:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147390348560.29915.4608723702392933231.idtracker@ietfa.amsl.com>
Date: Wed, 14 Sep 2016 18:38:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/PsEeDoAJMtXb7khSISIrjp0ugX8>
Cc: stox@ietf.org
Subject: [Stox] I-D Action: draft-ietf-stox-7248bis-12.txt
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: Thu, 15 Sep 2016 01:38:05 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIP-TO-XMPP of the IETF.

        Title           : Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
        Author          : Peter Saint-Andre
	Filename        : draft-ietf-stox-7248bis-12.txt
	Pages           : 31
	Date            : 2016-09-14

Abstract:
   This document defines a bidirectional protocol mapping for the
   exchange of presence information between the Session Initiation
   Protocol (SIP) and the Extensible Messaging and Presence Protocol
   (XMPP).  This document obsoletes RFC 7248.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-stox-7248bis-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-stox-7248bis-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Sep 22 08:19:57 2016
Return-Path: <iesg-secretary@ietf.org>
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 9CC5312B673; Thu, 22 Sep 2016 08:19:55 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.33.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <147455759563.22510.4201839411761164792.idtracker@ietfa.amsl.com>
Date: Thu, 22 Sep 2016 08:19:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/stox/Tps0E7vhiKyaPFkM2QLdpXj349k>
Cc: draft-ietf-stox-7248bis@ietf.org, ben@nostrum.com, saul@ag-projects.com, stox-chairs@ietf.org, stox@ietf.org
Subject: [Stox] Last Call: <draft-ietf-stox-7248bis-12.txt> (Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence) to Proposed Standard
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Thu, 22 Sep 2016 15:19:55 -0000

The IESG has received a request from the SIP-TO-XMPP WG (stox) to
consider the following document:
- 'Interworking between the Session Initiation Protocol (SIP) and the
   Extensible Messaging and Presence Protocol (XMPP): Presence'
  <draft-ietf-stox-7248bis-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-10-06. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document defines a bidirectional protocol mapping for the
   exchange of presence information between the Session Initiation
   Protocol (SIP) and the Extensible Messaging and Presence Protocol
   (XMPP).  This document obsoletes RFC 7248.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-stox-7248bis/ballot/


No IPR declarations have been submitted directly on this I-D.




