Re: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 26 July 2014 00:18 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 9D0151A0A8C for <sipcore@ietfa.amsl.com>; Fri, 25 Jul 2014 17:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 GF3G5vW9luRq for <sipcore@ietfa.amsl.com>; Fri, 25 Jul 2014 17:18:54 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ACD71A0657 for <sipcore@ietf.org>; Fri, 25 Jul 2014 17:18:52 -0700 (PDT)
X-AuditID: c1b4fb2d-f798a6d000000e9b-f0-53d2f3eae27f
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 0E.AB.03739.AE3F2D35; Sat, 26 Jul 2014 02:18:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.4]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0174.001; Sat, 26 Jul 2014 02:18:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Andrew Allen <aallen@blackberry.com>, Robert Sparks <rjsparks@nostrum.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt
Thread-Index: AQHPpTJ1yJBWKwyL3ESv/6dpj9kew5uwtw0AgADLijA=
Date: Sat, 26 Jul 2014 00:18:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D3D52FD@ESESSMB209.ericsson.se>
References: <20140721222239.14965.50656.idtracker@ietfa.amsl.com> <53CD92F2.9060403@nostrum.com> <BBF5DDFE515C3946BC18D733B20DAD233991173A@XMB122CNC.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233991173A@XMB122CNC.rim.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D3D52FDESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3RvfV50vBBjN26Vjcn7eV0eLanEY2 i68/NrE5MHvMaljL7rFkyU8mj1k7n7AEMEdx2aSk5mSWpRbp2yVwZfR9lC9YdJOx4traHywN jEcuM3YxcnJICJhI7PmxFMoWk7hwbz1bFyMXh5DAUUaJ+58uMkM4ixglVsw5yd7FyMHBJmAh 0f1PG8QUESiXuHrGHqRXWCBbYtKHG+wgtohAjsSlmQdYIWwrid0PW5lBbBYBVYnfd96A7eIV 8JU49baVEWL8QkaJeZO3MIEkOAU8JXrv9YIVMQId9P3UGrA4s4C4xK0n85kgDhWQWLLnPDOE LSrx8vE/VghbSaJxyRNWiPp8ie62d1DLBCVOznzCMoFRZBaSUbOQlM1CUjYL6DVmAU2J9bv0 IUoUJaZ0P2SHsDUkWufMZUcWX8DIvopRtDi1uDg33chYL7UoM7m4OD9PLy+1ZBMjMNYObvmt u4Nx9WvHQ4wCHIxKPLwKsy8FC7EmlhVX5h5ilOZgURLnXXRuXrCQQHpiSWp2ampBalF8UWlO avEhRiYOTqkGRvXlkRzRKR88fA2e+19OUHeTeyjyKkKvZgpLqtGj70cSXXycHIK/lC5mXTjB ecsj3gN893U8ikWn1NivW5rFcVtTVfbrsbOBXEL5SccuHHXQnFF2JPmBxS+p5jn8J9bfNJvy wcRwTm9yaNvuFo2CAnu+/WV6P49tW8dZoitzYt6dtcHrWroXKLEUZyQaajEXFScCAD/4xzaW AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/iljXGV08TfOlgbwuJalBrXwkuK4
Subject: Re: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt
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: Sat, 26 Jul 2014 00:18:56 -0000

Andrew,

We discussed your “other issue” in London, and it was clear that there were different opinions.

A way to solve that is to use Robert’s explicitsub mechanism. It allows the UAC to ensure that no implicit subscription will be created – without having to rely on media feature tags etc.

Regards,

Christer

From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Andrew Allen
Sent: 25 July 2014 17:05
To: Robert Sparks; sipcore@ietf.org
Subject: Re: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt

Robert

I have reviewed the new version and my comment is addressed now.

Another issue though. In a discussion taking place on another SDO list some people are still taking the view that if they have defined a feature at both the UAC and UAS with a media feature tag that lets the UAC know the UAS supports the feature and the feature defines that the UAC will use norefersub to request that a subscription is not created by REFER and the UAS will accept the norefersub and not create a subscription then it’s OK to then send the REFER on an existing dialog.

My view is this is a violation of protocol layering principles and could cause problems for implementations since SIP protocol layer functionality is now be coupled with the application semantics (i.e ths protocol layer has to know what the application behavior is going to be in order to know that no subscription will be created and therefore its OK to send the REFER on the pre-existing dialog).

We need the refer-explicit-subscription mechanism in order to ensure that no implicit subscription is created.

I welcome opinions on this?

Andrew

From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Robert Sparks
Sent: Monday, July 21, 2014 6:24 PM
To: sipcore@ietf.org<mailto:sipcore@ietf.org>
Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt

This fixed the missing slide 3 text.

RjS


-------- Original Message --------
Subject:

New Version Notification for draft-sparks-sipcore-refer-clarifications-02.txt

Date:

Mon, 21 Jul 2014 15:22:39 -0700

From:

internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>

To:

Robert Sparks <rjs@nostrum.com><mailto:rjs@nostrum.com>, "Adam Roach" <adam@nostrum.com><mailto:adam@nostrum.com>, Adam Roach <adam@nostrum.com><mailto:adam@nostrum.com>, "Robert Sparks" <RjS@nostrum.com><mailto:RjS@nostrum.com>



A new version of I-D, draft-sparks-sipcore-refer-clarifications-02.txt

has been successfully submitted by Robert Sparks and posted to the

IETF repository.



Name:          draft-sparks-sipcore-refer-clarifications

Revision:      02

Title:         Clarifications for the use of REFER with RFC6665

Document date: 2014-07-21

Group:         Individual Submission

Pages:         4

URL:            http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-02.txt

Status:         https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/

Htmlized:       http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-02

Diff:           http://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-refer-clarifications-02



Abstract:

   An accepted SIP REFER method creates an implicit subscription using

   the SIP-Specific Event Notification Framework.  That framework was

   revised by RFC6665.  This document highlights the implications of the

   requirement changes in RFC6665, and updates the definition of the

   REFER method, RFC3515, to clarify and disambiguate the impact of

   those changes.









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.



The IETF Secretariat