IETF Logo Mail Archive

Re: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 28 September 2018 07:30 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB789130F40 for <sipcore@ietfa.amsl.com>; Fri, 28 Sep 2018 00:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.756
X-Spam-Level:
X-Spam-Status: No, score=-4.756 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 xmk7ZqcdHjxz for <sipcore@ietfa.amsl.com>; Fri, 28 Sep 2018 00:29:58 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46A0A130F30 for <sipcore@ietf.org>; Fri, 28 Sep 2018 00:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1538119795; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=S9W9vB8y2CVrBH9fJvt7gEMe42MnukkqR0q5Oxbo+mg=; b=cbPjixOvBcARQEwI7GNVzn4Vtc5g6OBK/JYdU4Uo4lbGw+3mfUhLGLfx4jELclc4 jDqQvKFpi8OT0mkVjtLXe+qoCPiuxPp2RNzJ4iXmVP10KXLs1gmNIuW9Y8tWs93V r+ydGA0Gci5LpgLbFAxmY7SXnhd3RpzZNWpY9oJYyHU=;
X-AuditID: c1b4fb2d-20bff700000055ff-5e-5badd873000b
Received: from ESESSMB504.ericsson.se (Unknown_Domain [153.88.183.122]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 77.1C.22015.378DDAB5; Fri, 28 Sep 2018 09:29:55 +0200 (CEST)
Received: from ESESBMB503.ericsson.se (153.88.183.170) by ESESSMB504.ericsson.se (153.88.183.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Fri, 28 Sep 2018 09:29:55 +0200
Received: from ESESBMB503.ericsson.se ([153.88.183.186]) by ESESBMB503.ericsson.se ([153.88.183.186]) with mapi id 15.01.1466.003; Fri, 28 Sep 2018 09:29:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>
CC: SIPCORE <sipcore@ietf.org>, Roman Shpount <roman@telurix.com>
Thread-Topic: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request
Thread-Index: AQHUUa7eTJ+hvSxii0mbhZOQZV2ROaT6rz+AgAA3Z4D///owYoAAG0xQ///mAQCAACfboIAAD62AgAWlEwCAA3HMgIAAI0MwgAEAzKCAAAFYwA==
Date: Fri, 28 Sep 2018 07:29:55 +0000
Message-ID: <6ecef7493a2347399ca49099e79b9c36@ericsson.com>
References: <61AD41E5-BD92-4E9D-86EF-181197208BC7@ericsson.com> <CAD5OKxsB=GnZ-9stkPCv5QS5VcCchCC1CbjtCUDsi4fQXae7kw@mail.gmail.com> <7907AB0C-A86C-42CA-9350-F4C70447B644@ericsson.com> <29A03E81-BF14-4F12-8B5B-8EC2C1BEBEC6@ericsson.com> <36d1e339ba9843bfb657c29c8f90e495@ericsson.com> <CAD5OKxvDT86VFoFzqM6J77udYNtfwCwOkADydwayf4ATySmtOQ@mail.gmail.com> <11c8e33a6bc1429c92d53632365939df@ericsson.com> <CAD5OKxu1NH9X+1rLvOyeN5xD8cxsr6QrFor_1fqheiLXJh9eBQ@mail.gmail.com> <125364D9-9574-407E-903C-39994CDE2971@ericsson.com> <724F81BC-E68F-4940-861C-904F82B0D2E2@vidyo.com> <03ed1101830a41258019ee3ad1dc3698@ericsson.com> <f3dfb6c4756e438cb6e050d89939ee8b@ericsson.com>
In-Reply-To: <f3dfb6c4756e438cb6e050d89939ee8b@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.153]
Content-Type: multipart/alternative; boundary="_000_6ecef7493a2347399ca49099e79b9c36ericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJIsWRmVeSWpSXmKPExsUyM2J7lW7xjbXRBqv75C32Lz7PbDHjwlRm i68/NrE5MHssWfKTyePWlAKPtmd32AOYo7hsUlJzMstSi/TtErgyri+9x1bw4QhjxZbnM9gb GK/sZ+xi5OSQEDCRuLpyKVsXIxeHkMBRRom7/XuYIZxvjBJH3p9iBakSEljGKHHuh08XIwcH m4CFRPc/bZCwiICGxMVnH9hAwswCjhKzdiuBtAoLNDNKTD/azAJR08Iosf6IHYRdJ9Exp4cN xGYRUJXYt3kZM4jNK2Atsfv7dBaIvRtZJfaduM7UxcjOwSlgI/E2GqSEUUBM4vupNUwgNrOA uMStJ/OZIO4XkFiy5zwzhC0q8fLxP1YIW0li77HrLBD1yRJHPv1mh1glKHFy5hOWCYyis5CM moWkbBaSsllgn2lKrN+lD1GiKDGl+yE7hK0h0TpnLjuy+AJG9lWMosWpxcW56UbGeqlFmcnF xfl5enmpJZsYgRF4cMtv3R2Mq187HmIU4GBU4uEVvLw2Wog1say4MvcQowQHs5II775qoBBv SmJlVWpRfnxRaU5q8SFGaQ4WJXFevVV7ooQE0hNLUrNTUwtSi2CyTBycUg2M5RIvTnVNeLVF 1Lvxp9e+JTo+cR9lOzdffa2/+pHicS+jUJa+vifZVbkOCS28E1NiHzT1zotdVPBd58KHFw+5 xHdP+itp2pj2gN2p9WXeHlueYqeAEI2nxcmFlrGCwRYXnUwUXy2/y+xzPjG07WPmzx+CM6dH OK0QuLPdzedF1HmLPxsDltUrsRRnJBpqMRcVJwIA60whVrwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/dfcRmTfBZz3RqL89PsVcwmTEfAE>
Subject: Re: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 28 Sep 2018 07:30:02 -0000

Ok, I got the abbreviation wrong – don’t know where the F came from :)



From: Christer Holmberg
Sent: 28 September 2018 10:23
To: Christer Holmberg <christer.holmberg@ericsson.com>; Jonathan Lennox <jonathan@vidyo.com>
Cc: SIPCORE <sipcore@ietf.org>; Roman Shpount <roman@telurix.com>
Subject: RE: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request

Would ‘PURF (Proxy Unique Registration Reference)’ be better?

Regards,

Christer

From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 27 September 2018 19:04
To: Jonathan Lennox <jonathan@vidyo.com<mailto:jonathan@vidyo.com>>
Cc: SIPCORE <sipcore@ietf.org<mailto:sipcore@ietf.org>>; Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Subject: Re: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request

Give me a better name and I’ll change it…

From: Jonathan Lennox [mailto:jonathan@vidyo.com]
Sent: 27 September 2018 18:57
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Cc: Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>; SIPCORE <sipcore@ietf.org<mailto:sipcore@ietf.org>>
Subject: Re: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request

I have no comment on the mechanism, but I find it unfortunate to have a new object called a “PURK” when the IETF is also working on a mechanism called “PERC”...

On Sep 25, 2018, at 4:21 AM, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

Are people (others than Roman) ok with this? I’d like to merge the PR and submit a new version of the draft.

Regards,

Christer

From: Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Date: Saturday 22 September 2018 at 00:08
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Cc: "sipcore@ietf.org<mailto:sipcore@ietf.org>" <sipcore@ietf.org<mailto:sipcore@ietf.org>>
Subject: Re: [sipcore] SIP Push with mid-dialog request triggered notifications: Way forward - The text using PURK - Pull request

On Fri, Sep 21, 2018 at 2:16 PM, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:

>This update looks good. The only remaining question is should proxy generated >new PURK on each binding refresh or periodically based on local policy. In RFC >5627, temp-gruu was generated on each binding refresh so that UA can obtain new >value on demand.

Since the frequency of binding refreshes can vary quite much, I don’t think we should mandate a new value for each refresh.


In this case, current update looks good to me.

Regards,
_____________
Roman Shpount


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

v2.23.0 | Report a Bug | By Email