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

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Wed, 13 August 2014 15:03 UTC

Return-Path: <ivo.sedlacek@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 615B01A0324 for <sipcore@ietfa.amsl.com>; Wed, 13 Aug 2014 08:03: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, MANGLED_LIST=2.3, 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 uQ6xfe4l7R_D for <sipcore@ietfa.amsl.com>; Wed, 13 Aug 2014 08:03:21 -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 0794D1A0750 for <sipcore@ietf.org>; Wed, 13 Aug 2014 08:03:20 -0700 (PDT)
X-AuditID: c1b4fb2d-f793d6d000005356-60-53eb7e37725d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id C4.09.21334.73E7BE35; Wed, 13 Aug 2014 17:03:19 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.135]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0174.001; Wed, 13 Aug 2014 17:03:18 +0200
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: Robert Sparks <rjsparks@nostrum.com>, Andrew Allen <aallen@blackberry.com>, Adam Roach <adam@nostrum.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.txt
Thread-Index: AQHPtwKKcpmVO0fqZ0Se6torAo6gG5vOm0cg
Date: Wed, 13 Aug 2014 15:03:18 +0000
Message-ID: <39B5E4D390E9BD4890E2B310790061011271222B@ESESSMB301.ericsson.se>
References: <20140728221604.19558.73431.idtracker@ietfa.amsl.com> <53D6CC3D.4000005@nostrum.com> <39B5E4D390E9BD4890E2B310790061011270A76B@ESESSMB301.ericsson.se> <53D7BB5D.5010402@nostrum.com> <BBF5DDFE515C3946BC18D733B20DAD233991419A@XMB122CNC.rim.net> <53D92314.6040607@nostrum.com> <39B5E4D390E9BD4890E2B310790061011270B9E1@ESESSMB301.ericsson.se> <39B5E4D390E9BD4890E2B310790061011270BA18@ESESSMB301.ericsson.se> <39B5E4D390E9BD4890E2B310790061011270C376@ESESSMB301.ericsson.se> <53E3BD65.5080105@nostrum.com> <39B5E4D390E9BD4890E2B3107900610112711567@ESESSMB301.ericsson.se> <39B5E4D390E9BD4890E2B3107900610112711708@ESESSMB301.ericsson.se> <53EA2BCC.2080306@nostrum.com> <39B5E4D390E9BD4890E2B3107900610112711DE0@ESESSMB301.ericsson.se> <53EB757E.5000601@nostrum.com>
In-Reply-To: <53EB757E.5000601@nostrum.com>
Accept-Language: en-US, cs-CZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyM+Jvja553etgg0szJSzuz9vKaLHn7yJ2 i2tzGtksvv7YxObA4jGrYS27x5IlP5k8Zu18whLAHMVlk5Kak1mWWqRvl8CV0dhnU3BJsuJp 7xG2BsY/El2MnBwSAiYS01/OZIGwxSQu3FvP1sXIxSEkcJRRYtKziUwQzhJGiWtnfrCBVLEJ 6ElM3HKEFSQhIjCDUeLn/9eMIAlhgWyJlRt2gdkiAjkS/Z9b2CBsI4mTC56ArWARUJW48nsx K4jNK+Ar0fCzlRliwyI2icvn1oElOAW0Jc69nsYEYjMKyEpc/dMLNpRZQFzi1pP5TBC3Ckgs 2XOeGcIWlXj5+B8rhK0o0f60AaieA6heU2L9Ln2IVkWJKd0P2SH2CkqcnPmEZQKj6CwkU2ch dMxC0jELSccCRpZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIFRdHDLb90djKtfOx5iFOBg VOLhPRL9OliINbGsuDL3EKM0B4uSOO+ic/OChQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTDq HX9y5dvXqV+3+vYn7Hqwce/CRv0/ovZ7DIXdZjk5fnhhGCG0bPWfpdl75k1VvqJ3LUz7gvnv e5s7Sm1nzzq9Iy/V+OimTon/vAnMpyWM38+ZfXHVTo5lm62N9DcUHV/pId7jwTTN76L4zdks z1y6hYKce9g/aEwLO7f0QrqDWYNkwmShG/pNSizFGYmGWsxFxYkAp4KanYMCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/9lWffCzXzL78p5Y9L9sk0-p1qHg
Subject: Re: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.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: Wed, 13 Aug 2014 15:03:23 -0000

Hello,

> >> Your posited UA is going to reject out-of-dialog refers (at least in the context of a given dialog).
> >> Is it going to reject all refers?
> > If you meant REFERs related to dialogs created by the particular INVITE request, then:
> > - the UA rejects any out-of-dialog REFERs related to dialogs created 
> > by the particular INVITE request as stated in the question below; and
> > - the UA handles any in-dialog REFER received in a dialog created by the particular INVITE request according to RFC6665. The UA rejects any in-dialog REFER request that would result in an implicit subscription.
> Is this back to norefersub? Is your argument that you can accept the refer because you're the potential notifier and you know you won't take the path of norefersub that would create a subscription? If so, we may have a box around what we need to cover. If not, say more.

Could we focus on the next question (which seems to be the KEY question) and, after we solved it, return to this one?

> > If you also meant REFERs related to dialogs created by other INVITE request, then UA can accept or reject them within rules given by RFC6665.
> No, I was talking the the context of a given dialog.
> >
> >> If your UA did not provide a GRUU, it is (in the context of this dialog) not satisfying the requirements of 6665.
> >> ...
> >> The text you're proposing (if I've got it right) is trying to say "this UA is not using 6665 in the context of this dialog".
> > Can you please quote the RFC6665 requirement which the UA does not satisfy?
> The first sentence of 4.5.1.
> The clarification that Adam has signed up for well shine the light on that.
> If there is any potential for a UA to become a notifier for _any_ event package (not just refer, but think also dialog), it will need to provide a GRUU for any dialog it tries to enter.

RFC6665, section 4.5.1, 1st sentence states:   

	Notifiers MUST implement the Globally Routable User Agent URI (GRUU) extension defined in [RFC5627], and MUST use a GRUU as their local target.

Isn't notifier a role taken in subscription, applicable only for the dialog of the subscription?
The UA does not act as notifier in the dialogs created by the particular INVITE request. 
Thus, in my reading, the requirement does not apply for the particular INVITE request.
Or do I miss anything?

Kind regards

Ivo Sedlacek