IETF Logo Mail Archive

Re: [sipcore] New Version Notification for draft-sparks-sipcore-refer-explicit-subscription-01

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 06 October 2014 14:59 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0265E1A6FC7 for <sipcore@ietfa.amsl.com>; Mon, 6 Oct 2014 07:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Z2IrWnZcN19t for <sipcore@ietfa.amsl.com>; Mon, 6 Oct 2014 07:59:34 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FCC41A01A8 for <sipcore@ietf.org>; Mon, 6 Oct 2014 07:59:33 -0700 (PDT)
X-AuditID: c1b4fb3a-f79da6d0000008c7-d3-5432ae532717
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 92.CD.02247.35EA2345; Mon, 6 Oct 2014 16:59:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0174.001; Mon, 6 Oct 2014 16:59:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Robert Sparks <rjsparks@nostrum.com>, OKUMURA Shinji <ietf.shinji@gmail.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] New Version Notification for draft-sparks-sipcore-refer-explicit-subscription-01
Thread-Index: AQHP4Sitk7syhy5dEkWF18PjbgOJz5wi/wqAgAAq55k=
Date: Mon, 06 Oct 2014 14:59:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D46A059@ESESSMB209.ericsson.se>
References: <20140908203132.10649.77126.idtracker@ietfa.amsl.com> <540E1444.4020205@nostrum.com> <21CFDEE5BE1BABietf.shinji@gmail.com> <542E62B6.8010309@nostrum.com> <52CFE128A63254ietf.shinji@gmail.com>,<5432A675.9020702@nostrum.com>
In-Reply-To: <5432A675.9020702@nostrum.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D46A059ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+JvjW7wOqMQg5+vNSyW9K9hs7g2p5HN 4uuPTWwOzB47Z91l91iy5CeTx6ydT1gCmKO4bFJSczLLUov07RK4Mg49nMJeMNWg4t3VM+wN jJ2aXYycHBICJhJTt39ghrDFJC7cW8/WxcjFISRwlFHizYIlTBDOYkaJhQ9uMHYxcnCwCVhI dP/TBmkQEaiUuLDyGhOILSyQKXFh0mwmiHiWxKMt91ggbCuJCV9fs4C0sgioSGxbGQAS5hXw lZjx7A/U+A+MEq1nv4LVcwpoS+z+PwVsDiPQQd9PrQGzmQXEJZq+rGSFOFRAYsme81BHi0q8 fPyPFaImX+Lx+24miAWCEidnPmGZwCg8C0n7LCRls5CUQcQNJL68vw1la0ssW/iaGcLWl+h+ f5oJWXwBI/sqRtHi1OLi3HQjI73Uoszk4uL8PL281JJNjMCYOrjlt9UOxoPPHQ8xCnAwKvHw Juw3DBFiTSwrrsw9xCjNwaIkzrvw3LxgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxqbbdN TCSOfZvVnD6r/sMl6WRJbRHB38kbQlaZTb6Qrj2Nx3Pq675XxX37ZRb+2fl6yjqRfWpcDmfT 5y6/fKgo5IyF6qQVywIM5H22H9lpuUGVtzx1wtkdj8Pn7/RbeYnhkwf/4b38PBc5rc5HM777 n2u5RqnXzzsqjF8ug+kv80W3aLW9TReUWIozEg21mIuKEwHkIUZuigIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/Ad2OSxZEb2EpBAdoDOL7iweO45Y
Subject: Re: [sipcore] New Version Notification for draft-sparks-sipcore-refer-explicit-subscription-01
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Oct 2014 14:59:36 -0000

Hi,

This of course does not apply to in-dialog REFERs, where forking does not occur.

Regards,

Christer


Sent from my Windows Phone
________________________________
From: Robert Sparks<mailto:rjsparks@nostrum.com>
Sent: ‎06/‎10/‎2014 17:26
To: OKUMURA Shinji<mailto:ietf.shinji@gmail.com>; sipcore@ietf.org<mailto:sipcore@ietf.org>
Subject: Re: [sipcore] New Version Notification for draft-sparks-sipcore-refer-explicit-subscription-01


On 10/6/14 12:44 AM, OKUMURA Shinji wrote:
> Hello Robert,
>
>> On 10/3/14 10:40 AM, OKUMURA Shinji wrote:
>>> Hi,
>>>
>>> As a general rule, REFER request may fork.
>>> But a referrer receives only one response(i.e. Refer-Events-At).
>>> Does this draft disallow a REFER request to be forked?
>> No.
>>
>> If the REFER forks, it will get responses from each branch of the fork.
>> The response from each branch will have its own information about whether
>> the REFER was accepted on that branch, including its own Refer-Events-At
>> URI.
> In accordance with the following, a successful response for REFER
> request is only one.
>
> RFC3261
> 17.1.2.1 Overview of the non-INVITE Transaction
>
>     Unlike an INVITE transaction, a non-INVITE transaction has no special
>     handling for the 2xx response.  The result is that only a single 2xx
>     response to a non-INVITE is ever delivered to a UAC.
Wow (slaps forehead) - very good catch. That's the whole reason the
immediate NOTIFY
in SIP Events exists.

The consequences of that are going to require some time to think through.


>
>
>> With the typical use of REFER specified to date (transfer), the refer
>> will have
>> a Target-Dialog header field and will likely be accepted at only one of the
>> places it might have forked to.
>>
>> RjS
> Regards,
> Shinji

_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email