Re: [sipcore] More comments regarding draft-ietf-sipcore-sip-push-08 - Pull request

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 19 March 2018 11:55 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 5A01212741D for <sipcore@ietfa.amsl.com>; Mon, 19 Mar 2018 04:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level:
X-Spam-Status: No, score=-4.32 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 pTPp5jcjCp_o for <sipcore@ietfa.amsl.com>; Mon, 19 Mar 2018 04:55:18 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 1488C124234 for <sipcore@ietf.org>; Mon, 19 Mar 2018 04:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1521460516; 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=kU1EcmlaWu9wzaHzPKreYhMZuE5jHEsxOI9YWouDMpA=; b=ByPwJMRgeqD/AZM5ehtWP1mOYO1lN/DNeIBbRg1Nj0yBnc07/rNswWy8Gt/9a9Cs 8zHbuNbyl+8FTpt8GUS1PgoIDrycBCg+GkMZdGQbjoGGzbrX+5C5c+k2Q0sV3DTB 0Ey2tlgSYPY7ThZipshUQx5RGiIrxc1jhbcYx0D6xQc=;
X-AuditID: c1b4fb25-681ff70000006222-65-5aafa524a3f3
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id BB.4B.25122.425AFAA5; Mon, 19 Mar 2018 12:55:16 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.172]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0382.000; Mon, 19 Mar 2018 12:55:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] More comments regarding draft-ietf-sipcore-sip-push-08 - Pull request
Thread-Index: AdO/eQ5I7FzMU/CISw2Amr+GohnAOw==
Date: Mon, 19 Mar 2018 11:55:15 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C20F1F8@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.164]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2J7lK7K0vVRBjdPSFl8/bGJzeLliTIH Jo/J+78yeyxZ8pMpgCmKyyYlNSezLLVI3y6BK+P31o3sBd+4K7o7XrA1MO7j7GLk5JAQMJH4 8uEbSxcjF4eQwGFGib3TWpghnCWMEitfNzN1MXJwsAlYSHT/0waJiwi0MUrcuNnIDNItLBAn ce7zBhYQW0QgXmLV4WmMELaexM4nG1hBbBYBVYmFU9+B2bwCvhJbn2wFq2EUEJP4fmoNE4jN LCAucevJfCaIiwQkluw5zwxhi0q8fPyPFcJWkjj7ZQobRL2OxILdn6BsbYllC18zQ8wXlDg5 8wnLBEahWUjGzkLSMgtJyywkLQsYWVYxihanFiflphsZ66UWZSYXF+fn6eWllmxiBIb3wS2/ VXcwXn7jeIhRgINRiYf3yMT1UUKsiWXFlbmHGCU4mJVEeJ9eWRclxJuSWFmVWpQfX1Sak1p8 iFGag0VJnHeOcHuUkEB6YklqdmpqQWoRTJaJg1OqgTFsiWCe3bzLt1i9Qm3u3olelqn9hEss 88OlzynaypsmxpxkYGiU1HmZs1P0jWjhNfV9Iiy3J6/0s9j+yyntuFLTEuvfDFcdp1ldPvNU z55LQcJ//berF4o6bIX+vjVocWiRPjnX0bv/Kt/8w7uXqOpEhmrVqs2fu+yVoP7B+24J0/rU Guo14pVYijMSDbWYi4oTAYxnkKprAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Q07a9feu8bdlmctytjBEhiMzDWw>
Subject: Re: [sipcore] More comments regarding draft-ietf-sipcore-sip-push-08 - Pull request
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Mar 2018 11:55:19 -0000

Hi,

I have created a pull request based on Dale's comments.

https://github.com/cdh4u/draft-sip-push/pull/16

However, below is one change I previously agreed to, but realized it goes against the original intention:

...

>> sec 4
>>
>>   In addition, if the response contains a Feature-Caps header field
>>   with a 'sip.vapid' feature-capability indicator, the UA can use the
>>   Voluntary Application Server Identification VAPID) mechanism
>>   [RFC8292] to restrict push notifications to the proxy (assuming that
>>   the PNS supports VAPID).
>>
>> I think you want to be more explict that 'sip.vapid' only indicates that the 
>> proxy supports VAPID.  Perhaps:
>>
>>   In addition, if the response contains a Feature-Caps header field
>>   with a 'sip.vapid' feature-capability indicator, the proxy supports
>>   use of the Voluntary Application Server Identification VAPID)
>>   mechanism [RFC8292] to restrict push notifications to the proxy.
>>   However, the use of VAPID also requires that the PNS supports
>>   VAPID, and determining that is the responsibility of the UA, not
>>   the proxy.

My original assumption was that the proxy will indicate support of VAPID if it knows that the PNS supports VAPID. That is indicated in "will use", but I guess that the text could be clarified.

"if the proxy supports the VAPID mechanism, knows that the mechanism is supported by the PNS, and the proxy will use the mechanism, the proxy MUST..."

Regards,

Christer