From nobody Tue Jan 2 02:43:16 2018 Return-Path: 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 24FCB126BF7 for ; Tue, 2 Jan 2018 02:43:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.221 X-Spam-Level: X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 r1UoCV_5PJXF for ; Tue, 2 Jan 2018 02:43:13 -0800 (PST) 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 1D111126FDC for ; Tue, 2 Jan 2018 02:43:12 -0800 (PST) X-AuditID: c1b4fb2d-f179c9c000007932-13-5a4b623fdb97 Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 3D.40.31026.F326B4A5; Tue, 2 Jan 2018 11:43:11 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Tue, 2 Jan 2018 11:42:15 +0100 From: Christer Holmberg To: "Dale R. Worley" , "sipcore@ietf.org" Thread-Topic: [sipcore] Comments regarding sip-push registration - Editorial Comments & Pull Request Thread-Index: AQHTg7ZaXmQ0lcEMwk+ggervW3I6fQ== Date: Tue, 2 Jan 2018 10:42:14 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.19] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <462ED02BB70CCA4AA25E103C7363DBD6@ericsson.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyM2K7tK59kneUwf9tIhZff2xis3h5osyB yWPy/q/MHkuW/GQKYIrisklJzcksSy3St0vgynj3wb5gl27F2gvr2BoYbyp3MXJwSAiYSGw8 LtTFyMUhJHCYUeLZyW4mCGcxo0TLucNsIEVsAhYS3f+0uxg5OUQEgiQ2da5gBrGFBVIluvfd Z4eIp0lsOPGfBcLWk9j56CETiM0ioCJx/PkRsDivgLXEz1XL2EBsRgExie+n1oDVMAuIS9x6 Mh/MlhAQkFiy5zwzhC0q8fLxP1YQWxRo5oYTt9kh4ooS7U8bGCF69SRuTJ3CBmFbS8zZ+ANq prbEsoWvmSH2CkqcnPmEZQKjyCwk62YhaZ+FpH0WkvZZSNoXMLKuYhQtTi0uzk03MtZLLcpM Li7Oz9PLSy3ZxAiMkINbfuvuYFz92vEQowAHoxIPb3Kod5QQa2JZcWXuIUYJDmYlEd4eBaAQ b0piZVVqUX58UWlOavEhRmkOFiVx3pOevFFCAumJJanZqakFqUUwWSYOTqkGRtfY9a82GSyf Uxb7df6Tuuim1x9LT4TvnR5xyPHT98UsxqlMVfz88/lmiv3g//CsYWKtsPrKIpmnHF+MpL9v Fg3nZftbJFS1r8z3omCDwo3lFfntc3x8nIROMmTN0xI6pqyx5v16GyPJKR+0xPzKHHI4rz2u WhChfHBj1RpdsZPLLU+y5h86oMRSnJFoqMVcVJwIAEaJruGMAgAA Archived-At: Subject: Re: [sipcore] Comments regarding sip-push registration - Editorial Comments & Pull Request X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jan 2018 10:43:16 -0000 Hi, Below are my replies to Dale=B9s editorial comments. >* Editorial things > >The capitalization of the section titles is inconsistent. I=B9ll fix that. --- > When the SIP proxy receives a SIP request for a new session, or a > >s/session/dialog/ > > the SIP proxy will send a push request to the push notification > service used by the SIP UA, using the push resource ID associated > with the registered contact of the SIP UA, in order to trigger a push > notification towards the SIP UA. The SIP proxy will then forward the > SIP request towards the SIP UA using normal SIP routing procedures. > Once the SIP UA receives the push notification, it will be to receive > the SIP request, and to generate a SIP request (e.g., a SIP REGISTER) > itself. > >This description is incomplete, as it leaves out the step between the >first and second sentences, "the proxy waits to receive a >re-registration from the UA". The other descriptions of the process >for sending requests to the UA need to be checked for this as well. The proxy procedures section says that the proxy can forward the request once it receives the REGISTER request. I will add that to the Introduction too. --- >The abbreviation "pn-prid" is redundant, as it means "push >notification - push registration id". Perhaps reduce it to "pn-rid" >or "pn-id". I=B9d prefer to keep pn-prid, in order to associate it with =B3PRID". --- > The format of the PRID may vary depending on the PNS provider. The > PRID may be part of a URI that can be used to retrieve the address > and port of the PNS when sending push requests to the PNS. The PRID > may also be a token value, in which case the address and port of the > PNS needs to be provided using other means. > >It's not clear what "may be part of a URI" means, since just about any >string could be part of a URI. In any case, the format of the PRID is >outside the scope of this document; from our point of view, it's an >opaque string. The only real restriction is that it's a sequence of >Unicode characters and can be represented as a quoted-string (RFC 3261 >section 25.1). If the text is unclear, I can remove it, and simply keep the depending-on-the-PNS-provider sentence. > If the SIP UA at some point wants to stop the SIP proxy from sending > push requests, the SIP UA MUST send a SIP REGISTER request without > the pn-prid and pn-type URI parameters. > >It should be added, "or remove the registration". I=B9ll add that. --- > If the SIP UA expects to receive payload in the push notification, > the SIP UA MAY add a pn-enckey and a pn-encsec Contact header field > URI parameter, in order to allow encryption of the data using the > mechanism in [I-D.ietf-webpush-encryption]. The pn-enckey URI > parameter contains the public key, and the pn-encsec URI parameter > contains the authentication secret [I-D.ietf-webpush-encryption]. > >Need to mention that the format and use of such a payload is outside >the scope of this document; all we're doing here is defining the >parameters that make such payloads possible. I=B9ll add that. --- > In some cases the push notification provider can be retrieved from > the pn-prid URI parameter. In other cases the pn-type URI parameter > is used to identity the push notification provider. > >Exactly how you retrieve Apple Corp. from the parameters is unclear; I >know of no media-type for Apple Corp. >I think you mean, "Together, the pn-prid and pn-type parameters >suffice to identify which push notification provider is to be used and >how to direct it to notify the UA." I believe the text has been removed in version -02. --- > If the proxy is not able to contact the push notification provider, > or even determine which push notification provider to contact, it > SHOULD reject the SIP request. > >This sentence conflates two situations that should be handled >differently. If the redirector is unable to contact the push >notification provider, it must necessarily reject the request. (Do we >need to define a 4xx code to indicate that?) If the redirector is >unable to determine the push notification provider, it is able to >detect that during registration, and the REGISTER should have been >rejected. I will s/SHOULD/MUST, and remove the unable-to-determine-the-provider part. --- > It is currently suggested (see pull request in other e-mail) that > a proxy that receives a SIP REGISTER request with pn- parameters > for a PNS provider it does not support sends a 501 (Not > Implemented) response code. > > The question is whether it would be useful to define a > PNS-specific response code for this? E.g., 514 (Push Notification > Service Not Supported). In addition, we could define a feature > capability indicator that could be added to the response and list > the PNS providers supported by the proxy. > >And also, > > I have updated the pull request by adding a new SIP response code, > 555 (Push Notification Service Not Supported). > >Defining 514/555 like this doesn't really help, because the baseline >incompatibility case is when the registrar/redirector doesn't >understand the push notification mechanism at all, and happily >provides an ordinary registration when the UA wanted a >push-notification registration. See comments about an option-tag >above. The -02 version now contains text saying that the proxy will insert a feature capability indicator in the REGISTER 200 response. That will be an indicator to the UA that the feature is supported. Pull Request: https://github.com/cdh4u/draft-sip-push/pull/7 Regards, Christer From nobody Thu Jan 4 03:49:27 2018 Return-Path: X-Original-To: sipcore@ietf.org Delivered-To: sipcore@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 86BEE126DED; Thu, 4 Jan 2018 03:49:20 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipcore@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.68.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151506656050.18334.4996118513000389033@ietfa.amsl.com> Date: Thu, 04 Jan 2018 03:49:20 -0800 Archived-At: Subject: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-03.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 11:49:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core WG of the IETF. Title : Push Notification with the Session Initiation Protocol (SIP) Author : Christer Holmberg Filename : draft-ietf-sipcore-sip-push-03.txt Pages : 14 Date : 2018-01-04 Abstract: This document describes how push notification mechanisms can be used to wake up suspended Session Initiation Protocol (SIP) User Agents (UAs), in order to be able to receive and generate SIP requests. The document defines new SIP URI parameters, that can be used in a SIP REGISTER request to provide push notification information from the SIP User Agent (UA) to the SIP entity (realized as a SIP proxy in this document) that will send a push request to the push server in order to trigger a push notification towards the SIP UA. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipcore-sip-push-03 https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-sip-push-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-sip-push-03 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jan 4 03:51:01 2018 Return-Path: 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 1C5CB126CB6 for ; Thu, 4 Jan 2018 03:51:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 pEaQOy0Ct2tf for ; Thu, 4 Jan 2018 03:50:58 -0800 (PST) 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 B60C6124B18 for ; Thu, 4 Jan 2018 03:50:57 -0800 (PST) X-AuditID: c1b4fb25-473ff7000000341b-89-5a4e151ff06f Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id BA.12.13339.F151E4A5; Thu, 4 Jan 2018 12:50:55 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0352.000; Thu, 4 Jan 2018 12:50:55 +0100 From: Christer Holmberg To: "sipcore@ietf.org" Thread-Topic: Draft new version: SIP Push -03 Thread-Index: AQHThVJGyIc8ooX5WUm0OQV1lGFmVg== Date: Thu, 4 Jan 2018 11:50:54 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_D673E42C284D1christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7q668qF+UQcMqXYuvPzaxOTB6LFny kymAMYrLJiU1J7MstUjfLoErY8XNWUwFyzkqLq5Zz9rAuIi9i5GTQ0LAROLa3vUsXYxcHEIC hxklFqx5ygThLGaUuP/7BnMXIwcHm4CFRPc/bZAGEQFNieXftoI1CwtoSCz4dZwNIq4r8WPu LSaQchEBPYnP3xRBwiwCKhLHt3axgti8AtYSZxt+MoPYjAJiEt9PrWECsZkFxCVuPZnPBHGP gMSSPeeZIWxRiZeP/4H1igKN3HDiNjvIeAkBJYlpW9MgWhMk1n1cyAgxXlDi5MwnLBMYhWYh mToLSdksJGUQcQOJ9+fmM0PY2hLLFr6GsvUlNn45ywhhW0v82dvGhqxmASPHKkbR4tTipNx0 I2O91KLM5OLi/Dy9vNSSTYzAODm45bfqDsbLbxwPMQpwMCrx8PKx+EUJsSaWFVfmHmKU4GBW EuH1ee0bJcSbklhZlVqUH19UmpNafIhRmoNFSZz3pCdvlJBAemJJanZqakFqEUyWiYNTqoFR TqlAdi5LW5TdUnftrp9HTMN09xusr9PokHr1bO7f3Smz17zv/bJxzUTj7knic6/3OeS8fP3q 9IG7M+fFzFzaa8jxcMKmsmfHpD/8ePamhP+CFlP3qtZdqvYTKs2v2XwNnOB+3Wxn9q6S8i+H Cqq9uvrD96d+lOlriZ9zZiUz2x7by7ePMQt/UGIpzkg01GIuKk4EAEv/TvaPAgAA Archived-At: Subject: [sipcore] Draft new version: SIP Push -03 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 11:51:00 -0000 --_000_D673E42C284D1christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, Based on Dale=92s editorial comments, I=92ve submitted a new version (-03) = of SIP Push. Regards, Christer --_000_D673E42C284D1christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <2432021D5995E449BE14DB124B9BADCE@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

Based on Dale=92s editorial comments, I=92ve submitted a new version (= -03) of SIP Push.

Regards,

Christer
--_000_D673E42C284D1christerholmbergericssoncom_-- From nobody Thu Jan 4 03:54:03 2018 Return-Path: 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 6842A1271DF for ; Thu, 4 Jan 2018 03:54:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 kHkPs1LPOUEa for ; Thu, 4 Jan 2018 03:54:00 -0800 (PST) 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 0935C124B18 for ; Thu, 4 Jan 2018 03:53:59 -0800 (PST) X-AuditID: c1b4fb2d-f179c9c000007932-c3-5a4e15d65f3f Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id FC.A3.31026.6D51E4A5; Thu, 4 Jan 2018 12:53:58 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0352.000; Thu, 4 Jan 2018 12:53:57 +0100 From: Christer Holmberg To: Christer Holmberg , "sipcore@ietf.org" Thread-Topic: [sipcore] Draft new version: SIP Push -03 Thread-Index: AQHThVKzwwa5ILciH0KpqmNQhLvZFQ== Date: Thu, 4 Jan 2018 11:53:56 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.16] Content-Type: multipart/alternative; boundary="_000_D673E4A5284D4christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7me41Ub8og+3nxC2+/tjE5sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujCnf7rMXzJao+DN3N2MD40zRLkZODgkBE4l/D+eydTFycQgJ HGaU+PLxODuEs5hRYveJ/UAOBwebgIVE9z9tkAYRgXiJfQteMoLYwgJmEje7rjFDxM0l/nx/ zARh60k86G1iBbFZBFQkTk74xAgyhlfAWuJgAz9ImFFATOL7qTVg5cwC4hK3nsxngrhHQGLJ nvPMELaoxMvH/8DGiAKN3HDiNjtEXFFi59l2ZojeBIn/xw6D2bwCghInZz5hmcAoNAvJ2FlI ymYhKYOIG0i8PzefGcLWlli28DWUrS+x8ctZRgjbWmLb4adsyGoWMHKsYhQtTi0uzk03MtZL LcpMLi7Oz9PLSy3ZxAiMlINbfuvuYFz92vEQowAHoxIP7y8mvygh1sSy4srcQ4wSHMxKIrw+ r32jhHhTEiurUovy44tKc1KLDzFKc7AoifOe9OSNEhJITyxJzU5NLUgtgskycXBKNTCm/VSZ oPksoJD9TZPR5AV3THv8uFp2PDIq9LL55fR5PdfNmMKLsx7+1NHYMPXEhhd3mDkO3z4kIFlR ElNXqKbRNE8rpYH3g7zBcvvOx1PzK4/6rDni/Ga/O6vQ9XM69dscDT1YZlpH5gu48K6RuPlB 9bSl7xJVnuvdf8q1CkXeRe1ZXG6TkaDEUpyRaKjFXFScCACk0JV0kAIAAA== Archived-At: Subject: Re: [sipcore] Draft new version: SIP Push -03 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 11:54:02 -0000 --_000_D673E4A5284D4christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, Note that version =9603 does not contain any changes based on Paul=92s ABNF= comments, as I am still figuring out how to change it. Regards, Christer From: sipcore > o= n behalf of Christer Holmberg > Date: Thursday 4 January 2018 at 13:50 To: "sipcore@ietf.org" > Subject: [sipcore] Draft new version: SIP Push -03 Hi, Based on Dale=92s editorial comments, I=92ve submitted a new version (-03) = of SIP Push. Regards, Christer --_000_D673E4A5284D4christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <3621C407C642D44481FF93D9026427D4@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

Note that version =9603 does not contain any changes based on Paul=92s= ABNF comments, as I am still figuring out how to change it. 

Regards,

Christer

From: sipcore <sipcore-bounces@ietf.org> on behalf of Ch= rister Holmberg <chris= ter.holmberg@ericsson.com>
Date: Thursday 4 January 2018 at 13= :50
To: "sipcore@ietf.org" <sipcore@ietf.org>
Subject: [sipcore] Draft new versio= n: SIP Push -03

Hi,

Based on Dale=92s editorial comments, I=92ve submitted a new version (= -03) of SIP Push.

Regards,

Christer
 --_000_D673E4A5284D4christerholmbergericssoncom_-- From nobody Thu Jan 11 06:31:37 2018 Return-Path: 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 C475312EB93 for ; Thu, 11 Jan 2018 06:31:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 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 JqfLniikZAZw for ; Thu, 11 Jan 2018 06:31:33 -0800 (PST) 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 9C1C812EB8E for ; Thu, 11 Jan 2018 06:31:32 -0800 (PST) X-AuditID: c1b4fb2d-f179c9c000007932-13-5a577542dbfb Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F2.E5.31026.245775A5; Thu, 11 Jan 2018 15:31:30 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0352.000; Thu, 11 Jan 2018 15:31:28 +0100 From: Christer Holmberg To: Paul Kyzivat , "sipcore@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-02.txt - fci syntax Thread-Index: AQHTiujdqfyIp2B6T0K5vdbyrql1oA== Date: Thu, 11 Jan 2018 14:31:27 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.17] Content-Type: text/plain; charset="us-ascii" Content-ID: <986820038A32724AA2257AABF4488530@ericsson.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyM2K7t65TaXiUQfdkQ4sVGw6wWnz9sYnN gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4Mp4eHYVY8FqxYpXLQ/YGhinSHYxcnJICJhI vDj9kxnEFhI4zCgxYw1XFyMXkL2EUeL/q+msXYwcHGwCFhLd/7RBakQEAiWuLpnADBIWFgiR eNgQCmKKCIRKvPuoAVGhJ/Ho72dWEJtFQFVi/fl3jCA2r4C1RPPNr2A2o4CYxPdTa5hAbGYB cYlbT+YzQVwjILFkz3lmCFtU4uXjf2BzRIFmbjhxmx1klYSAosTyfjmIVh2JBbs/sUHY1hIz etcxQtjaEssWvmaGWCsocXLmE5YJjCKzkGybhaR9FpL2WUjaZyFpX8DIuopRtDi1uDg33chY L7UoM7m4OD9PLy+1ZBMjMD4Obvmtu4Nx9WvHQ4wCHIxKPLxGaeFRQqyJZcWVuYcYJTiYlUR4 FweGRQnxpiRWVqUW5ccXleakFh9ilOZgURLnPenJGyUkkJ5YkpqdmlqQWgSTZeLglGpg9H4m 8m3+H3WztZd+1cfFTZf+H9L1c8dVg2RVVrUeOdv2N5EM5huPTVt2bRnPYWWrjsXThHYbHDAR 9hN6Uiy+KiA2QVDZPoY3hZcjcV+W0RTtk0qzZgednNBz2PzJ+elhuwJc9SSiYz7YSO9eVrPp sd2HOFu+DfMvsN9KEuo466l0d0kWq0mREktxRqKhFnNRcSIAKeeJuYsCAAA= Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-02.txt - fci syntax X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 14:31:36 -0000 Hi Paul, What about the following syntax: pns-fc =3D "+sip.pns" EQUAL LDQUOT pns-list RDQUOT pns-list =3D pns *(COMMA pns) pns =3D tag-value ; tag-value as defined in RFC 3840 Regards, Christer On 21/12/17 17:07, "sipcore on behalf of Paul Kyzivat" wrote: >Christer, > >I just looked more closely at the ABNF for the indicator. It has some >problems. > > sip.pns =3D "<" pns-list ">" > pns-list =3D pns *(COMMA pns) > pns =3D pvalue > > ; pvalue as defined in RFC 3261 > >First, 'sip.pns' isn't a valid rulename. I presume you simply mean that >the name of this feature-capability indicator is "sip.pns", or "pns" in >the "sip" tree. This would be taken care of if you filled in a >registration template as specified in rfc6809. I can find no such >template. > >Next, according to rfc3840 the syntax of a feature param is: > > feature-param =3D enc-feature-tag [EQUAL LDQUOT (tag-value-list > / string-value ) RDQUOT] >... > tag-value-list =3D tag-value *("," tag-value) > tag-value =3D ["!"] (token-nobang / boolean / numeric) > token-nobang =3D 1*(alphanum / "-" / "." / "%" / "*" > / "_" / "+" / "`" / "'" / "~" ) > boolean =3D "TRUE" / "FALSE" > numeric =3D "#" numeric-relation number > numeric-relation =3D ">=3D" / "<=3D" / "=3D" / (number ":") > number =3D [ "+" / "-" ] 1*DIGIT ["." 0*DIGIT] > string-value =3D "<" *(qdtext-no-abkt / quoted-pair ) ">" > qdtext-no-abkt =3D LWS / %x21 / %x23-3B / %x3D > / %x3F-5B / %x5D-7E / UTF8-NONASCII > >Notably, the value of the feature-param is always enclosed in double >quotes. Also, I think your use of "<" and ">" means that you intend this >to be a string-value with a particular syntax, but possibly the >tag-value-list syntax would work for you. > > Thanks, > Paul > > >On 12/21/17 8:44 AM, internet-drafts@ietf.org wrote: >>=20 >> A New Internet-Draft is available from the on-line Internet-Drafts >>directories. >> This draft is a work item of the Session Initiation Protocol Core WG of >>the IETF. >>=20 >> Title : Push Notification with the Session >>Initiation Protocol (SIP) >> Author : Christer Holmberg >> Filename : draft-ietf-sipcore-sip-push-02.txt >> Pages : 14 >> Date : 2017-12-21 >>=20 >> Abstract: >> This document describes how push notification mechanisms can be used >> to wake up suspended Session Initiation Protocol (SIP) User Agents >> (UAs), in order to be able to receive and generate SIP requests. >>The >> document defines new SIP URI parameters, that can be used in a SIP >> REGISTER request to provide push notification information from the >> SIP User Agent (UA) to the SIP entity (realized as a SIP proxy in >> this document) that will send a push request to the push server in >> order to trigger a push notification towards the SIP UA. >>=20 >>=20 >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ >>=20 >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-ietf-sipcore-sip-push-02 >> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-sip-push-02 >>=20 >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-sip-push-02 >>=20 >>=20 >> 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. >>=20 >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >>=20 >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore >>=20 > >_______________________________________________ >sipcore mailing list >sipcore@ietf.org >https://www.ietf.org/mailman/listinfo/sipcore From nobody Thu Jan 11 13:13:10 2018 Return-Path: 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 A551E12E036 for ; Thu, 11 Jan 2018 13:13:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Kf_Ayih8q3Ns for ; Thu, 11 Jan 2018 13:13:06 -0800 (PST) Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id A709212426E for ; Thu, 11 Jan 2018 13:13:05 -0800 (PST) X-AuditID: 1207440d-98bff70000000c05-20-5a57d359785f Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 9E.F0.03077.953D75A5; Thu, 11 Jan 2018 16:12:58 -0500 (EST) Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w0BLCtMh026554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 11 Jan 2018 16:12:56 -0500 To: Christer Holmberg , "sipcore@ietf.org" References: From: Paul Kyzivat Message-ID: <574a0df0-fbb3-ec8b-8541-131fe4efc9e9@alum.mit.edu> Date: Thu, 11 Jan 2018 16:12:55 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDIsWRmVeSWpSXmKPExsUixO6iqBt1OTzK4FW7usWFmYcZLb7+2MTm wOTx6+tVNo8lS34yBTBFcdmkpOZklqUW6dslcGX82jmBueCuUsWD62eYGhhfSHYxcnJICJhI fLp1hrGLkYtDSGAHk0TXo3VsEM5DJom1k7ezdDFycAgLhEg8bAgFaRARSJPomdjPDhIWErCW +NbiBBJmE9CSmHPoPwuIzStgL/F5WTMTSAmLgKrEpj3VIGFRoM5Xz3YwQ5QISpyc+QSsnFPA RmLu+yNgNrOAmcS8zQ+ZIWxxiVtP5jNB2PIS29/OYZ7AyD8LSfssJC2zkLTMQtKygJFlFaNc Yk5prm5uYmZOcWqybnFyYl5eapGukV5uZoleakrpJkZIkPLuYPy/TuYQowAHoxIP74Pc8Cgh 1sSy4srcQ4ySHExKorx70oFCfEn5KZUZicUZ8UWlOanFhxglOJiVRHhruoFyvCmJlVWpRfkw KWkOFiVxXrUl6n5CAumJJanZqakFqUUwWRkODiUJXv1LQI2CRanpqRVpmTklCGkmDk6Q4TxA wy9cBBleXJCYW5yZDpE/xWjM0XLxSRszx40Xr9uYhVjy8vNSpcR5G0DGCYCUZpTmwU2DJZpX jOJAzwlDVPEAkxTcvFdAq5iAVp3fGAqyqiQRISXVwFhp+7+l8qE+w39jTeNJU901bqyZGm5V /WZ11MnT2a4BJdyHD1vPzXN6XOH97Wt04lFGg8epj2tbp06b+Wid9frVDzdOW+Bl0C0X/c1V eJdikegNYXW2V4KP1r1TrVzCtVa1UMB07bz3dtMzUvIjlZue3O0Sil/sXTCh7FpvZXzHNAHV 45d/timxFGckGmoxFxUnAgAy7Z1sDwMAAA== Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-02.txt - fci syntax X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2018 21:13:08 -0000 WFM On 1/11/18 9:31 AM, Christer Holmberg wrote: > Hi Paul, > > What about the following syntax: > > pns-fc = "+sip.pns" EQUAL LDQUOT pns-list RDQUOT > pns-list = pns *(COMMA pns) > pns = tag-value > > ; tag-value as defined in RFC 3840 > > > > Regards, > > Christer > > > On 21/12/17 17:07, "sipcore on behalf of Paul Kyzivat" > wrote: > >> Christer, >> >> I just looked more closely at the ABNF for the indicator. It has some >> problems. >> >> sip.pns = "<" pns-list ">" >> pns-list = pns *(COMMA pns) >> pns = pvalue >> >> ; pvalue as defined in RFC 3261 >> >> First, 'sip.pns' isn't a valid rulename. I presume you simply mean that >> the name of this feature-capability indicator is "sip.pns", or "pns" in >> the "sip" tree. This would be taken care of if you filled in a >> registration template as specified in rfc6809. I can find no such >> template. >> >> Next, according to rfc3840 the syntax of a feature param is: >> >> feature-param = enc-feature-tag [EQUAL LDQUOT (tag-value-list >> / string-value ) RDQUOT] >> ... >> tag-value-list = tag-value *("," tag-value) >> tag-value = ["!"] (token-nobang / boolean / numeric) >> token-nobang = 1*(alphanum / "-" / "." / "%" / "*" >> / "_" / "+" / "`" / "'" / "~" ) >> boolean = "TRUE" / "FALSE" >> numeric = "#" numeric-relation number >> numeric-relation = ">=" / "<=" / "=" / (number ":") >> number = [ "+" / "-" ] 1*DIGIT ["." 0*DIGIT] >> string-value = "<" *(qdtext-no-abkt / quoted-pair ) ">" >> qdtext-no-abkt = LWS / %x21 / %x23-3B / %x3D >> / %x3F-5B / %x5D-7E / UTF8-NONASCII >> >> Notably, the value of the feature-param is always enclosed in double >> quotes. Also, I think your use of "<" and ">" means that you intend this >> to be a string-value with a particular syntax, but possibly the >> tag-value-list syntax would work for you. >> >> Thanks, >> Paul >> >> >> On 12/21/17 8:44 AM, internet-drafts@ietf.org wrote: >>> >>> A New Internet-Draft is available from the on-line Internet-Drafts >>> directories. >>> This draft is a work item of the Session Initiation Protocol Core WG of >>> the IETF. >>> >>> Title : Push Notification with the Session >>> Initiation Protocol (SIP) >>> Author : Christer Holmberg >>> Filename : draft-ietf-sipcore-sip-push-02.txt >>> Pages : 14 >>> Date : 2017-12-21 >>> >>> Abstract: >>> This document describes how push notification mechanisms can be used >>> to wake up suspended Session Initiation Protocol (SIP) User Agents >>> (UAs), in order to be able to receive and generate SIP requests. >>> The >>> document defines new SIP URI parameters, that can be used in a SIP >>> REGISTER request to provide push notification information from the >>> SIP User Agent (UA) to the SIP entity (realized as a SIP proxy in >>> this document) that will send a push request to the push server in >>> order to trigger a push notification towards the SIP UA. >>> >>> >>> The IETF datatracker status page for this draft is: >>> https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ >>> >>> There are also htmlized versions available at: >>> https://tools.ietf.org/html/draft-ietf-sipcore-sip-push-02 >>> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-sip-push-02 >>> >>> A diff from the previous version is available at: >>> https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-sip-push-02 >>> >>> >>> 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. >>> >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>> >>> _______________________________________________ >>> sipcore mailing list >>> sipcore@ietf.org >>> https://www.ietf.org/mailman/listinfo/sipcore >>> >> >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> https://www.ietf.org/mailman/listinfo/sipcore > > From nobody Fri Jan 12 01:22:48 2018 Return-Path: X-Original-To: sipcore@ietf.org Delivered-To: sipcore@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB9412D77C; Fri, 12 Jan 2018 01:22:47 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipcore@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.68.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151574896753.18703.10591023833739476362@ietfa.amsl.com> Date: Fri, 12 Jan 2018 01:22:47 -0800 Archived-At: Subject: [sipcore] I-D Action: draft-ietf-sipcore-sip-push-04.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 09:22:47 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core WG of the IETF. Title : Push Notification with the Session Initiation Protocol (SIP) Author : Christer Holmberg Filename : draft-ietf-sipcore-sip-push-04.txt Pages : 15 Date : 2018-01-12 Abstract: This document describes how push notification mechanisms can be used to wake up suspended Session Initiation Protocol (SIP) User Agents (UAs), in order to be able to receive and generate SIP requests. The document defines new SIP URI parameters, that can be used in a SIP REGISTER request to provide push notification information from the SIP User Agent (UA) to the SIP entity (realized as a SIP proxy in this document) that will send a push request to the push server in order to trigger a push notification towards the SIP UA. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipcore-sip-push-04 https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-sip-push-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-sip-push-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jan 12 01:24:54 2018 Return-Path: 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 053D912DA6B for ; Fri, 12 Jan 2018 01:24:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 WoD9aePX81g4 for ; Fri, 12 Jan 2018 01:24:50 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 E9E2812DA68 for ; Fri, 12 Jan 2018 01:24:49 -0800 (PST) X-AuditID: c1b4fb3a-34dff700000037f2-df-5a587ee0f697 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 78.0A.14322.0EE785A5; Fri, 12 Jan 2018 10:24:48 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0352.000; Fri, 12 Jan 2018 10:24:47 +0100 From: Christer Holmberg To: "sipcore@ietf.org" Thread-Topic: Draft new version: sip-push-04 Thread-Index: AQHTi4cwhJZix9d/PEu1sJxRVPJ/BQ== Date: Fri, 12 Jan 2018 09:24:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.146] Content-Type: multipart/alternative; boundary="_000_D67E4E0328D94christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7ge6Duogog9nz+Cy+/tjE5sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujF9bJjEXrOaoaHrSydzAOI+9i5GTQ0LARGLtthuMXYxcHEIC hxkl/vy/xQbhLGGUeLDrKWsXIwcHm4CFRPc/bZAGEQFNieXftoI1CwuoS2x4tYAZpEREQEdi 0zo5iBI9iabLJ1hBbBYBVYkJM9YzgZTwClhLfJ8kDBJmFBCT+H5qDROIzSwgLnHryXwmiHME JJbsOc8MYYtKvHz8D2yMKNDIDSduQ52sJPFjwyUWiN4EiRvHIebwCghKnJz5hGUCo9AsJGNn ISmbhaQMIq4jsWD3JzYIW1ti2cLXzDD2mQOPoXqtJSZ8fsyCrGYBI8cqRtHi1OLi3HQjI73U oszk4uL8PL281JJNjMA4Objlt9UOxoPPHQ8xCnAwKvHw9qZFRAmxJpYVV+YeYpTgYFYS4WUp AgrxpiRWVqUW5ccXleakFh9ilOZgURLndUqziBISSE8sSc1OTS1ILYLJMnFwSjUwrlp5Otme pyJuE6fGbZE7x+ylvUUehV+c++UtyyS5lY2JbKJ2vJbn/25nmM3yn9fAp4yxZGnpnq3qM+y6 J+dn2C1SlaqbUm930ntx6IPND7bwsyX9KbBtnPB5330bnrUN/2911uoK6j5+P+XDQ8ZZTBmu pY/PpHuzb8vUDzr7XDyp78eVh0talViKMxINtZiLihMB0a6qlY8CAAA= Archived-At: Subject: [sipcore] Draft new version: sip-push-04 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 09:24:52 -0000 --_000_D67E4E0328D94christerholmbergericssoncom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I have submitted a new version (-04) of SIP Push, based on the syntax comme= nts provide by Paul. Regards, Christer --_000_D67E4E0328D94christerholmbergericssoncom_ Content-Type: text/html; charset="us-ascii" Content-ID: <829E9ED86FEE2E41B72CE5533F81AFEE@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

I have submitted a new version (-04) of SIP Push, based on the syntax = comments provide by Paul.

Regards,

Christer
--_000_D67E4E0328D94christerholmbergericssoncom_-- From nobody Fri Jan 19 05:19:18 2018 Return-Path: X-Original-To: sipcore@ietf.org Delivered-To: sipcore@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8121A126DEE; Fri, 19 Jan 2018 05:19:16 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sipcore@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.69.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <151636795648.26835.4923730256103699291@ietfa.amsl.com> Date: Fri, 19 Jan 2018 05:19:16 -0800 Archived-At: Subject: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 13:19:17 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core WG of the IETF. Title : ISUP Cause Location Parameter for the SIP Reason Header Field Author : Roland Jesske Filename : draft-ietf-sipcore-reason-q850-loc-02.txt Pages : 6 Date : 2018-01-19 Abstract: The SIP Reason header field is defined for carrying ISUP cause values as well as SIP response codes. Some services in SIP networks may need to know the ISUP location where the call was released in the PSTN network to correctly interpret the reason of release. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-reason-q850-loc/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sipcore-reason-q850-loc-02 https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-reason-q850-loc-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-reason-q850-loc-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Jan 19 07:56:34 2018 Return-Path: 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 E5BB91270B4 for ; Fri, 19 Jan 2018 07:56:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no 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 uirfKqCx7dWV for ; Fri, 19 Jan 2018 07:56:30 -0800 (PST) Received: from alum-mailsec-scanner-8.mit.edu (alum-mailsec-scanner-8.mit.edu [18.7.68.20]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5F4126E3A for ; Fri, 19 Jan 2018 07:56:30 -0800 (PST) X-AuditID: 12074414-ebbff70000000aea-d7-5a62152b1456 Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 37.5F.02794.B25126A5; Fri, 19 Jan 2018 10:56:27 -0500 (EST) Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w0JFuP0r020994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 19 Jan 2018 10:56:26 -0500 To: sipcore@ietf.org References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> From: Paul Kyzivat Message-ID: Date: Fri, 19 Jan 2018 10:56:24 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <151636795648.26835.4923730256103699291@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixO6iqKstmhRl0NkuYvH1xyY2B0aPJUt+ MgUwRnHZpKTmZJalFunbJXBlbHpzjbngCkvFtf1f2RsYzzF3MXJySAiYSFyd9Iixi5GLQ0hg B5PE5csHmSCcH0wSrcfngFUJC/hI/Du7CMwWERCReDb9HxuILSTgLDHt4V8wm01AS2LOof8s IDavgL3E1XUPwOIsAqoSB5r+M4HYogJpEq+e7WCGqBGUODnzCVg9p4CLxNRnS1hBbGYBM4l5 mx8yQ9jiEreezGeCsOUltr+dwzyBkX8WkvZZSFpmIWmZhaRlASPLKka5xJzSXN3cxMyc4tRk 3eLkxLy81CJdC73czBK91JTSTYyQsBTZwXjkpNwhRgEORiUeXoOviVFCrIllxZW5hxglOZiU RHnL/gKF+JLyUyozEosz4otKc1KLDzFKcDArifBqcydFCfGmJFZWpRblw6SkOViUxHm/LVb3 ExJITyxJzU5NLUgtgsnKcHAoSfCyiwA1ChalpqdWpGXmlCCkmTg4QYbzAA3/IQwyvLggMbc4 Mx0if4rRkqNt5ZM2Zo6WiyDyxovXbcxCLHn5ealS4rxCIEMFQBoySvPgZsLSzCtGcaAXhXmN QKp4gCkKbuoroIVMQAsn9iaCLCxJREhJNTDWq53tCj21+prl0capdXeyw/TWOPTd2fSu/f/Z fT7CQm9uhjRtvqj5GJgiZXMTul29Z6jOetH8O1b/6sIOI6NnGU/YWfds6DizTsKRySzGQPX1 m6DLUS1a/fkf+Den7T25uJXb3t3g75rl3wQWZB1uFWCy6H3QI9dtfiV8jnIR99TZKzreyiux FGckGmoxFxUnAgAmEpSCDgMAAA== Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 15:56:32 -0000 I question whether the following new text says exactly what you mean: The use of the location header is restricted to Q850 cause values in other cases the location, if present, MUST be silently discarted. I am guessing that you mean "ignored" rather than "discarded". As written it might me taken to mean that an intermediary should remove it. There are also some language issues in it. Perhaps the following: The use of the location header is restricted to Q850 cause values. In other cases the location, if present, MUST be silently ignored. Thanks, Paul From nobody Tue Jan 23 01:31:11 2018 Return-Path: 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 BEED3124E15 for ; Tue, 23 Jan 2018 01:31:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.329 X-Spam-Level: X-Spam-Status: No, score=-4.329 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de 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 DBHS4xpRWXxk for ; Tue, 23 Jan 2018 01:31:07 -0800 (PST) Received: from mailout33.telekom.de (MAILOUT33.telekom.de [194.25.225.145]) (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 A484A120725 for ; Tue, 23 Jan 2018 01:31:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1516699866; x=1548235866; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=jNruYfbqdyZWqh0/B8Xrg5RDljQmikD+5a25SySpubI=; b=tqvY2PlibuF7ayi7wKHZgUVuuHwFB8arIpNW6ap6GnaMIfVEukW2y3WF 0lisJKWDVT+v1EFjbaRveNGLsd64cXSoHYcy/B8i0WReJW7VKQ1cpWntc SeOSl+aGX7uyyhUL6X6W+1J+AwHFGBAvqE1ljUWXUR3H6czRBIfh5dU77 HvhFRRf7iKbo4sVcMk4aoa0jtuCMIImBmHJLzBEQeLDY1ACd6usshoFp1 pBchP7R2llFbqXhFOZ88ay9+JFaApfNKDQ3dqzrqJG7pq9I75nxbM9bVR iRsggTYZXy13LqYU4Eno7WLQr0SxhjCml5DR3HPH8oW+HaiGimzcICqn3 Q==; Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jan 2018 10:30:03 +0100 X-IronPort-AV: E=Sophos;i="5.46,400,1511823600"; d="scan'208";a="1463486963" Received: from he104850.emea1.cds.t-internal.com ([10.169.118.13]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES256-SHA; 23 Jan 2018 10:30:02 +0100 Received: from HE105872.EMEA1.cds.t-internal.com (10.169.118.69) by HE104850.emea1.cds.t-internal.com (10.169.118.13) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:30:01 +0100 Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105872.EMEA1.cds.t-internal.com (10.169.118.69) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 23 Jan 2018 10:30:02 +0100 Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.17) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:29:27 +0100 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.13) by FRAPR01MB0484.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Tue, 23 Jan 2018 09:30:01 +0000 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708]) by FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708%14]) with mapi id 15.20.0428.023; Tue, 23 Jan 2018 09:30:01 +0000 From: To: , Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt Thread-Index: AQHTkSg1SMxZ0XrB/ESpyKxyM34gKKN7WcwAgAXcwGA= Date: Tue, 23 Jan 2018 09:30:01 +0000 Message-ID: References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de; x-originating-ip: [164.19.3.217] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; FRAPR01MB0484; 7:hTtDyM5ssfnBEO22trrRCGyeAAWAiadoqqqcycsbzrR8ZVggbZ2pDj+i/TJxf7gIFFS4OOWnzIA6c3wWQnxRNEnLB53alzqda4cxHb+OKZf/hSPZXeITH3Rd3p67oJMlITU10SCJYSg+aCAPc7XgEzBVmqCkPkISpvvz1WN9zxFQjUqokT1sbKyRw/0W9JT8QoEdRjlHMmMYRS+jJAKbPWoUNucOKwFauw9s7YGCMnsqNC02QOZDpoxeKMjn12YB x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 349cb97c-ce3e-427e-960d-08d56243e082 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534145)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:FRAPR01MB0484; x-ms-traffictypediagnostic: FRAPR01MB0484: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041288)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:FRAPR01MB0484; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:FRAPR01MB0484; x-forefront-prvs: 05610E64EE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(39380400002)(396003)(346002)(39860400002)(376002)(366004)(189003)(199004)(5660300001)(66066001)(33656002)(2906002)(6116002)(68736007)(8936002)(5250100002)(53936002)(55016002)(316002)(8676002)(6306002)(9686003)(2501003)(110136005)(2171002)(74482002)(26005)(102836004)(59450400001)(966005)(72206003)(14454004)(86362001)(305945005)(52396003)(81166006)(76176011)(7696005)(345774005)(3846002)(106356001)(105586002)(3660700001)(3280700002)(81156014)(2950100002)(478600001)(230783001)(2900100001)(7736002)(97736004)(75402003)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0484; H:FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts) x-microsoft-antispam-message-info: Q8WGg8Gw2EgFYDz1VqdtUbOd9emNh+VBdcJZVxWqQZmSQNYbIC9U9qkomMCv4f4WEeQvqEnM76J1IvnifsyTRg== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 349cb97c-ce3e-427e-960d-08d56243e082 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2018 09:30:01.0684 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0484 X-OriginatorOrg: telekom.de Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 09:31:10 -0000 Hi Paul, thank you for your comment. I think you aspect is valid and so I will change it to your wording. This avoid that a manipulation must be done. Thank you and Best Regards Roland > -----Urspr=FCngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von Paul Kyziva= t > Gesendet: Freitag, 19. Januar 2018 16:56 > An: sipcore@ietf.org > Betreff: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.= txt >=20 > I question whether the following new text says exactly what you mean: >=20 > The use of the location header is restricted to Q850 cause values in > other cases the location, if present, MUST be silently discarted. >=20 > I am guessing that you mean "ignored" rather than "discarded". As written= it > might me taken to mean that an intermediary should remove it. >=20 > There are also some language issues in it. Perhaps the following: >=20 > The use of the location header is restricted to Q850 cause values. In > other cases the location, if present, MUST be silently ignored. >=20 > Thanks, > Paul >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Tue Jan 23 01:33:13 2018 Return-Path: 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 E0056126BFD for ; Tue, 23 Jan 2018 01:33:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.329 X-Spam-Level: X-Spam-Status: No, score=-4.329 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de 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 qqgoVccmQjuZ for ; Tue, 23 Jan 2018 01:33:09 -0800 (PST) Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (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 3F4B4124F57 for ; Tue, 23 Jan 2018 01:33:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1516699989; x=1548235989; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=rEMWuyO+8Zki2DBu7rAlB20vIwj3LWyMIv5PugK2s8U=; b=l6iX58vdX3RLVnPNxqK7EeiQt2tfKpVnTdvn3+Ij8dM+1qHjBGqaUL5a b8cC7t/Qk77bC68NXLaJ3XunbtSwKwCBEbvvDN1Ik48gjVKp7GC2erBjs uh9n0nUA4Zi47vNrGCCnIaNtj6aj4SiJiaG3pstjPkeWLZviqXpav/+O3 pJxXKXZ1YwL4K9G6e53YayrM7T4p4Clb0h4HqovzQcdql0rFYkYB6unyS bW40ytBMK7ijtMaNtfT6i8NstvPk0mAaG5LDFo7/LImyu4Yg9cl/FNqxi zM4JbheXb/wNZPWDUcXMqPayxLKMt5h3OLlctVDDeks51IHwCu5TogWlO A==; Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jan 2018 10:33:07 +0100 X-IronPort-AV: E=Sophos;i="5.46,400,1511823600"; d="scan'208";a="732168982" Received: from he104993.emea1.cds.t-internal.com ([10.169.119.36]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 23 Jan 2018 10:33:05 +0100 Received: from HE105660.EMEA1.cds.t-internal.com (10.169.119.56) by HE104993.emea1.cds.t-internal.com (10.169.119.36) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:33:05 +0100 Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE105660.EMEA1.cds.t-internal.com (10.169.119.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 23 Jan 2018 10:33:05 +0100 Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.23) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:32:24 +0100 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.13) by FRAPR01MB0484.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Tue, 23 Jan 2018 09:33:04 +0000 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708]) by FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708%14]) with mapi id 15.20.0428.023; Tue, 23 Jan 2018 09:33:04 +0000 From: To: Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt Thread-Index: AQHTkSg1SMxZ0XrB/ESpyKxyM34gKKOBNzOw Date: Tue, 23 Jan 2018 09:33:04 +0000 Message-ID: References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> In-Reply-To: <151636795648.26835.4923730256103699291@ietfa.amsl.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de; x-originating-ip: [164.19.3.217] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; FRAPR01MB0484; 7:oOA6gqjw9C1OQ3A0pl4bogP/Ddguja+Vx24V9+OzvrJjHs6SxlT9DKWn7i+bGFtwl3kk3jXU1awd/Ib1QEW5EsMoAxMf2iG077tPSEHIsBOtikfa/d1/aYXzTpwkdcFr72gNJq2IlrALvAr2bzze51SnobFzPPM3yPGsST6B1/gwUWmTSD/yx2HYEOAN/rKEuqlQQiMfOhfGJEXZim7iB4r826aXOFhfYd2tqIoW6zVgpMfyw604IQDMQSu2Jr4B x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 1002243e-4460-4303-6440-08d562444e09 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534164)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:FRAPR01MB0484; x-ms-traffictypediagnostic: FRAPR01MB0484: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041288)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:FRAPR01MB0484; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:FRAPR01MB0484; x-forefront-prvs: 05610E64EE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(396003)(346002)(39860400002)(376002)(366004)(189003)(199004)(377424004)(5660300001)(66066001)(33656002)(2906002)(6116002)(68736007)(8936002)(5640700003)(5250100002)(53936002)(55016002)(316002)(8676002)(6306002)(9686003)(2501003)(74482002)(26005)(102836004)(966005)(72206003)(14454004)(86362001)(305945005)(1730700003)(52396003)(81166006)(76176011)(7696005)(2351001)(3846002)(106356001)(105586002)(3660700001)(3280700002)(81156014)(6916009)(2950100002)(478600001)(230783001)(2900100001)(7736002)(97736004)(75402003); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0484; H:FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts) x-microsoft-antispam-message-info: sj+pB+uhQLjPrJ3M4jiMaH0XUlq9YBL3xYbE290jA2/zX0oCqNxr/LNExFM3UCpmMKi8TcstX2FrneYCO+sRmA== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 1002243e-4460-4303-6440-08d562444e09 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2018 09:33:04.8704 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0484 X-OriginatorOrg: telekom.de Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 09:33:12 -0000 Hi, I have now produced a further draft.=20 Paul has one comment which I will change. So the protocol from the last SIPCORE session indicates that the draft is w= aiting for a last call. So question is if we can proceed with a WGLC for this draft? Best Regards Roland > -----Urspr=FCngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von internet- > drafts@ietf.org > Gesendet: Freitag, 19. Januar 2018 14:19 > An: i-d-announce@ietf.org > Cc: sipcore@ietf.org > Betreff: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Session Initiation Protocol Core WG of t= he > IETF. >=20 > Title : ISUP Cause Location Parameter for the SIP Reaso= n Header > Field > Author : Roland Jesske > Filename : draft-ietf-sipcore-reason-q850-loc-02.txt > Pages : 6 > Date : 2018-01-19 >=20 > Abstract: > The SIP Reason header field is defined for carrying ISUP cause values > as well as SIP response codes. Some services in SIP networks may > need to know the ISUP location where the call was released in the > PSTN network to correctly interpret the reason of release. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sipcore-reason-q850-loc/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-sipcore-reason-q850-loc-02 > https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-reason-q850-loc-= 02 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-reason-q850-loc-02 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Tue Jan 23 01:42:17 2018 Return-Path: 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 22B0512DA05 for ; Tue, 23 Jan 2018 01:42:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.329 X-Spam-Level: X-Spam-Status: No, score=-4.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de 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 G2qXL4Ziu7mb for ; Tue, 23 Jan 2018 01:42:00 -0800 (PST) Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (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 A4FD61271DF for ; Tue, 23 Jan 2018 01:41:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1516700519; x=1548236519; h=from:to:subject:date:message-id:mime-version; bh=ukM7hU5WtlcLbpDQC7QMsdCo+g1K7VuzOxxyGiddOxI=; b=ZPvssBUBLPizbsOKw1Ka5eWfS8tv4MIyXSbZFQ5YHKhMpa1hVzKHCG6T bZHuCmsUqBa19x9MUEaRszHVsEZqXZ6RfFjnbtQAmGuGIsk4WCQmm9EZP riwh0ZJbWgPWBo2v6+Ddg5XyTzL8m/gzW90iaOH/McaHWNY/q0UAPugWM 4jUsRbKqU7Wo3IW0xFUnPXsebOUAYNkQHRwEEwCzNnJR1XSntacKDMNRk ihfJwn1PF93wykd4D+74vTHF7zsCAl+np3vfRpOWMBh6gAwc7+bWUAY2p l/Nupaqp+rqZ/AUzPYjsS2DTTtBr9S2RAkfztawRhlS5g9v0+4o/DVqJy w==; Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jan 2018 10:41:56 +0100 X-IronPort-AV: E=Sophos;i="5.46,400,1511823600"; d="scan'208,217";a="732178126" Received: from he105777.emea1.cds.t-internal.com ([10.169.118.37]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 23 Jan 2018 10:41:56 +0100 Received: from HE105778.EMEA1.cds.t-internal.com (10.169.118.38) by HE105777.emea1.cds.t-internal.com (10.169.118.37) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:41:56 +0100 Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105778.EMEA1.cds.t-internal.com (10.169.118.38) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 23 Jan 2018 10:41:56 +0100 Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.20) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 23 Jan 2018 10:41:21 +0100 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.13) by FRAPR01MB0482.DEUPRD01.PROD.OUTLOOK.DE (10.158.133.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Tue, 23 Jan 2018 09:41:55 +0000 Received: from FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708]) by FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE ([fe80::8100:ada2:e3e2:5708%14]) with mapi id 15.20.0428.023; Tue, 23 Jan 2018 09:41:54 +0000 From: To: Thread-Topic: draft-winterbottom-sipcore-locparam-02 Thread-Index: AdOULiHr+hU1s4GNQP+416y9YvrO1A== Date: Tue, 23 Jan 2018 09:41:54 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=R.Jesske@telekom.de; x-originating-ip: [164.19.3.217] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; FRAPR01MB0482; 7:Ljlv/pUzWMBj7Z9vDLoDlIaX1zyBKL3xTG3qzSuhL1bX/Zx7S883MRliMr9y6laIeKbge1A5AU2uU2APG+YsPYkB6XQaZQtTCKBD8Nm25gnREWd1cHGLkBLEV2N/p6Yd95q5ikixEfR2YAzjH726hRx/MnMwYhpMem8hGzA9m2MeOAc45yGiqOxOQlxXWk8LDSkpMDswX8V46kL9ZkwtLblGMkyl7WB8c8V1kRsQXpBmwR1DFRbCndlKmLw8zWb1 x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: b0a245f6-6f47-4a0a-220e-08d5624589fa x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534164)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:FRAPR01MB0482; x-ms-traffictypediagnostic: FRAPR01MB0482: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(3002001)(10201501046)(93006095)(93001095)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(6072148)(201708071742011); SRVR:FRAPR01MB0482; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:FRAPR01MB0482; x-forefront-prvs: 05610E64EE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(396003)(366004)(346002)(39380400002)(189003)(199004)(55016002)(105586002)(86362001)(1730700003)(81156014)(81166006)(66066001)(2351001)(413944005)(75402003)(106356001)(72206003)(2906002)(478600001)(8676002)(6116002)(3846002)(790700001)(5250100002)(230783001)(2501003)(6916009)(8936002)(2900100001)(558084003)(3660700001)(5660300001)(53936002)(97736004)(102836004)(3280700002)(26005)(68736007)(316002)(5640700003)(9686003)(54896002)(6306002)(7736002)(14454004)(74482002)(5630700001)(7696005)(52396003)(33656002)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0482; H:FRAPR01MB0483.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts) x-microsoft-antispam-message-info: mj08FKO7w9p7zI6uZkkUuGCcm/g4jhBYwOQJ2er2vdEVBkSg/8D0txmD2aaxX/CJT13Z7fju1R/hVxJtdnYWGA== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_FRAPR01MB04838C825720F768FDDB01F7F9E30FRAPR01MB0483DEUP_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: b0a245f6-6f47-4a0a-220e-08d5624589fa X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2018 09:41:54.8836 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0482 X-OriginatorOrg: telekom.de Archived-At: Subject: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 09:42:15 -0000 --_000_FRAPR01MB04838C825720F768FDDB01F7F9E30FRAPR01MB0483DEUP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, we had a slight discussion at the last IETF meeting on the draft draft-wint= erbottom-sipcore-locparam-02. As stated within the Minutes "log-param: will do call for adoption soon, on= the list". So I would like to ask if we can start the call for addition on the list? Best Regards Roland --_000_FRAPR01MB04838C825720F768FDDB01F7F9E30FRAPR01MB0483DEUP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

we had a slight discussion at the last IET=
F meeting on the draft draft-winterbottom-sipcore-locparam-02.
As stated within the Minutes “log-pa=
ram: will do call for adoption soon, on the list”.<=
/pre>

 


So I would like to ask if w=
e can start the call for addition on the list?


 

Best Regards


 

Roland

 


 


 
--_000_FRAPR01MB04838C825720F768FDDB01F7F9E30FRAPR01MB0483DEUP_-- From nobody Tue Jan 23 02:08:02 2018 Return-Path: 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 11B5E12DA6E for ; Tue, 23 Jan 2018 02:08:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.628 X-Spam-Level: X-Spam-Status: No, score=-2.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 DdmOEBNiVgz2 for ; Tue, 23 Jan 2018 02:07:59 -0800 (PST) Received: from orange.com (mta135.mail.business.static.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECF9D12DA6D for ; Tue, 23 Jan 2018 02:07:58 -0800 (PST) Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id C300B2115C; Tue, 23 Jan 2018 11:07:57 +0100 (CET) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.59]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id A09231A0076; Tue, 23 Jan 2018 11:07:57 +0100 (CET) Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c%19]) with mapi id 14.03.0382.000; Tue, 23 Jan 2018 11:07:57 +0100 From: To: "R.Jesske@telekom.de" , "sipcore@ietf.org" Thread-Topic: draft-winterbottom-sipcore-locparam-02 Thread-Index: AdOULiHr+hU1s4GNQP+416y9YvrO1AAA6sgw Date: Tue, 23 Jan 2018 10:07:57 +0000 Message-ID: <9020_1516702077_5A67097D_9020_40_1_8B970F90C584EA4E97D5BAAC9172DBB81D6D068C@OPEXCLILMA4.corporate.adroot.infra.ftgroup> References: In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.2] Content-Type: multipart/alternative; boundary="_000_8B970F90C584EA4E97D5BAAC9172DBB81D6D068COPEXCLILMA4corp_" MIME-Version: 1.0 Archived-At: Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 10:08:01 -0000 --_000_8B970F90C584EA4E97D5BAAC9172DBB81D6D068COPEXCLILMA4corp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I support having a call for adoption of this I-D. BR, Marianne De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de R.Jesske@telek= om.de Envoy=E9 : mardi 23 janvier 2018 10:42 =C0 : sipcore@ietf.org Objet : [sipcore] draft-winterbottom-sipcore-locparam-02 Dear all, we had a slight discussion at the last IETF meeting on the draft draft-wint= erbottom-sipcore-locparam-02. As stated within the Minutes "log-param: will do call for adoption soon, on= the list". So I would like to ask if we can start the call for addition on the list? Best Regards Roland ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_8B970F90C584EA4E97D5BAAC9172DBB81D6D068COPEXCLILMA4corp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

 

I support havi= ng a call for adoption of this I-D.

 

BR,=

Marianne<= /o:p>

 

De : sipcore [mailto:sipcore-bounces= @ietf.org] De la part de R.Jesske@telekom.de
Envoy=E9 : mardi 23 janvier 2018 10:42
=C0 : sipcore@ietf.org
Objet : [sipcore] draft-winterbottom-sipcore-locparam-02

 

Dear all,

we had a slight di=
scussion at the last IETF meeting on the draft draft-winterbottom-sipcore-l=
ocparam-02.
As stated within t=
he Minutes “log-param: will do call for adoption soon, on the list=
221;.
 <=
/span>
So I would like=
 to ask if we can start the call for addition on the list?
 
Best Regards
 
Roland
 
 

 

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
--_000_8B970F90C584EA4E97D5BAAC9172DBB81D6D068COPEXCLILMA4corp_-- From nobody Wed Jan 24 03:52:09 2018 Return-Path: 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 4B0AE12DA2C for ; Wed, 24 Jan 2018 03:52:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.62 X-Spam-Level: X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no 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 6xaLzaavwj54 for ; Wed, 24 Jan 2018 03:52:01 -0800 (PST) Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CD241200C5 for ; Wed, 24 Jan 2018 03:52:01 -0800 (PST) X-Spoof: Received: from smtp-pop.rim.net (HELO XCT104CNC.rim.net) ([10.65.161.204]) by mhs211cnc.rim.net with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Jan 2018 06:52:00 -0500 Received: from XCT116CNC.rim.net (10.65.161.216) by XCT104CNC.rim.net (10.65.161.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 24 Jan 2018 06:52:00 -0500 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT116CNC.rim.net ([::1]) with mapi id 14.03.0319.002; Wed, 24 Jan 2018 06:51:59 -0500 From: Andrew Allen To: "R.Jesske@telekom.de" , "sipcore@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt Thread-Index: AQHTkSge7/OTvuT51E+T7oUwo31oI6OBi9cAgAFlOjA= Date: Wed, 24 Jan 2018 11:51:58 +0000 Message-ID: References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> In-Reply-To: Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.65.160.249] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 11:52:08 -0000 I support this draft proceeding to WGLC -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of R.Jesske@telek= om.de Sent: Tuesday, January 23, 2018 4:33 AM To: sipcore@ietf.org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t Hi, I have now produced a further draft.=20 Paul has one comment which I will change. So the protocol from the last SIPCORE session indicates that the draft is w= aiting for a last call. So question is if we can proceed with a WGLC for this draft? Best Regards Roland > -----Urspr=FCngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von=20 > internet- drafts@ietf.org > Gesendet: Freitag, 19. Januar 2018 14:19 > An: i-d-announce@ietf.org > Cc: sipcore@ietf.org > Betreff: [sipcore] I-D Action:=20 > draft-ietf-sipcore-reason-q850-loc-02.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Session Initiation Protocol Core WG=20 > of the IETF. >=20 > Title : ISUP Cause Location Parameter for the SIP Reaso= n Header > Field > Author : Roland Jesske > Filename : draft-ietf-sipcore-reason-q850-loc-02.txt > Pages : 6 > Date : 2018-01-19 >=20 > Abstract: > The SIP Reason header field is defined for carrying ISUP cause values > as well as SIP response codes. Some services in SIP networks may > need to know the ISUP location where the call was released in the > PSTN network to correctly interpret the reason of release. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sipcore-reason-q850-loc/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-sipcore-reason-q850-loc-02 > https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-reason-q850-l > oc-02 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-reason-q850-loc-0 > 2 >=20 >=20 > Please note that it may take a couple of minutes from the time of=20 > submission until the htmlized version and diff are available at tools.iet= f.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 24 04:50:46 2018 Return-Path: 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 AD912120227 for ; Wed, 24 Jan 2018 04:50:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.621 X-Spam-Level: X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 uaDjSPOh6JZ6 for ; Wed, 24 Jan 2018 04:50:41 -0800 (PST) Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 C13541200E5 for ; Wed, 24 Jan 2018 04:50:41 -0800 (PST) Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id w0OCkb90041529; Wed, 24 Jan 2018 07:50:38 -0500 Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049458.ppops.net-00191d01. with ESMTP id 2fpt9087eu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 24 Jan 2018 07:50:38 -0500 Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w0OCobbI007157; Wed, 24 Jan 2018 07:50:38 -0500 Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id w0OCoRWT006976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 Jan 2018 07:50:31 -0500 Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [135.66.87.31]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Wed, 24 Jan 2018 12:50:21 GMT Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [127.0.0.1]) by zlp27127.vci.att.com (Service) with ESMTP id 4C52140002A8; Wed, 24 Jan 2018 12:50:21 +0000 (GMT) Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (unknown [130.9.129.149]) by zlp27127.vci.att.com (Service) with ESMTPS id 35BD940006FC; Wed, 24 Jan 2018 12:50:21 +0000 (GMT) Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.35]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0361.001; Wed, 24 Jan 2018 07:50:21 -0500 From: "DOLLY, MARTIN C" To: Andrew Allen , "R.Jesske@telekom.de" , "sipcore@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt Thread-Index: AQHTkSgi2Xwk112yGE6DIbmEkJY0WaOBi9cAgAG5JAD//7xjMA== Date: Wed, 24 Jan 2018 12:50:20 +0000 Message-ID: References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.10.131.24] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-24_06:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801240172 Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 12:50:45 -0000 AT&T supports=20 -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Andrew Allen Sent: Wednesday, January 24, 2018 6:52 AM To: R.Jesske@telekom.de; sipcore@ietf.org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t I support this draft proceeding to WGLC -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of R.Jesske@telek= om.de Sent: Tuesday, January 23, 2018 4:33 AM To: sipcore@ietf.org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t Hi, I have now produced a further draft.=20 Paul has one comment which I will change. So the protocol from the last SIPCORE session indicates that the draft is w= aiting for a last call. So question is if we can proceed with a WGLC for this draft? Best Regards Roland > -----Urspr=FCngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von > internet- drafts@ietf.org > Gesendet: Freitag, 19. Januar 2018 14:19 > An: i-d-announce@ietf.org > Cc: sipcore@ietf.org > Betreff: [sipcore] I-D Action:=20 > draft-ietf-sipcore-reason-q850-loc-02.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Session Initiation Protocol Core WG=20 > of the IETF. >=20 > Title : ISUP Cause Location Parameter for the SIP Reaso= n Header > Field > Author : Roland Jesske > Filename : draft-ietf-sipcore-reason-q850-loc-02.txt > Pages : 6 > Date : 2018-01-19 >=20 > Abstract: > The SIP Reason header field is defined for carrying ISUP cause values > as well as SIP response codes. Some services in SIP networks may > need to know the ISUP location where the call was released in the > PSTN network to correctly interpret the reason of release. >=20 >=20 > The IETF datatracker status page for this draft is: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. > org_doc_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc_&d=3DDwIFAw&c=3DLFYZ= - > o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhS= J > HdHMhh59f9N45MaCwQ&s=3DU6YIXUKiyZjqcKv65j6fklO98YB8YiKaKw8V4zj4omQ&e=3D >=20 > There are also htmlized versions available at: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_ht > ml_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D02&d=3DDwIFAw&c=3DLFYZ-= o > 9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJ= H > dHMhh59f9N45MaCwQ&s=3DUtqaXXuGsogKnZzd2irlF_fl8NWgoUY6E6ADTKDughk&e=3D > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. > org_doc_html_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dl&d=3DDwIFAw&c=3DLF= Y > Z-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiV= h > SJHdHMhh59f9N45MaCwQ&s=3DUSEtZvuh6Oj1pzBsF7gf_-3uoKY21UtneCxj7ZbQjrs&e=3D > oc-02 >=20 > A diff from the previous version is available at: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_rfcd > iff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D0&d=3DDwIFAw > &c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXq= YZF > vYAiVhSJHdHMhh59f9N45MaCwQ&s=3DHgcyUp4t9MpBTaHCV7pn9TMvAeGeLGGd3mGx08xiu > Vo&e=3D > 2 >=20 >=20 > Please note that it may take a couple of minutes from the time of=20 > submission until the htmlized version and diff are available at tools.iet= f.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > https://urldefense.proofpoint.com/v2/url?u=3Dftp-3A__ftp.ietf.org_intern > et-2Ddrafts_&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG= 0r2 > g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DLLzPs9oD2XI8t6-cSRO= 5 > soD2xKopKI3g2tZHGlpZeuQ&e=3D >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mail > man_listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQh= Cmp > w7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03= A > FeRZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D _______________________________________________ sipcore mailing list sipcore@ietf.org https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7= ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03AFeR= ZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D=20 _______________________________________________ sipcore mailing list sipcore@ietf.org https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7= ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03AFeR= ZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D=20 From nobody Wed Jan 24 04:52:00 2018 Return-Path: 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 3C6921200E5 for ; Wed, 24 Jan 2018 04:51:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.721 X-Spam-Level: X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=proximus.com header.b=NkB4Vv0v; dkim=pass (1024-bit key) header.d=proximuscorp.onmicrosoft.com header.b=eJvAcfrY 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 wQCmK6bMwGyh for ; Wed, 24 Jan 2018 04:51:54 -0800 (PST) Received: from mx16.belgacom.be (mx16.belgacom.be [195.13.15.236]) (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 5EA05120726 for ; Wed, 24 Jan 2018 04:51:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=proximus.com; i=@proximus.com; q=dns/txt; s=dkim; t=1516798314; x=1548334314; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=VsCX7W7QDYgtyHCejL8+xwBl8lksdr1fQgXhUIB03q8=; b=NkB4Vv0vJP7NYYDxCz57Xitq1OxAo/ODp8+UWtvp8lVUZqFE201x6nO+ y6hbxqAMJPFbkxN8fdt7gfj4jHpwveuMrkNPsc0qqh/6tZvgkvcmB1bdr FCAIkufB2L4XVn/xD2NZQJ/MH/cUz1mZ7KcLewsaKWVTG9auEM9LWn6tK Y=; X-IronPort-AV: E=Sophos;i="5.46,407,1511823600"; d="scan'208";a="48506594" Received: from a07584.bgc.net ([10.120.80.100]) by mx16.belgacom.be with ESMTP; 24 Jan 2018 13:51:51 +0100 X-TM-IMSS-Message-ID: Received: from A04027.BGC.NET ([10.121.135.24]) by proximus.com ([10.120.80.100]) with ESMTP (TREND IMSS SMTP Service 7.5) id b2eafd8d002ec3d5 ; Wed, 24 Jan 2018 13:51:50 +0100 Received: from A07622.bgc.net (10.26.29.230) by A04027.BGC.NET (10.121.135.24) with Microsoft SMTP Server (TLS) id 14.3.339.0; Wed, 24 Jan 2018 13:51:50 +0100 Received: from EUR01-HE1-obe.outbound.protection.outlook.com (10.26.31.158) by outlook.proximus.com (10.26.31.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.669.32; Wed, 24 Jan 2018 13:51:49 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ProximusCorp.onmicrosoft.com; s=selector1-proximus-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=0MSe8v9mdH6uTHn0w7lI5i9va4YSR15mk08GsKQiyuM=; b=eJvAcfrYG/p5rNLLDhrQRyHbruHERak9LTPscihn9gplmKTTAiW6EV7h+e78ZltSrut8zE7J7aWAVsd1Ynb3jQOlZTu84eBb996pxoOXhMx2Zacu56rS/SCmjwI3G0n2kqvrQNBJeV974Pm1YYh6f/9ve/isMQqwZkAM3If0uv8= Received: from HE1PR0801MB1884.eurprd08.prod.outlook.com (10.168.94.15) by HE1PR0801MB1882.eurprd08.prod.outlook.com (10.168.94.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Wed, 24 Jan 2018 12:51:48 +0000 Received: from HE1PR0801MB1884.eurprd08.prod.outlook.com ([fe80::d066:f28e:5ceb:6e0f]) by HE1PR0801MB1884.eurprd08.prod.outlook.com ([fe80::d066:f28e:5ceb:6e0f%13]) with mapi id 15.20.0428.019; Wed, 24 Jan 2018 12:51:48 +0000 From: "VAN GEEL Jan (SPC/CSP)" To: "sipcore@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt Thread-Index: AQHTkSge7/OTvuT51E+T7oUwo31oI6OBi9cAgAFlOjCAABBnAIAAAFFQ Date: Wed, 24 Jan 2018 12:51:48 +0000 Message-ID: References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=jan.van.geel@proximus.com; x-originating-ip: [195.238.28.19] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; HE1PR0801MB1882; 7:fPpgRhAE9CAiKUht8EKFhWSe/f96x6X8r8dAC7VquNbw8WYuoDfr4pWDsQmIHKadyQf9NUUK3Oe9Q4o0JB2hsqn2IqPj5XM8UPmgxALdiq1tlkXJbDOlBPAkJrmeA7OA3dnibCiMEyuaqqkWzqBqA1Mq5i9th1i6KuSn5xj3lh+/yHw4z6dvzX4Pkcr8/cofCZ4n5wkcD3tPLy0EUESiv5rtj9SAb1W+iUXhaMSIfya6yoXOfHscri831ReozeCF x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 18353148-0010-4c30-e441-08d563293b80 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:HE1PR0801MB1882; x-ms-traffictypediagnostic: HE1PR0801MB1882: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(10436049006162)(260130700054247)(174211160506117); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041288)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:HE1PR0801MB1882; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0801MB1882; x-forefront-prvs: 056297E276 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(366004)(346002)(376002)(39860400002)(39380400002)(199004)(189003)(377424004)(13464003)(86362001)(97736004)(966005)(5660300001)(106356001)(478600001)(229853002)(25786009)(53936002)(5250100002)(2900100001)(105586002)(6506007)(55016002)(26005)(6306002)(575784001)(2906002)(5640700003)(99286004)(9686003)(81166006)(6116002)(68736007)(2950100002)(316002)(6246003)(81156014)(76176011)(74316002)(93886005)(3660700001)(6436002)(7696005)(3846002)(7736002)(2501003)(14454004)(8936002)(1730700003)(8676002)(102836004)(53546011)(33656002)(1720100001)(230783001)(2351001)(66066001)(3280700002)(305945005)(6916009)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0801MB1882; H:HE1PR0801MB1884.eurprd08.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; x-microsoft-antispam-message-info: KRRjP4xjv1OWmg7zU3PEc9oQ3VK5hfw7Fzq02QVeTV5YT+mVyvb+/sAegtvg8bnz/MwUMQEcqa7K+MOaAH9x2w== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 18353148-0010-4c30-e441-08d563293b80 X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jan 2018 12:51:48.5123 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: e7ab81b2-1e84-4bf7-9dcb-b6fec01ed138 X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0801MB1882 X-OriginatorOrg: proximus.com X-TM-AS-MatchedID: 150567-139006-701960-701472-852497-106660-700564-701236-1 21155-700693-139010-852748-705386-701611-850298-704425-186035-703448-705388 -700839-703969-703399-703378-702807-702643-704173-863828-702131-139705-7068 17-709584-708196-106230-703267-702957-701249-703829-139703-700047-700607-13 9702-148004-148051-20016-20032-20043-42000-42003 X-TM-AS-MML: disable Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 12:51:59 -0000 +1 -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of DOLLY, MARTIN = C Sent: Wednesday 24 January 2018 13:50 To: Andrew Allen ; R.Jesske@telekom.de; sipcore@ietf= .org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t AT&T supports -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Andrew Allen Sent: Wednesday, January 24, 2018 6:52 AM To: R.Jesske@telekom.de; sipcore@ietf.org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t I support this draft proceeding to WGLC -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of R.Jesske@telek= om.de Sent: Tuesday, January 23, 2018 4:33 AM To: sipcore@ietf.org Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.tx= t Hi, I have now produced a further draft. Paul has one comment which I will change. So the protocol from the last SIPCORE session indicates that the draft is w= aiting for a last call. So question is if we can proceed with a WGLC for this draft? Best Regards Roland > -----Urspr=FCngliche Nachricht----- > Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von > internet- drafts@ietf.org > Gesendet: Freitag, 19. Januar 2018 14:19 > An: i-d-announce@ietf.org > Cc: sipcore@ietf.org > Betreff: [sipcore] I-D Action: > draft-ietf-sipcore-reason-q850-loc-02.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Session Initiation Protocol Core WG > of the IETF. > > Title : ISUP Cause Location Parameter for the SIP Reaso= n Header > Field > Author : Roland Jesske > Filename : draft-ietf-sipcore-reason-q850-loc-02.txt > Pages : 6 > Date : 2018-01-19 > > Abstract: > The SIP Reason header field is defined for carrying ISUP cause values > as well as SIP response codes. Some services in SIP networks may > need to know the ISUP location where the call was released in the > PSTN network to correctly interpret the reason of release. > > > The IETF datatracker status page for this draft is: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. > org_doc_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc_&d=3DDwIFAw&c=3DLFYZ= - > o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhS= J > HdHMhh59f9N45MaCwQ&s=3DU6YIXUKiyZjqcKv65j6fklO98YB8YiKaKw8V4zj4omQ&e=3D > > There are also htmlized versions available at: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_ht > ml_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D02&d=3DDwIFAw&c=3DLFYZ-= o > 9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJ= H > dHMhh59f9N45MaCwQ&s=3DUtqaXXuGsogKnZzd2irlF_fl8NWgoUY6E6ADTKDughk&e=3D > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. > org_doc_html_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dl&d=3DDwIFAw&c=3DLF= Y > Z-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiV= h > SJHdHMhh59f9N45MaCwQ&s=3DUSEtZvuh6Oj1pzBsF7gf_-3uoKY21UtneCxj7ZbQjrs&e=3D > oc-02 > > A diff from the previous version is available at: > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_rfcd > iff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D0&d=3DDwIFAw > &c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXq= YZF > vYAiVhSJHdHMhh59f9N45MaCwQ&s=3DHgcyUp4t9MpBTaHCV7pn9TMvAeGeLGGd3mGx08xiu > Vo&e=3D > 2 > > > 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.iet= f.org. > > Internet-Drafts are also available by anonymous FTP at: > https://urldefense.proofpoint.com/v2/url?u=3Dftp-3A__ftp.ietf.org_intern > et-2Ddrafts_&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG= 0r2 > g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DLLzPs9oD2XI8t6-cSRO= 5 > soD2xKopKI3g2tZHGlpZeuQ&e=3D > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mail > man_listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQh= Cmp > w7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03= A > FeRZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D _______________________________________________ sipcore mailing list sipcore@ietf.org https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7= ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03AFeR= ZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D _______________________________________________ sipcore mailing list sipcore@ietf.org https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7= ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03AFeR= ZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore ________________________________ ***** Disclaimer ***** http://www.proximus.be/maildisclaimer From nobody Wed Jan 24 06:18:17 2018 Return-Path: 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 4A5A31243FE for ; Wed, 24 Jan 2018 06:18:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.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 7e64fZwy9PND for ; Wed, 24 Jan 2018 06:18:13 -0800 (PST) Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4681912422F for ; Wed, 24 Jan 2018 06:18:13 -0800 (PST) Received: by mail-qt0-x231.google.com with SMTP id l20so10585870qtj.11 for ; Wed, 24 Jan 2018 06:18:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kAHonxUMnz9YWxpCFBR0zGNdNSL9dDNwz5nid7PRkHw=; b=rCX4JH7nNbpecESiwFwMr4L0lGd9Cf69NPh1VmSukLNAEbTC7YF8Tim+cyFKKmKbFU WBsYXBz4yXuSSWncorhkLM7gE/No7W7KY2la6jQw2RjEWSD9qh5hkEyHv9ChQSDwDy0o Rd6poaStZpCTzi6rvJ8HAfBkZjCdac0cKnbw6pq3QEFUBn7F0nArcll/L5nI2el5c0fG 4oJdw2c28Ip9uo4U3Pvbx+11HAp6v+MWC+OoYN9y1d3stDFPTG4JfHF6QJbiku6nzZdS xkKwu+GwbJW3GPKpb5JzFA80/9qZLcrRmFq9ScrIQ1pZoHXd0H4UjOwJi/hOPlJZc1RJ pAyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kAHonxUMnz9YWxpCFBR0zGNdNSL9dDNwz5nid7PRkHw=; b=IpAndXBwytnH90o7Poa6eA6AJ3pWC1gsz3NNN3lumYXkPlU3B2LK+EfWcLVYIVC31g 8LMV1XUVVUeuZof4GmGfDCsAMtjTEBkm8oGSN9NAsmktWwYeOQQUh0Z7DwgYeZoepNRl AZfUViScZMKPPPm8o1rGyP0dMWdwXkTxFbH+fb/8MA1otGH6Ds1z6oNeaRLU/zL+yj/o kdXtZ8Y4IBGm1MpT0oXyMAYr4aNzSw2/BLaU5tI4hwiwT+2eLYgYa2KPW9xRqUC0med0 x+07SXnFdkLxVD3YOXsca0KKQ8rZHPKe8+q/52vQSl18EF6TCnTuYsPsb65dBWgCbCfk E0gw== X-Gm-Message-State: AKwxyte3btbWVMByDwU4DA4bKvVtxVh1QZ5/wvl/r8dP00Xt/G8eUZrc K2kf3HT5k0BfkYoEJK/e6BazZA== X-Google-Smtp-Source: AH8x226BgDKcEqzzltCxhXcqb6mBSVP7YuXGQ86J9xA8lQ+2kFvNeHPvjFOWqy7q4Asa0/5lSt8e+g== X-Received: by 10.55.76.133 with SMTP id z127mr9514760qka.318.1516803492309; Wed, 24 Jan 2018 06:18:12 -0800 (PST) Received: from [10.33.193.0] (neustar-sthide-nat1.neustar.biz. [156.154.81.54]) by smtp.gmail.com with ESMTPSA id d201sm278606qke.69.2018.01.24.06.18.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 06:18:10 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Brian Rosen In-Reply-To: Date: Wed, 24 Jan 2018 09:18:08 -0500 Cc: "sipcore@ietf.org" Content-Transfer-Encoding: quoted-printable Message-Id: <9096E9C1-CCE1-45E4-BC1F-9E864E8C682F@brianrosen.net> References: <151636795648.26835.4923730256103699291@ietfa.amsl.com> To: "VAN GEEL Jan (SPC/CSP)" X-Mailer: Apple Mail (2.3273) Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2018 14:18:16 -0000 chairs are working on a WGLC schedule. We will announce very soon. This draft will be on it. Brian > On Jan 24, 2018, at 7:51 AM, VAN GEEL Jan (SPC/CSP) = wrote: >=20 >=20 > +1 >=20 > -----Original Message----- > From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of DOLLY, = MARTIN C > Sent: Wednesday 24 January 2018 13:50 > To: Andrew Allen ; R.Jesske@telekom.de; = sipcore@ietf.org > Subject: Re: [sipcore] I-D Action: = draft-ietf-sipcore-reason-q850-loc-02.txt >=20 > AT&T supports >=20 > -----Original Message----- > From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Andrew = Allen > Sent: Wednesday, January 24, 2018 6:52 AM > To: R.Jesske@telekom.de; sipcore@ietf.org > Subject: Re: [sipcore] I-D Action: = draft-ietf-sipcore-reason-q850-loc-02.txt >=20 > I support this draft proceeding to WGLC >=20 > -----Original Message----- > From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of = R.Jesske@telekom.de > Sent: Tuesday, January 23, 2018 4:33 AM > To: sipcore@ietf.org > Subject: Re: [sipcore] I-D Action: = draft-ietf-sipcore-reason-q850-loc-02.txt >=20 > Hi, > I have now produced a further draft. > Paul has one comment which I will change. > So the protocol from the last SIPCORE session indicates that the draft = is waiting for a last call. > So question is if we can proceed with a WGLC for this draft? >=20 > Best Regards >=20 > Roland >=20 >> -----Urspr=C3=BCngliche Nachricht----- >> Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von >> internet- drafts@ietf.org >> Gesendet: Freitag, 19. Januar 2018 14:19 >> An: i-d-announce@ietf.org >> Cc: sipcore@ietf.org >> Betreff: [sipcore] I-D Action: >> draft-ietf-sipcore-reason-q850-loc-02.txt >>=20 >>=20 >> A New Internet-Draft is available from the on-line Internet-Drafts = directories. >> This draft is a work item of the Session Initiation Protocol Core WG >> of the IETF. >>=20 >> Title : ISUP Cause Location Parameter for the SIP = Reason Header >> Field >> Author : Roland Jesske >> Filename : draft-ietf-sipcore-reason-q850-loc-02.txt >> Pages : 6 >> Date : 2018-01-19 >>=20 >> Abstract: >> The SIP Reason header field is defined for carrying ISUP cause = values >> as well as SIP response codes. Some services in SIP networks may >> need to know the ISUP location where the call was released in the >> PSTN network to correctly interpret the reason of release. >>=20 >>=20 >> The IETF datatracker status page for this draft is: >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. >> = org_doc_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc_&d=3DDwIFAw&c=3DLFYZ-= >> = o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJ= >> HdHMhh59f9N45MaCwQ&s=3DU6YIXUKiyZjqcKv65j6fklO98YB8YiKaKw8V4zj4omQ&e=3D= >>=20 >> There are also htmlized versions available at: >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_ht >> = ml_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D02&d=3DDwIFAw&c=3DLFYZ-o= >> = 9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJH= >> dHMhh59f9N45MaCwQ&s=3DUtqaXXuGsogKnZzd2irlF_fl8NWgoUY6E6ADTKDughk&e=3D >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf. >> = org_doc_html_draft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dl&d=3DDwIFAw&c=3DLFY= >> = Z-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVh= >> SJHdHMhh59f9N45MaCwQ&s=3DUSEtZvuh6Oj1pzBsF7gf_-3uoKY21UtneCxj7ZbQjrs&e=3D= >> oc-02 >>=20 >> A diff from the previous version is available at: >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_rfcd >> = iff-3Furl2-3Ddraft-2Dietf-2Dsipcore-2Dreason-2Dq850-2Dloc-2D0&d=3DDwIFAw >> = &c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0r2g&m=3D871Owu0oVsHqXqY= ZF >> = vYAiVhSJHdHMhh59f9N45MaCwQ&s=3DHgcyUp4t9MpBTaHCV7pn9TMvAeGeLGGd3mGx08xiu >> Vo&e=3D >> 2 >>=20 >>=20 >> 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. >>=20 >> Internet-Drafts are also available by anonymous FTP at: >> = https://urldefense.proofpoint.com/v2/url?u=3Dftp-3A__ftp.ietf.org_intern >> = et-2Ddrafts_&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmpw7ItG0= r2 >> = g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DLLzPs9oD2XI8t6-cSRO5= >> soD2xKopKI3g2tZHGlpZeuQ&e=3D >>=20 >> _______________________________________________ >> sipcore mailing list >> sipcore@ietf.org >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mail >> = man_listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhC= mp >> = w7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03A= >> FeRZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailma= n_listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmp= w7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03A= FeRZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailma= n_listinfo_sipcore&d=3DDwIFAw&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DG9v8uCSSQhCmp= w7ItG0r2g&m=3D871Owu0oVsHqXqYZFvYAiVhSJHdHMhh59f9N45MaCwQ&s=3DdOBvpQbyf03A= FeRZC3dN0fFAPTAgVu0HmaQ581Du3yo&e=3D >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >=20 > ________________________________ >=20 > ***** Disclaimer ***** > http://www.proximus.be/maildisclaimer >=20 > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 24 23:35:07 2018 Return-Path: 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 7028112E055 for ; Wed, 24 Jan 2018 23:35:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.219 X-Spam-Level: X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 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 WzCYFQzpOhRA for ; Wed, 24 Jan 2018 23:35:03 -0800 (PST) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 1395812E042 for ; Wed, 24 Jan 2018 23:35:02 -0800 (PST) X-AuditID: c1b4fb30-d31ff70000006bc7-ff-5a6988a502d7 Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id B9.2F.27591.5A8896A5; Thu, 25 Jan 2018 08:35:01 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0352.000; Thu, 25 Jan 2018 08:35:00 +0100 From: Christer Holmberg To: "marianne.mohali@orange.com" , "R.Jesske@telekom.de" , "sipcore@ietf.org" Thread-Topic: [sipcore] draft-winterbottom-sipcore-locparam-02 Thread-Index: AQHTla8B+jaJyhtFYEadHQKxgCnOlg== Date: Thu, 25 Jan 2018 07:35:00 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.7.170905 x-originating-ip: [153.88.183.17] Content-Type: multipart/alternative; boundary="_000_D68F55CF29AF4christerholmbergericssoncom_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2K7se7Sjswog/YnIhbbmvcxWTTd6WKz +PpjE5sDs8eSJT+ZPFqenWTzaHupEMAcxWWTkpqTWZZapG+XwJWxZc49poKz0RXL77xgbWCc H9DFyMkhIWAiseHDXdYuRi4OIYHDjBI3T3exQDhLGCXm/17O3MXIwcEmYCHR/U8bJC4iMJVR 4sqqP6wg3cICthK7J75mAbFFBOwktq2ZDmXrScz49YkdxGYRUJV48HoKWD2vgLVE88kLTCA2 o4CYxPdTa8BsZgFxiVtP5jNBXCQgsWTPeWYIW1Ti5eN/YL2iQDM3nLjNDnKPhICixPJ+OYjW BImGd/3sEOMFJU7OfMIygVFoFpKps5CUzUJSBhE3kHh/bj4zhK0tsWzhayhbX2Ljl7OMELa1 xM2vnYzIahYwcqxiFC1OLU7KTTcy0kstykwuLs7P08tLLdnECIyog1t+G+xgfPnc8RCjAAej Eg/v3arMKCHWxLLiytxDjBIczEoivJfbM6KEeFMSK6tSi/Lji0pzUosPMUpzsCiJ85705I0S EkhPLEnNTk0tSC2CyTJxcEo1MHpzyZtkbTXQLeyQv595muXOrJenQ0+82RMZuOlo6KS3H8Nf Vfparm21OsTL/uRhkNx82S2Nj42SZhw32/rL9lxWQPC7ReJ1/uKrzOa8NnBfV6DXXLDkltLX shs+316ydh092sj3wW5P2+qEPO45c3W1j916INQ8f+vZRZqW38riPkSzfzi4fpESS3FGoqEW c1FxIgDDg9FgpAIAAA== Archived-At: Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 07:35:05 -0000 --_000_D68F55CF29AF4christerholmbergericssoncom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, +1. I support adoption, and would participate in the work by reviewing and = commenting. (Note, though, that I did already provide comments on -01, and we had some = discussions, but I haven=92t checked whether everything has been addressed = in =9602.) Regards, Christer From: sipcore > o= n behalf of "marianne.mohali@orange.com"= > Date: Tuesday 23 January 2018 at 12:07 To: "R.Jesske@telekom.de" >, "sipcore@ietf.org" <= sipcore@ietf.org> Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 Hi, I support having a call for adoption of this I-D. BR, Marianne De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de R.Jesske@telek= om.de Envoy=E9 : mardi 23 janvier 2018 10:42 =C0 : sipcore@ietf.org Objet : [sipcore] draft-winterbottom-sipcore-locparam-02 Dear all, we had a slight discussion at the last IETF meeting on the draft draft-wint= erbottom-sipcore-locparam-02. As stated within the Minutes =93log-param: will do call for adoption soon, = on the list=94. So I would like to ask if we can start the call for addition on the list? Best Regards Roland ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_D68F55CF29AF4christerholmbergericssoncom_ Content-Type: text/html; charset="Windows-1252" Content-ID: <4689F42C8B313A408112B0073E8478DF@ericsson.com> Content-Transfer-Encoding: quoted-printable
Hi,

+1. I support adoption, and would participate in the work by revie= wing and commenting.

(Note, though, that I did already provide comments on -01, and we had = some discussions, but I haven=92t checked whether everything has been addre= ssed in =9602.)

Regards,

Christer

From: sipcore <sipcore-bounces@ietf.org> on behalf of &q= uot;marianne.mohali@orange.co= m" <marianne.moha= li@orange.com>
Date: Tuesday 23 January 2018 at 12= :07
To: "R.Jesske@telekom.de" <R.Jesske@telekom.de>, "sipcore@ietf.org" <= sipcore@ietf.org>
Subject: Re: [sipcore] draft-winter= bottom-sipcore-locparam-02

Hi,

 

I support having a call for adopt= ion of this I-D.

 

BR,

Marianne

 

De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de R.Jesske@teleko= m.de
Envoy=E9 : mardi 23 janvier 2018 10:42
=C0 : sipcore@ietf.org<= br> Objet : [sipcore] draft-winterbottom-sipcore-locparam-02

 

Dear all,

we had a slight discussion at the last IETF meeting on the draft d=
raft-winterbottom-sipcore-locparam-02.
As stated within the Minutes =93log-param: will do call for adopti=
on soon, on the list=94.
 
So I would like to ask if we can start the call for addition on=
 the list?
 
Best Regards
 
Roland
 
 

 

______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
--_000_D68F55CF29AF4christerholmbergericssoncom_-- From nobody Thu Jan 25 01:19:37 2018 Return-Path: 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 55AD812E870 for ; Thu, 25 Jan 2018 01:19:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.328 X-Spam-Level: X-Spam-Status: No, score=-4.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de 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 xo7bbu8ip8bp for ; Thu, 25 Jan 2018 01:19:32 -0800 (PST) Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (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 BAF1412D868 for ; Thu, 25 Jan 2018 01:19:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1516871972; x=1548407972; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=csZ+354BNrUcVU1hcCvM+VOK4SppHvKoZjexBPIlT6s=; b=SGETfitYl64b0m6AJqNP21tpO2iS1kaxexhR7oyjoDtuWqf6jbfTjbd/ TjHBjDZz85q/WxDQzfJALIBRzUTGZlMAw4MJ/QSjKnR27Xz/Iat0Zt6Lc pYj+/MsaH6zkQJiIDy5CD4lWVShFM25rhMZRmbQtMpQ7F8LV0UjOPWLQl izht6vKnb785mLBmlp/nqOoh8nC+su2Tf8aDN+cKbRwMo4SJH3ldfHg5U biI1Wc9k8VxLCyT68cVQsATLpxqbvGNUnGs/14iGmoNhm75WHKOzrmfML DtJqFJzio6irvWU/9oWB5NHQRM5WyOQ4bAiFB2dMev9k1UPNsHwCfnUGw w==; Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2018 10:18:26 +0100 X-IronPort-AV: E=Sophos;i="5.46,411,1511823600"; d="scan'208,217";a="100897182" Received: from he105689.emea1.cds.t-internal.com ([10.169.119.67]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 25 Jan 2018 10:13:11 +0100 Received: from HE104993.EMEA1.cds.t-internal.com (10.169.119.36) by HE105689.emea1.cds.t-internal.com (10.169.119.67) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 25 Jan 2018 10:13:11 +0100 Received: from HE100181.emea1.cds.t-internal.com (10.171.40.15) by HE104993.EMEA1.cds.t-internal.com (10.169.119.36) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Thu, 25 Jan 2018 10:13:11 +0100 Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.20) by O365mail02.telekom.de (172.30.0.235) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 25 Jan 2018 10:12:29 +0100 Received: from FRAPR01MB0691.DEUPRD01.PROD.OUTLOOK.DE (10.158.134.140) by FRAPR01MB0691.DEUPRD01.PROD.OUTLOOK.DE (10.158.134.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.15; Thu, 25 Jan 2018 09:13:10 +0000 Received: from FRAPR01MB0691.DEUPRD01.PROD.OUTLOOK.DE ([fe80::49e8:bd9b:e51f:c686]) by FRAPR01MB0691.DEUPRD01.PROD.OUTLOOK.DE ([fe80::49e8:bd9b:e51f:c686%15]) with mapi id 15.20.0444.016; Thu, 25 Jan 2018 09:13:10 +0000 From: To: Thread-Topic: [sipcore] draft-winterbottom-sipcore-locparam-02 Thread-Index: AQHTla8B+jaJyhtFYEadHQKxgCnOlqOESrjQ Date: Thu, 25 Jan 2018 09:13:10 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=A.Seus@telekom.de; x-originating-ip: [164.19.3.121] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; FRAPR01MB0691; 7:gSGRSxcWHy5/2ZdpbQGP5UXyl79bDoBqQCtU6q0D+iDMkWlB/hH4ueMTBmVTEJ3lkK/y36JKsbKGpN/8+JI2TosPOo0ls1IwIa3wUHTulweOflWYj/SRUhGxdBGWFkV5MfrMKpnQ6T3Yqtaqagk1dOgGr/g04lbIQakP0HSockEg5tIJ8WhDNz/Dab3SNr5WZIez5e7OeiiAp2zhPOtHtJB7n3k9xgmamQohJPjGdUu1pidYrVnrDTA7RxaJG7G7 x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: 46adb9c2-fa2d-4678-ba2b-08d563d3db0a x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:FRAPR01MB0691; x-ms-traffictypediagnostic: FRAPR01MB0691: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(260130700054247)(18271650672692)(21748063052155); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(10201501046)(93006095)(93001095)(3002001)(6041288)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:FRAPR01MB0691; BCL:0; PCL:0; RULEID:; SRVR:FRAPR01MB0691; x-forefront-prvs: 0563F2E8B7 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39380400002)(396003)(376002)(39860400002)(346002)(199004)(189003)(5660300001)(6116002)(790700001)(2906002)(97736004)(3846002)(74482002)(2950100002)(6916009)(33656002)(81156014)(81166006)(8676002)(1730700003)(478600001)(8936002)(76176011)(5630700001)(53546011)(59450400001)(102836004)(52396003)(230783001)(75402003)(3660700001)(26005)(68736007)(72206003)(7696005)(3280700002)(7736002)(66066001)(413944005)(14454004)(2900100001)(105586002)(606006)(53936002)(316002)(5890100001)(6306002)(236005)(55016002)(86362001)(5250100002)(9686003)(5640700003)(2501003)(186003)(106356001)(54896002)(2351001)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0691; H:FRAPR01MB0691.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts) x-microsoft-antispam-message-info: Rws3qr60EayoPMDKgQtzhCN5ShGRxvymaSsAdFANcTIanaufOCqPRgs3T+KwyubjSG/XbbfkJXMyi1J3dw13bg== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_FRAPR01MB0691C8D03FC78C5FF60DD227FBE10FRAPR01MB0691DEUP_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 46adb9c2-fa2d-4678-ba2b-08d563d3db0a X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jan 2018 09:13:10.6487 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0691 X-OriginatorOrg: telekom.de Archived-At: Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 09:19:35 -0000 --_000_FRAPR01MB0691C8D03FC78C5FF60DD227FBE10FRAPR01MB0691DEUP_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I also support the adoption. As described in the liaison statement from ETSI NTECH (https://datatracker.= ietf.org/liaison/1527/), there is a need to enable its use to support the e= mergency caller location as defined by ETSI M493 Group. Regards Albrecht Von: sipcore [mailto:sipcore-bounces@ietf.org] Im Auftrag von Christer Holm= berg Gesendet: Donnerstag, 25. Januar 2018 08:35 An: marianne.mohali@orange.com; Jesske, Roland ; sipco= re@ietf.org Betreff: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 Hi, +1. I support adoption, and would participate in the work by reviewing and = commenting. (Note, though, that I did already provide comments on -01, and we had some = discussions, but I haven't checked whether everything has been addressed in= -02.) Regards, Christer From: sipcore > o= n behalf of "marianne.mohali@orange.com"= > Date: Tuesday 23 January 2018 at 12:07 To: "R.Jesske@telekom.de" >, "sipcore@ietf.org" <= sipcore@ietf.org> Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 Hi, I support having a call for adoption of this I-D. BR, Marianne De : sipcore [mailto:sipcore-bounces@ietf.org] De la part de R.Jesske@telek= om.de Envoy=E9 : mardi 23 janvier 2018 10:42 =C0 : sipcore@ietf.org Objet : [sipcore] draft-winterbottom-sipcore-locparam-02 Dear all, we had a slight discussion at the last IETF meeting on the draft draft-wint= erbottom-sipcore-locparam-02. As stated within the Minutes "log-param: will do call for adoption soon, on= the list". So I would like to ask if we can start the call for addition on the list? Best Regards Roland ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. --_000_FRAPR01MB0691C8D03FC78C5FF60DD227FBE10FRAPR01MB0691DEUP_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Dear all,

 

I also support the adoption.

As described in the liaison statement = from ETSI NTECH (htt= ps://datatracker.ietf.org/liaison/1527/), there is a need to enable its use to support the emergency caller location as de= fined by ETSI M493 Group.

 

 

Regards

Albrecht

 

 

Von: sipcore [mailto:sipcore-boun= ces@ietf.org] Im Auftrag von Christer Holmberg
Gesendet: Donnerstag, 25. Januar 2018 08:35
An: marianne.mohali@orange.com; Jesske, Roland <R.Jesske@telekom.= de>; sipcore@ietf.org
Betreff: Re: [sipcore] draft-winterbottom-sipcore-locparam-02

 

Hi,

&n= bsp;

+1.= I support adoption, and would participate in the work by reviewing and com= menting.

&n= bsp;

(Note, = though, that I did already provide comments on -01, and we had some discuss= ions, but I haven’t checked whether everything has been addressed in = –02.)

&n= bsp;

Regards= ,

&n= bsp;

Christe= r

&n= bsp;

From: sipcore <sipcore-bounces@ietf.org> on behalf of "marianne.mohali@orange.com" <marianne.mohali@orange.c= om>
Date: Tuesday 23 January 2018 at 12:07
To: "R.Jesske@telekom.de= " <R.Jesske@telekom.de>, "sipcore@ietf.org"= ; <sipcore@ietf.org>
Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02

&n= bsp;

Hi,

 

I support having a call fo= r adoption of this I-D.=

 

BR,

Marianne

 

De : sipcore [ma= ilto:sipcore-bounces@ietf.org] De la part de R.Jesske@teleko= m.de
Envoy=E9 : mardi 23 janvier 2018 10:42
=C0 : sipcore@ietf.org<= br> Objet : [sipcore] draft-winterbottom-sipcore-locparam-02=

 <= /o:p>

Dear all,

we had a slight di=
scussion at the last IETF meeting on the draft draft-winterbottom-sipcore-l=
ocparam-02.
As stated within t=
he Minutes “log-param: will do call for adoption soon, on the list=
221;.

 


So =
I would like to ask if we can start the call for addition on the list?


&nb=
sp;

Bes=
t Regards


&nb=
sp;

Rol=
and

 


 


 


____________________________=
___________________________________________________________________________=
__________________
 

Ce message et ses pieces joi=
ntes peuvent contenir des informations confidentielles ou privilegiees et n=
e doivent donc


pas etre diffuses, exploites=
 ou copies sans autorisation. Si vous avez recu ce message par erreur, veui=
llez le signaler


a l'expediteur et le detruir=
e ainsi que les pieces jointes. Les messages electroniques etant susceptibl=
es d'alteration,


Orange decline toute respons=
abilite si ce message a ete altere, deforme ou falsifie. Merci.<=
/span>


 

This message and its attachm=
ents may contain confidential or privileged information that may be protect=
ed by law;


they should not be distribut=
ed, used or copied without authorisation.


If you have received this em=
ail in error, please notify the sender and delete this message and its atta=
chments.


As emails may be altered, Or=
ange is not liable for messages that have been modified, changed or falsifi=
ed.


Thank you.=
--_000_FRAPR01MB0691C8D03FC78C5FF60DD227FBE10FRAPR01MB0691DEUP_-- From nobody Thu Jan 25 04:36:32 2018 Return-Path: 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 C8642124319 for ; Thu, 25 Jan 2018 04:36:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.234 X-Spam-Level: X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no 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 JMmI2Yo_OtTk for ; Thu, 25 Jan 2018 04:36:30 -0800 (PST) Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [69.252.207.36]) (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 8D0BD1242F7 for ; Thu, 25 Jan 2018 04:36:30 -0800 (PST) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-04v.sys.comcast.net with ESMTP id egjWeDEQpxbkoegjdeHSDI; Thu, 25 Jan 2018 12:34:29 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-14v.sys.comcast.net with SMTP id egjbeG2Ar9aG0egjcerMUY; Thu, 25 Jan 2018 12:34:28 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w0PCYPEP006844; Thu, 25 Jan 2018 07:34:25 -0500 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w0PCYOwt006831; Thu, 25 Jan 2018 07:34:24 -0500 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: Cc: sipcore@ietf.org In-Reply-To: (R.Jesske@telekom.de) Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 25 Jan 2018 07:34:24 -0500 Message-ID: <87po5yjewf.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfGTKHyg4I97z/RWcU9f5/N8JPzUSnsqg5vOZ03iYq3+rlSXad+lB/ZnXRRb6NgNJt80uZhYL2p1TdqXdurM0QY7nNOFBJ9yRLRbUVbeyyQgwTiDVqJ+g 7IjeLuhbF215Ci4Rzy1nNLJqw2REab/yTlN5Z9pClGQaND6408OCkK/zESRzmcI7mcceoVyveGBD7A== Archived-At: Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 12:36:32 -0000 writes: > So I would like to ask if we can start the call for addition on the list? I support adoption of this draft, for all the reasons others have given. ----- There is "The The" in section 1. ----- Wasn't there a draft defining values for , based on a four-bit field with similar semantics in ISUP. Or was that regarding a different SIP parameter? Dale From nobody Thu Jan 25 08:29:41 2018 Return-Path: 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 3557C12E882; Thu, 25 Jan 2018 08:29:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 BoWFZHqLf_Ah; Thu, 25 Jan 2018 08:29:36 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D962F12DA73; Thu, 25 Jan 2018 08:29:36 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 0280FB80E13; Thu, 25 Jan 2018 08:29:20 -0800 (PST) To: lreeder@bandwidth.com, jmpolk@cisco.com, br@brianrosen.net, jon.peterson@neustar.biz X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: ben@nostrum.com, iesg@ietf.org, sipcore@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20180125162921.0280FB80E13@rfc-editor.org> Date: Thu, 25 Jan 2018 08:29:20 -0800 (PST) Archived-At: Subject: [sipcore] [Errata Verified] RFC6442 (5027) X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 16:29:39 -0000 The following errata report has been verified for RFC6442, "Location Conveyance for the Session Initiation Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5027 -------------------------------------- Status: Verified Type: Technical Reported by: Larry Reeder Date Reported: 2017-05-31 Verified by: Ben Campbell (IESG) Section: 5.1 Original Text ------------- --boundary1 Content-Type: application/pidf+xml Content-ID: 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 B676D1242F7; Thu, 25 Jan 2018 08:30:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.21 X-Spam-Level: X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 7W4MKqHzaaP8; Thu, 25 Jan 2018 08:30:22 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6F6E1241F3; Thu, 25 Jan 2018 08:30:22 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 1B07BB80E24; Thu, 25 Jan 2018 08:30:07 -0800 (PST) To: rappleto@avaya.com, jmpolk@cisco.com, br@brianrosen.net, jon.peterson@neustar.biz X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Cc: ben@nostrum.com, iesg@ietf.org, sipcore@ietf.org, rfc-editor@rfc-editor.org Content-Type: text/plain; charset=UTF-8 Message-Id: <20180125163007.1B07BB80E24@rfc-editor.org> Date: Thu, 25 Jan 2018 08:30:07 -0800 (PST) Archived-At: Subject: [sipcore] [Errata Verified] RFC6442 (4236) X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 16:30:25 -0000 The following errata report has been verified for RFC6442, "Location Conveyance for the Session Initiation Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid4236 -------------------------------------- Status: Verified Type: Technical Reported by: Richard Appleton Date Reported: 2015-01-19 Verified by: Ben Campbell (IESG) Section: 5.1, 5.2 Original Text ------------- false Corrected Text -------------- no Notes ----- as per section 4.4 This location error is specific to having the PIDF-LO [RFC4119] element set to "no". This location error is stating it requires permission (i.e., PIDF-LO element set to "yes") and RFC4119 section 2.2.2 -------------------------------------- RFC6442 (draft-ietf-sipcore-location-conveyance-09) -------------------------------------- Title : Location Conveyance for the Session Initiation Protocol Publication Date : December 2011 Author(s) : J. Polk, B. Rosen, J. Peterson Category : PROPOSED STANDARD Source : Session Initiation Protocol Core RAI Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From nobody Thu Jan 25 12:35:26 2018 Return-Path: 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 75BC612EAAA for ; Thu, 25 Jan 2018 12:35:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.889 X-Spam-Level: X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 sRsTJzHR8xJ2 for ; Thu, 25 Jan 2018 12:35:22 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1BEB12EA5A for ; Thu, 25 Jan 2018 12:35:22 -0800 (PST) Received: from mutabilis-2.local ([47.186.15.50]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w0PKZLjB080670 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 25 Jan 2018 14:35:22 -0600 (CST) (envelope-from mahoney@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.15.50] claimed to be mutabilis-2.local To: SIPCORE From: "A. Jean Mahoney" Message-ID: Date: Thu, 25 Jan 2018 14:35:21 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [sipcore] WGLC: draft-ietf-sipcore-sip-push X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2018 20:35:24 -0000 Hi all, Working Group Last Call starts today for draft-ietf-sipcore-sip-push. https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ Please provide any feedback to the sipcore mailing list by Friday, February 9th. Thanks! Jean From nobody Thu Jan 25 18:34:26 2018 Return-Path: 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 A18D512D87F for ; Thu, 25 Jan 2018 18:34:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 P72QRL6ogrPk for ; Thu, 25 Jan 2018 18:34:23 -0800 (PST) Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 7ADA412D854 for ; Thu, 25 Jan 2018 18:34:23 -0800 (PST) Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id etqGePH2Hvd8retqQev0sK; Fri, 26 Jan 2018 02:34:22 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with SMTP id etqOerHppXRegetqPeLqSp; Fri, 26 Jan 2018 02:34:21 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w0Q2YJdq019785; Thu, 25 Jan 2018 21:34:19 -0500 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w0Q2YJt0019782; Thu, 25 Jan 2018 21:34:19 -0500 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: worley@ariadne.com (Dale R. Worley) Cc: R.Jesske@telekom.de, sipcore@ietf.org In-Reply-To: <87po5yjewf.fsf@hobgoblin.ariadne.com> (worley@ariadne.com) Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 25 Jan 2018 21:34:19 -0500 Message-ID: <87607pjql0.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfDK8XxyA6485veFAojaYGiXevBK9y/FoQZFKTNxpohzhiD4ijnEhDB2Y2XCPoQhqHWQVfhgpgPD41Rao6pJty3Q5VM+KPEwYLH7pdku7olLr9i8M7ib6 kRiFxqJCozTCuZMsCnx9AC8m3d7KbxO/WvkyfKq0uozMDJTxku0jq+e2LGWZsh9KWRyByXTdy2fJ6oI5WxkSuyUZ94teSNxOFiLcbn4iKXPHN0SB60FKKFwB Archived-At: Subject: Re: [sipcore] draft-winterbottom-sipcore-locparam-02 X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 02:34:24 -0000 worley@ariadne.com (Dale R. Worley) writes: > I support adoption of this draft, for all the reasons others have given. > ----- > > Wasn't there a draft defining values for , based on a > four-bit field with similar semantics in ISUP. Or was that regarding a > different SIP parameter? I was wrong about that; I was thinking of draft-winterbottom-sipcore-locparam-02, which defines tokens for "locations" in the network, as encoded by ISUP in a 4-bit field. But is there reason to think that these values might be intended or useful as "other-loc-src" values in the loc-src parameter? Dale From nobody Thu Jan 25 18:36:47 2018 Return-Path: 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 24AA912D87F for ; Thu, 25 Jan 2018 18:36:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no 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 WCe2PJs2OJX0 for ; Thu, 25 Jan 2018 18:36:45 -0800 (PST) Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 063CF12D854 for ; Thu, 25 Jan 2018 18:36:44 -0800 (PST) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-08v.sys.comcast.net with ESMTP id etsiePHDDvd8retsiev18I; Fri, 26 Jan 2018 02:36:44 +0000 Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-17v.sys.comcast.net with SMTP id etsgekpAZz86vetsheDp15; Fri, 26 Jan 2018 02:36:43 +0000 Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w0Q2afsR019931; Thu, 25 Jan 2018 21:36:41 -0500 Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w0Q2afRm019928; Thu, 25 Jan 2018 21:36:41 -0500 X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f From: worley@ariadne.com (Dale R. Worley) To: Cc: sipcore@ietf.org In-Reply-To: (R.Jesske@telekom.de) Sender: worley@ariadne.com (Dale R. Worley) Date: Thu, 25 Jan 2018 21:36:41 -0500 Message-ID: <87372tjqh2.fsf@hobgoblin.ariadne.com> X-CMAE-Envelope: MS4wfFv/UMZV2R9o/7GPm0XsNVk3tyQIjE5C2ddZUuE9vsuuLfh9mah1n80kwB0TgSJ8apqr+/MM/0tJ2wC3L6a/f1CfnqkSnVMvjLDuinivDO4nEhnhhZpG V6PhAhkUftaChPUa+RrTisU1phf6QoJhXViU5t7uXy4vSg2sdKLZw48TGTpozfo0J6rPV4aATy4JqQ== Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 02:36:46 -0000 writes: > So question is if we can proceed with a WGLC for this draft? Yes, let us proceed to WGLC for draft-ietf-sipcore-reason-q850-loc. Dale From nobody Fri Jan 26 07:34:35 2018 Return-Path: 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 10F0B12DA29 for ; Fri, 26 Jan 2018 07:34:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no 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 Ao41epT08FpX for ; Fri, 26 Jan 2018 07:34:32 -0800 (PST) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 665A6124207 for ; Fri, 26 Jan 2018 07:34:32 -0800 (PST) Received: from mutabilis-2.local ([47.186.15.50]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w0QFYV5K009056 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 26 Jan 2018 09:34:31 -0600 (CST) (envelope-from mahoney@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host [47.186.15.50] claimed to be mutabilis-2.local To: sipcore@ietf.org References: <87372tjqh2.fsf@hobgoblin.ariadne.com> From: "A. Jean Mahoney" Message-ID: <8fd33198-514c-372c-ac9e-2f7ae5a18d50@nostrum.com> Date: Fri, 26 Jan 2018 09:34:30 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <87372tjqh2.fsf@hobgoblin.ariadne.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-reason-q850-loc-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2018 15:34:34 -0000 Hi all, The chairs talked over scheduling for WGLCs. We have started WGLC for sip-push. Since we didn't want completely overlapping WGLCs, we will start WGLC for this draft at the end of next week. Thanks! Jean On 1/25/18 8:36 PM, Dale R. Worley wrote: > writes: >> So question is if we can proceed with a WGLC for this draft? > > Yes, let us proceed to WGLC for draft-ietf-sipcore-reason-q850-loc. > > Dale > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > From nobody Wed Jan 31 07:19:15 2018 Return-Path: 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 727D4131871 for ; Wed, 31 Jan 2018 07:19:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.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 0ZZLcFh3Su1q for ; Wed, 31 Jan 2018 07:19:12 -0800 (PST) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D9ED12EB71 for ; Wed, 31 Jan 2018 07:18:12 -0800 (PST) Received: by mail-pf0-x22a.google.com with SMTP id y26so12916594pfi.10 for ; Wed, 31 Jan 2018 07:18:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8CSGjqinex0HNyMSt3WDHFzqU7CIk8eCAozJGrEeLa8=; b=Bq/h/qH4I8IRRXEo5H8r7paD92MWxcb4e3S6AjL8ez0ak/4s7sxJSn/MMzRl8aZB5w Qy14pCmc9qvJP7nnWKGepif/6cygyTLvS/tF2Sd3Mu/MAkrEERv8vLVLtDJ0zaM9a1dQ YnJUzGs63SI1f499bMJejTaZE/8lsI79P5vcoJrSb/xo17PzO/Y2BBXVUOLAjW9OhyJe 8aEyMBjTLrxEP/RtKqlnNyApjTy7wGDv8ZPvGuupkEnwgIVhJreg1vynkxeFBy6kipKL BteUeFusuywmoqhMVXN7RSnnUnyvL7+CctExl9Sm6PfXNi9pS4xy9XIEEvOIz7me4rjG vfhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8CSGjqinex0HNyMSt3WDHFzqU7CIk8eCAozJGrEeLa8=; b=mFUs8zV/xOkALAQ/yzjyYax7gVRLw1IlemetUgTQYOPtiETKjBv7UBNcL7F6QiOiR3 j9UEE3uuPtzd3dtzEOekSydUyjiF2awiTODSiT5FqO3zF5YT7mBnAfxizyT+zHBTkt4W +Of9KHzbdG4N5C/MQ7VOQZpNOXdF5E6J3ageHJnnRAlPYhyTBoYB5FFdzEJ9w1MwA10F ezlLJjTYtT5/6gZU+bAWAOcGFCJh5cRhgTaa+Bft2l2D4dwWNYoCY+qmhPaSOMUd4Sfy zVA1vMGilTmj00JPjvp+3gaE31KhDk6YyuUHCvqSkPHTx88VBvxXorKF3p3O69wIlMUX KqiQ== X-Gm-Message-State: AKwxytfWsja/gpTlaaXpUTHdi5A9/K50TOR0NM1DuFF0e1zaMEp1yQ9f 4we+FPYRJSWfAvo802+Mns9b297a X-Google-Smtp-Source: AH8x2261SfNgfuV6Nch4JSIKjpSw2DNdXDXWslXWl9ToF9OIpafYkbHcxPjVswuYrrzSSTHbDQDg9Q== X-Received: by 2002:a17:902:bd82:: with SMTP id q2-v6mr19654344pls.339.1517411891553; Wed, 31 Jan 2018 07:18:11 -0800 (PST) Received: from mail-pf0-f170.google.com (mail-pf0-f170.google.com. [209.85.192.170]) by smtp.gmail.com with ESMTPSA id w12sm38553971pfd.86.2018.01.31.07.18.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 07:18:10 -0800 (PST) Received: by mail-pf0-f170.google.com with SMTP id b25so12911874pfd.9 for ; Wed, 31 Jan 2018 07:18:10 -0800 (PST) X-Received: by 2002:a17:902:6b49:: with SMTP id g9-v6mr29133496plt.9.1517411890257; Wed, 31 Jan 2018 07:18:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.191.3 with HTTP; Wed, 31 Jan 2018 07:18:09 -0800 (PST) In-Reply-To: References: From: Roman Shpount Date: Wed, 31 Jan 2018 10:18:09 -0500 X-Gmail-Original-Message-ID: Message-ID: To: SIPCORE , Christer Holmberg Content-Type: multipart/alternative; boundary="000000000000b2642c056413fcd9" Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 15:19:14 -0000 --000000000000b2642c056413fcd9 Content-Type: text/plain; charset="UTF-8" Hi All, I have reviewed this document. I have following comments: 1. In https://tools.ietf.org/html/draft-ietf-sipcore-sip-push-04#section-5.3 the document says: When the SIP proxy receives (or, in case the proxy is the SIP registrar, creates) a SIP request for a new dialog (e.g., a SIP INVITE request) or a non-dialog SIP request (e.g., a SIP MESSAGE request) aimed for a SIP UA, if the Request-URI of the request contains a pn-provider, a pn-prid and a pn-param (if required for the specific PNS provider) SIP URI parameter, the proxy triggers a push request towards the PNS associated with the PRID. After that the proxy forwards the SIP request towards the UA using normal SIP procedures. Does this create a potential race condition? The push notification request can take a substantial time to get delivered, so the NAT binding might still be absent and SIP message will not be delivered to the UA. Is this supposed to be handled by SIP Message re-transmit timers? In this case call setup will be significantly delayed especially if push service takes more then 0.5 sec to deliver the notification which will cause first two SIP re-transmit message to be lost. Also, what happens when reliable transport protocol is used such as SIPS is used and no re-transmit timers are there? Note that re-registration from the client might come from a new IP:port, especially in cases when new SIPS TCP connection is established for this and SIP message destination address can change from previous registration. Our solution for the similar problem was to store the message and only transmit it when registration from the client was received. 2. Does this document always require for a SIP Proxy to send regular timer based push messages to keep SIP Registrations active? Such policy will result in additional load and cost for the SIP Service operator. In most cases client application can be woken up on timer and does not need this, so this should be optional and controlled by pn-XXX parameter. 3. Does the proxy strip the pn-XXX parameters when forwarding message to the client or are they kept? Does it strip them when comparing contact registration URI? Without this, change in pn-XXX parameters will result in a new registration instead of existing registration update. Regards, _____________ Roman Shpount On Thu, Jan 25, 2018 at 3:35 PM, A. Jean Mahoney wrote: > Hi all, > > Working Group Last Call starts today for draft-ietf-sipcore-sip-push. > > https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ > > Please provide any feedback to the sipcore mailing list by Friday, > February 9th. > > > Thanks! > > Jean > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore > --000000000000b2642c056413fcd9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

I have reviewed this document. = I have following comments:


When the SIP proxy receives (or, in case= the proxy is the SIP registrar, creates) a SIP request for a new dialog (e= .g., a SIP INVITE request) or a non-dialog SIP request (e.g., a SIP MESSAGE= request) aimed for a SIP UA, if the Request-URI of the request contains a = pn-provider, a pn-prid and a pn-param (if required for the=C2=A0specific PN= S provider) SIP URI parameter, the proxy triggers a push=C2=A0request towar= ds the PNS associated with the PRID.=C2=A0 After that the=C2=A0proxy forwar= ds the SIP request towards the UA using normal SIP procedures.

Does this create a potential race condition? The push notification r= equest can take a substantial time to get delivered, so the NAT binding mig= ht still be absent and SIP message will not be delivered to the UA.

Is this supposed to be handled by SIP Message re-transmit= timers? In this case call setup will be significantly delayed especially i= f push service takes more then 0.5 sec to deliver the notification which wi= ll cause first two SIP re-transmit message to be lost.

=
Also, what happens when reliable transport protocol is used such as SI= PS is used and=C2=A0 no re-transmit timers are there?
Note that r= e-registration from the client might come from a new IP:port, especially in= cases when new SIPS TCP connection is established for this and SIP message= destination address can change from previous registration.

<= /div>
Our solution for the similar problem was to store the message and= only transmit it when registration from the client was received.

2. Does this document always require for a SIP Proxy to sen= d regular timer based push messages to keep SIP Registrations active? Such = policy will result in additional load and cost for the SIP Service operator= . In most cases client application can be woken up on timer and does not ne= ed this, so this should be optional and controlled by pn-XXX parameter.

3. Does the proxy strip the pn-XXX parameters when fo= rwarding message to the client or are they kept? Does it strip them when co= mparing contact registration URI? Without this, change in pn-XXX parameters= will result in a new registration instead of existing registration update.=

Regards,
_____________
Roman Shpount

On Thu, Jan 25, 2018 at 3:35 PM, A. Jean Mah= oney <mahoney@nostrum.com> wrote:
Hi all,

Working Group Last Call starts today for draft-ietf-sipcore-sip-push.

https://datatracker.ietf.org/doc/d= raft-ietf-sipcore-sip-push/

Please provide any feedback to the sipcore mailing list by Friday, February= 9th.


Thanks!

Jean

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

--000000000000b2642c056413fcd9-- From nobody Wed Jan 31 08:37:46 2018 Return-Path: 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 8D4A312EBDF for ; Wed, 31 Jan 2018 08:37:45 -0800 (PST) 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 5zBB5P2N35bt for ; Wed, 31 Jan 2018 08:37:43 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 216C912EBF7 for ; Wed, 31 Jan 2018 08:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517416637; 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=XIX4pt74xWBR1rfzZCC81VfAmFV/bQCp6aEAl3y92cs=; b=g/2uYyQDBeDeFPpvGkZbLmKs0TGLVOYcGr8jLlKoWXR45xiILb1d+ktrZ4rGe+o+ IWm5TUsGD/z6KqCzlZlnG775jxWE4V2BNLKkcvVwp58IbN0xOmrUlytwpmufm8/Y srKZnT4j7Qz0BkpzEg+9zK79G4AvyHPYc0zLpuo2HSg=; X-AuditID: c1b4fb3a-335ff700000037f2-53-5a71f0bcb5d0 Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id CF.3C.14322.CB0F17A5; Wed, 31 Jan 2018 17:37:17 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 17:37:16 +0100 From: Christer Holmberg To: Roman Shpount , SIPCORE Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments Thread-Index: AdOarhvXN/SIYCSZQy2pLjQXhqV0eg== Date: Wed, 31 Jan 2018 16:37:15 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@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.149] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM2K7h+7eD4VRBu8CLRo6V7JazLgwldni 649NbA7MHkuW/GTymLXzCYvHrSkFAcxRXDYpqTmZZalF+nYJXBnH1n5jLWhQqpi3s5WxgXGC YhcjJ4eEgInEhek/WbsYuTiEBA4zSmz+Np8dwlnCKPGjfRFbFyMHB5uAhUT3P22QBhEBR4nt SzexgtjMAtoSMzedZgIpERbwlnjawQtR4iNxqucNC4StJ3HjWTcjiM0ioCrR9Pc9M4jNK+Ar MX/yfTCbUUBM4vupNUwQI8Ulbj2ZzwRxm4DEkj3nmSFsUYmXj/+xQthKEmsPb2cBWcssoCmx fpc+RKuixJTuh+wQ4wUlTs58wjKBUXgWkqmzEDpmIemYhaRjASPLKkbR4tTi4tx0IyO91KLM 5OLi/Dy9vNSSTYzACDi45bfVDsaDzx0PMQpwMCrx8N66VxglxJpYVlyZe4hRgoNZSYR3z0Wg EG9KYmVValF+fFFpTmrxIUZpDhYlcV6nNIsoIYH0xJLU7NTUgtQimCwTB6dUA+NMhyt7k997 fEuwmHLUKPGy44RDKw8wvQrmZkze0FVVGL5iZ5TP7hmBXrdbnK17GPI4D0tbaq93Fq9V1Ou7 ueiiQ07gc6Ej59Zkl9pvrdhRFfzVtuO2e1O2ye4A7d+uKvUrbFUiLKImTUuzsV4r3fhsyzZL 1rCAiTvWu9vOrJ/58K/Lm1NT7iuxFGckGmoxFxUnAgBbrJwrfAIAAA== Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:37:45 -0000 SGkgUm9tYW4sDQoNClRoYW5rcyBmb3IgeW91ciBjb21tZW50cyEgUGxlYXNlIHNlZSBpbmxpbmUu DQoNCj4xLiBJbsKgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtc2lwY29y ZS1zaXAtcHVzaC0wNCNzZWN0aW9uLTUuMyB0aGUgZG9jdW1lbnQgc2F5czoNCj4NCj5XaGVuIHRo ZSBTSVAgcHJveHkgcmVjZWl2ZXMgKG9yLCBpbiBjYXNlIHRoZSBwcm94eSBpcyB0aGUgU0lQIHJl Z2lzdHJhciwgY3JlYXRlcykgYSBTSVAgcmVxdWVzdCBmb3IgYSBuZXcgDQo+ZGlhbG9nIChlLmcu LCBhIFNJUCBJTlZJVEUgcmVxdWVzdCkgb3IgYSBub24tZGlhbG9nIFNJUCByZXF1ZXN0IChlLmcu LCBhIFNJUCBNRVNTQUdFIHJlcXVlc3QpIGFpbWVkIGZvciBhIA0KPlNJUCBVQSwgaWYgdGhlIFJl cXVlc3QtVVJJIG9mIHRoZSByZXF1ZXN0IGNvbnRhaW5zIGEgcG4tcHJvdmlkZXIsIGEgcG4tcHJp ZCBhbmQgYSBwbi1wYXJhbSAoaWYgcmVxdWlyZWQgZm9yIA0KPnRoZcKgc3BlY2lmaWMgUE5TIHBy b3ZpZGVyKSBTSVAgVVJJIHBhcmFtZXRlciwgdGhlIHByb3h5IHRyaWdnZXJzIGEgcHVzaMKgcmVx dWVzdCB0b3dhcmRzIHRoZSBQTlMgYXNzb2NpYXRlZCANCj53aXRoIHRoZSBQUklELsKgIEFmdGVy IHRoYXQgdGhlwqBwcm94eSBmb3J3YXJkcyB0aGUgU0lQIHJlcXVlc3QgdG93YXJkcyB0aGUgVUEg dXNpbmcgbm9ybWFsIFNJUCBwcm9jZWR1cmVzLg0KPg0KPkRvZXMgdGhpcyBjcmVhdGUgYSBwb3Rl bnRpYWwgcmFjZSBjb25kaXRpb24/IFRoZSBwdXNoIG5vdGlmaWNhdGlvbiByZXF1ZXN0IGNhbiB0 YWtlIGEgc3Vic3RhbnRpYWwgdGltZSB0byBnZXQgDQo+ZGVsaXZlcmVkLCBzbyB0aGUgTkFUIGJp bmRpbmcgbWlnaHQgc3RpbGwgYmUgYWJzZW50IGFuZCBTSVAgbWVzc2FnZSB3aWxsIG5vdCBiZSBk ZWxpdmVyZWQgdG8gdGhlIFVBLg0KPg0KPklzIHRoaXMgc3VwcG9zZWQgdG8gYmUgaGFuZGxlZCBi eSBTSVAgTWVzc2FnZSByZS10cmFuc21pdCB0aW1lcnM/IEluIHRoaXMgY2FzZSBjYWxsIHNldHVw IHdpbGwgYmUgc2lnbmlmaWNhbnRseSANCj5kZWxheWVkIGVzcGVjaWFsbHkgaWYgcHVzaCBzZXJ2 aWNlIHRha2VzIG1vcmUgdGhlbiAwLjUgc2VjIHRvIGRlbGl2ZXIgdGhlIG5vdGlmaWNhdGlvbiB3 aGljaCB3aWxsIGNhdXNlIGZpcnN0IHR3bw0KPlNJUCByZS10cmFuc21pdCBtZXNzYWdlIHRvIGJl IGxvc3QuDQo+DQo+QWxzbywgd2hhdCBoYXBwZW5zIHdoZW4gcmVsaWFibGUgdHJhbnNwb3J0IHBy b3RvY29sIGlzIHVzZWQgc3VjaCBhcyBTSVBTIGlzIHVzZWQgYW5kwqAgbm8gcmUtdHJhbnNtaXQg dGltZXJzIGFyZSB0aGVyZT8NCj5Ob3RlIHRoYXQgcmUtcmVnaXN0cmF0aW9uIGZyb20gdGhlIGNs aWVudCBtaWdodCBjb21lIGZyb20gYSBuZXcgSVA6cG9ydCwgZXNwZWNpYWxseSBpbiBjYXNlcyB3 aGVuIG5ldyBTSVBTIFRDUCBjb25uZWN0aW9uIA0KPmlzIGVzdGFibGlzaGVkIGZvciB0aGlzIGFu ZCBTSVAgbWVzc2FnZSBkZXN0aW5hdGlvbiBhZGRyZXNzIGNhbiBjaGFuZ2UgZnJvbSBwcmV2aW91 cyByZWdpc3RyYXRpb24uDQo+DQo+T3VyIHNvbHV0aW9uIGZvciB0aGUgc2ltaWxhciBwcm9ibGVt IHdhcyB0byBzdG9yZSB0aGUgbWVzc2FnZSBhbmQgb25seSB0cmFuc21pdCBpdCB3aGVuIHJlZ2lz dHJhdGlvbiBmcm9tIHRoZSBjbGllbnQgd2FzIHJlY2VpdmVkLg0KDQpDb3JyZWN0LiBBbmQsIHRo YXQgaXMgZGVzY3JpYmVkIGluIHRoZSBmb2xsb3dpbmcgcGFyYWdyYXBoIDopDQoNClRoZSByZWFz b24gZm9yIGFsbG93aW5nIHRoZSByZXF1ZXN0IHRvIGJlIGZvcndhcmRlZCBiZWZvcmUgdGhlIFJF R0lTVEVSIGFycml2ZXMgaXMgbW9yZSBhbiBvcHRpbWl6YXRpb24sIGluIGNhc2UgdGhlIGNvbm5l Y3Rpb24gYmV0d2VlbiB0aGUgVUEgYW5kIHByb3h5IGlzIHN0aWxsIGF2YWlsYWJsZSBmcm9tIGEg cHJldmlvdXMgc2Vzc2lvbi4NCg0KPjIuIERvZXMgdGhpcyBkb2N1bWVudCBhbHdheXMgcmVxdWly ZSBmb3IgYSBTSVAgUHJveHkgdG8gc2VuZCByZWd1bGFyIHRpbWVyIGJhc2VkIHB1c2ggbWVzc2Fn ZXMgdG8ga2VlcCBTSVAgUmVnaXN0cmF0aW9ucyANCj5hY3RpdmU/IFN1Y2ggcG9saWN5IHdpbGwg cmVzdWx0IGluIGFkZGl0aW9uYWwgbG9hZCBhbmQgY29zdCBmb3IgdGhlIFNJUCBTZXJ2aWNlIG9w ZXJhdG9yLiBJbiBtb3N0IGNhc2VzIGNsaWVudCBhcHBsaWNhdGlvbiBjYW4gDQo+YmUgd29rZW4g dXAgb24gdGltZXIgYW5kIGRvZXMgbm90IG5lZWQgdGhpcywgc28gdGhpcyBzaG91bGQgYmUgb3B0 aW9uYWwgYW5kIGNvbnRyb2xsZWQgYnkgcG4tWFhYIHBhcmFtZXRlci4NCg0KQXQgbGVhc3QgaW4g dGhlIGNhc2Ugb2YgaU9TLCB0aGUgYXBwbGljYXRpb24gY2FuIE5PVCBiZSB3b2tlbiB1cCBieSBh biBhcHBsaWNhdGlvbiB0aW1lciwgYXMgZmFyIGFzIEkgdW5kZXJzdGFuZC4gUHVzaCAob3IgdXNl ciBpbnRlcmFjdGlvbikgaXMgdGhlIG9ubHkgd2F5IHRvIHdha2UgdGhlIGFwcGxpY2F0aW9uIDop IA0KDQooVGhlcmUgdXNlZCB0byBiZSBhICJWb0lQIG1vZGUiIGluIGlPUywgYnV0IGl0IGhhcyBi ZWVuIGRlcHJlY2F0ZWQuKQ0KDQpCdXQsIGluIGdlbmVyYWwsIHJlLXJlZ2lzdHJhdGlvbnMgYXJl IG5vcm1hbGx5IG5vdCB0aGF0IGZyZXF1ZW50LCBzbyBJIGRvbid0IHRoaW5rIGl0IHdpbGwgY2F1 c2UgdG9vIG11Y2ggbG9hZC4NCg0KPjMuIERvZXMgdGhlIHByb3h5IHN0cmlwIHRoZSBwbi1YWFgg cGFyYW1ldGVycyB3aGVuIGZvcndhcmRpbmcgbWVzc2FnZSB0byB0aGUgY2xpZW50IG9yIGFyZSB0 aGV5IGtlcHQ/IERvZXMgaXQgc3RyaXAgDQo+dGhlbSB3aGVuIGNvbXBhcmluZyBjb250YWN0IHJl Z2lzdHJhdGlvbiBVUkk/IFdpdGhvdXQgdGhpcywgY2hhbmdlIGluIHBuLVhYWCBwYXJhbWV0ZXJz IHdpbGwgcmVzdWx0IGluIGEgbmV3IHJlZ2lzdHJhdGlvbiANCj5pbnN0ZWFkIG9mIGV4aXN0aW5n IHJlZ2lzdHJhdGlvbiB1cGRhdGUuDQoNClRoZXJlIGlzIG5vIHN0cmlwcGluZyBvZiBwYXJhbWV0 ZXJzLiBUaGUgcG4tIHBhcmFtZXRlcnMgd2lsbCB0eXBpY2FsbHkgbm90IGNoYW5nZSBiZXR3ZWVu IFVBIGRldmljZSByZWJvb3RzLiBCdXQsIGlmIHRoZXkgZG8sIGl0IGRvZXMgcmVxdWlyZSBhIG5l dyByZWdpc3RyYXRpb24uDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg== From nobody Wed Jan 31 08:51:00 2018 Return-Path: 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 1854B12EBD5 for ; Wed, 31 Jan 2018 08:50:59 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...] X-Spam-Flag: NO X-Spam-Score: -4.209 X-Spam-Level: X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 DAk4mRhx9rR4 for ; Wed, 31 Jan 2018 08:50:53 -0800 (PST) Received: from mail.opensips.org (opensips.org [136.243.23.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5926712EB7D for ; Wed, 31 Jan 2018 08:50:30 -0800 (PST) Received: from [109.99.227.30] (helo=[10.0.0.6]) by mail.opensips.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1egvad-00076N-5G for sipcore@ietf.org; Wed, 31 Jan 2018 11:50:28 -0500 To: sipcore@ietf.org References: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> From: Liviu Chircu Message-ID: <1d25dfde-8d78-9820-0cbb-c44815fa644e@opensips.org> Date: Wed, 31 Jan 2018 18:50:22 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:50:59 -0000 Hi all, On 31.01.2018 18:37, Christer Holmberg wrote: >> 3. Does the proxy strip the pn-XXX parameters when forwarding message to the client or are they kept? Does it strip >> them when comparing contact registration URI? Without this, change in pn-XXX parameters will result in a new registration >> instead of existing registration update. > There is no stripping of parameters. The pn- parameters will typically not change between UA device reboots. But, if they do, it does require a new registration. > Then what happens if a "pn-XXX" enabled INVITE R-URI from UA "a" to UA "b" traverses a chain of SIP proxies which are all "sip-push" aware? Will they not each perform the following:     * launch PNS provider query     * wait for re-REGISTER     * forward INVITE to the next "sip-push" aware proxy Thanks, Liviu > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 31 08:56:18 2018 Return-Path: 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 ED7FC12EB9E for ; Wed, 31 Jan 2018 08:56:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.02 X-Spam-Level: X-Spam-Status: No, score=-2.02 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_NONE=-0.0001, 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=metaswitch.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 NdrvZO1XoTKL for ; Wed, 31 Jan 2018 08:56:16 -0800 (PST) Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0091.outbound.protection.outlook.com [104.47.34.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E933312EB8C for ; Wed, 31 Jan 2018 08:56:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8sr/FEnCDpCodWG47i1mPl261n2ZhsyAp+e+5KoWeVs=; b=QuNU2EvDjHmG4+faa/jqCwznqPsfIOjDIXjjDVuKYJ643IULsTDNRkXv89u2w1X+RT+nIVs580qZDJN3yTReNynIR45e100XxaHcKF3mKB4sODGBJeRdsnuFu/Qf5wmAgLj1jogE4IVffXlAGHlOstOdOy4ORZBm1d7yl2dD23A= Received: from CY1PR02MB1262.namprd02.prod.outlook.com (10.163.16.155) by CY1PR02MB1995.namprd02.prod.outlook.com (10.166.189.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.14; Wed, 31 Jan 2018 16:56:14 +0000 Received: from CY1PR02MB1262.namprd02.prod.outlook.com ([10.163.16.155]) by CY1PR02MB1262.namprd02.prod.outlook.com ([10.163.16.155]) with mapi id 15.20.0444.016; Wed, 31 Jan 2018 16:56:14 +0000 From: Mickey Arnold To: SIPCORE , Christer Holmberg Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push Thread-Index: AQHTlhwLHKxh67zPd0iPtQS6SONdoKOOOlzQ Date: Wed, 31 Jan 2018 16:55:55 +0000 Deferred-Delivery: Wed, 31 Jan 2018 16:55:40 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Arnold@metaswitch.com; x-originating-ip: [2620:104:4000:206e:449:a3b9:11a0:f1b5] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CY1PR02MB1995; 7:+MK9qxHG4nfPxRk9NQdO7zZQN9ZkZLyjWZ7la/MdyXEviE/rTt8ZIcY3YfSo96sI5ee+801zM8IxFd1tGaDU4yvVLPSawZwrxdHYPnuimRBPT3VT40jy+oXPK80JBMqgdO9iikvFW+dNG0LKPg9sWu2KsKvw4mGzuZvEwYFRIdPblj6sCPpS8ASU174M8ZOKTPahdAQZ+Hgtdj9/bn7Z5bBlqlZXn8AbFrrJNGw47knHIGcC/jYGxZgdaaOUXbSk x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: fb8705cd-7f48-4097-0413-08d568cb89c1 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:CY1PR02MB1995; x-ms-traffictypediagnostic: CY1PR02MB1995: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105)(192374486261705)(48300812402016); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231101)(2400082)(944501161)(3002001)(10201501046)(6041288)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:CY1PR02MB1995; BCL:0; PCL:0; RULEID:; SRVR:CY1PR02MB1995; x-forefront-prvs: 056929CBB8 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39850400004)(366004)(376002)(39380400002)(53754006)(189003)(199004)(13464003)(966005)(105586002)(2950100002)(2906002)(59450400001)(102836004)(305945005)(478600001)(6666003)(6506007)(186003)(53546011)(2900100001)(6246003)(5660300001)(7696005)(8676002)(106356001)(68736007)(76176011)(25786009)(77096007)(86362001)(33656002)(7736002)(6116002)(9686003)(6306002)(3660700001)(99286004)(55016002)(97736004)(74316002)(3280700002)(53936002)(229853002)(81156014)(316002)(72206003)(8936002)(81166006)(110136005)(14454004)(6436002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR02MB1995; H:CY1PR02MB1262.namprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: metaswitch.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: 1ObmofVcgCMv+zkpc+n4fhtKpdlP4y+7vY+uHPP0OJugTrIJdz3WVFqinR7XV/serlSiFJG6UuxPXtuSp0oh+g== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: metaswitch.com X-MS-Exchange-CrossTenant-Network-Message-Id: fb8705cd-7f48-4097-0413-08d568cb89c1 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jan 2018 16:56:13.9852 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR02MB1995 Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 16:56:18 -0000 Hi Christer, I've a few comments, the first of which I believe requires a change to the = draft. -- Major comment -- Section 1: The proxy can use the receipt of the REGISTER request as a trigger to forward SIP request towards the UA, using normal SIP routing procedures. Section 4: If the SIP proxy triggered the push notification because it wants to forward a SIP request towards the UA, the receipt of the REGISTER request can be used by the proxy as a trigger to forward the request. Section 5.3: As the push notification will trigger the SIP UA to perform a re- registration, the SIP proxy can use the receipt of the SIP REGISTER request as a trigger to forward SIP request towards the UA. The SIP proxy should only be allowed to use the received (or generated if t= he Proxy contains the registrar functionality) 200 OK response to the REGIS= TER as a trigger to send on the queued message. Otherwise the proxy will be= re-routing based on a unconfirmed REGISTER request. If the reregister fail= s then the proxy has forwarded the INVITE or OOD request on to a contact UR= I that is not stored in the registrar. This would likely cause the call to = fail but also raises security concerns where a well-timed re-register with = incorrect SIP authentication by a 3rd party could "steal" a SIP message. -- Minor comments -- Typo in Section 1. I think "Some are based on there standardized mechanism..." Should be "Some are based on the standardized mechanism..." Section 1 Consider adding a mention of the feature capabilities indicator. Section 3 Consider clarifying that PRID need only be unique per PNS. Also consider cl= arifying that this mechanism is only appropriate for notification systems t= hat provide such a token. I hope that's useful feedback, please let me know if you have any follow-up= questions. Regards, Mickey -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of A. Jean Mahone= y Sent: 25 January 2018 20:35 To: SIPCORE Subject: [sipcore] WGLC: draft-ietf-sipcore-sip-push Hi all, Working Group Last Call starts today for draft-ietf-sipcore-sip-push. https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ Please provide any feedback to the sipcore mailing list by Friday, February= 9th. Thanks! Jean _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 31 09:20:38 2018 Return-Path: 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 C577312EC30 for ; Wed, 31 Jan 2018 09:20:36 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...] X-Spam-Flag: NO X-Spam-Score: -4.209 X-Spam-Level: X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 Ug45cYDCZpdI for ; Wed, 31 Jan 2018 09:20:34 -0800 (PST) Received: from mail.opensips.org (opensips.org [136.243.23.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2801131898 for ; Wed, 31 Jan 2018 09:18:51 -0800 (PST) Received: from [109.99.227.30] (helo=[10.0.0.6]) by mail.opensips.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1egw25-0007P9-83 for sipcore@ietf.org; Wed, 31 Jan 2018 12:18:49 -0500 To: sipcore@ietf.org References: From: Liviu Chircu Message-ID: Date: Wed, 31 Jan 2018 19:18:44 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Editorial Comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 17:20:37 -0000 Hi, I spotted some minor nuisances: Section 7.1 - typo  "555 (Push Notficiation Service Not Supported)" Section 7.2 - inconsistency (possibly due to an old iteration) The BNF grammar defines a series of "pn-*" params, yet the last sentence references a couple of undefined "pns-*" params: "The format and semantics of pns-param is specific to a given pns-provider value." Best regards, Liviu On 25.01.2018 22:35, A. Jean Mahoney wrote: > Hi all, > > Working Group Last Call starts today for draft-ietf-sipcore-sip-push. > > https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ > > Please provide any feedback to the sipcore mailing list by Friday, > February 9th. > > > Thanks! > > Jean > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 31 09:32:55 2018 Return-Path: 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 69B5A12DA46 for ; Wed, 31 Jan 2018 09:32:53 -0800 (PST) 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 VnuZ1a5L_1of for ; Wed, 31 Jan 2018 09:32:51 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 14EB712EB7D for ; Wed, 31 Jan 2018 09:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517419969; 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=t7KcfBWuRVg2RF33kStaalmcy+9NgJBIReXUWj0u/mg=; b=bScte09CHgH8kku8ZxQMPXm2GdwEy56LR9Q0j2s16vaW1nD+dEfEBzg5vpba6tP1 ssX2jBVr4D4SpCo6wS7k3R449mfHMqxht5OWQ3KG6fxR7zrXhm73rXYzaoPUKUGB +DiiZ7OFdRmqLL3uWq0bgglc3poHIKXpm2Joe/S7GS8=; X-AuditID: c1b4fb3a-335ff700000037f2-ee-5a71fdc0eb06 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id B6.B6.14322.0CDF17A5; Wed, 31 Jan 2018 18:32:49 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 18:32:48 +0100 From: Christer Holmberg To: Mickey Arnold , SIPCORE Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Mickey's comments Thread-Index: AdOauZCm8kyPGPeqSAKSD5NM1U1GKQ== Date: Wed, 31 Jan 2018 17:32:47 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14C19B@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.149] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM2K7ge7Bv4VRBjsfslgcbtnIbvH1xyY2 ByaPJUt+MnkcvTmXOYApissmJTUnsyy1SN8ugSvjxftO9oJN4hVf248zNzDeF+pi5OSQEDCR aPp8jqWLkYtDSOAwo8Tie6eYIZwljBI/f59m6mLk4GATsJDo/qcN0iAi4CvRtWA2K4gtLOAj MXNFIwtMfN/5S2DlIgJ6Es+/5oOEWQRUJaYff8kEYvMClWycPoENxGYUEJP4fmoNWJxZQFzi 1pP5TBD3CEgs2XOeGcIWlXj5+B8rhK0ksfbwdhaIeh2JBbs/sUHY2hLLFr5mhpgvKHFy5hOW CYxCs5CMnYWkZRaSlllIWhYwsqxiFC1OLS7OTTcy0kstykwuLs7P08tLLdnECAzug1t+W+1g PPjc8RCjAAejEg/vz8+FUUKsiWXFlbmHGCU4mJVEePdcBArxpiRWVqUW5ccXleakFh9ilOZg URLndUqziBISSE8sSc1OTS1ILYLJMnFwSjUw6hst/2z1z4L/7KeuVZbPX+s3hU1Ka/SbzbN3 ooZCnN/rum5+pvvPwyZd0Ckp0zo88ap+T0UL59ko1v1PjwomF8utv1E7jYmxJGjqkh+3ojep 31p+WP7JoTd6As2lKze5nI+0efIkxDNYdkZ7vHnX4nkNbzLE5xVyRYVfn2Rw0nv7qnCJ7VL8 SizFGYmGWsxFxYkAEFEzW2oCAAA= Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Mickey's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 17:32:53 -0000 Hi Mickey, Thanks for your review! Please see inline. -- Major comment -- >Section 1: > The proxy can use the > receipt of the REGISTER request as a trigger to forward SIP request > towards the UA, using normal SIP routing procedures. > >Section 4: > If the SIP proxy triggered > the push notification because it wants to forward a SIP request > towards the UA, the receipt of the REGISTER request can be used by > the proxy as a trigger to forward the request. > >Section 5.3: > As the push notification will trigger the SIP UA to perform a re- > registration, the SIP proxy can use the receipt of the SIP REGISTER > request as a trigger to forward SIP request towards the UA. > > The SIP proxy should only be allowed to use the received (or generated if= the Proxy contains the registrar functionality) 200 OK > response to the REGISTER as a trigger to send on the queued message. Othe= rwise the proxy will be re-routing based on a unconfirmed=20 > REGISTER request. If the reregister fails then the proxy has forwarded th= e INVITE or OOD request on to a contact URI that is not stored=20 > in the registrar. This would likely cause the call to fail but also raise= s security concerns where a well-timed re-register with incorrect=20 > SIP authentication by a 3rd party could "steal" a SIP message. That's a good point. Obviously, since the SIP request has been forwarded to begin with, the regi= stration is considered active. But, some registration information may have = changed in the triggered REGISTER request, and then the REGISTER needs to b= e accepted before the request is forwarded. =3D=3D=3D=3D=3D -- Minor comments -- >Typo in Section 1. I think >"Some are based on there standardized mechanism..." >Should be >"Some are based on the standardized mechanism..." Will fix as suggested. >Section 1 >Consider adding a mention of the feature capabilities indicator. Will be added. >Section 3 >Consider clarifying that PRID need only be unique per PNS. Also consider c= larifying that this mechanism is only=20 >appropriate for notification systems that provide such a token. I think all notification systems provide some kind of token (otherwise, how= would the push notification be routed?). But, I can add a note clarifying = it. Regards, Christer -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of A. Jean Mahone= y Sent: 25 January 2018 20:35 To: SIPCORE Subject: [sipcore] WGLC: draft-ietf-sipcore-sip-push Hi all, Working Group Last Call starts today for draft-ietf-sipcore-sip-push. https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ Please provide any feedback to the sipcore mailing list by Friday, February= 9th. Thanks! Jean _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Jan 31 09:36:20 2018 Return-Path: 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 324AD12EC4A for ; Wed, 31 Jan 2018 09:36:18 -0800 (PST) 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 RzCqczPNwCF0 for ; Wed, 31 Jan 2018 09:36:16 -0800 (PST) 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 5203A12EC4C for ; Wed, 31 Jan 2018 09:35:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517420157; 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=Nib4fCxLxDeYzU5TzGPIUfdqX5IJU3X0SJguFg6NzfY=; b=b7MMGD8EzeJr4h7r6LxcJHoLadnMNTFYkLvTHujRWql+7gx9ozlrAjW1iTNEs9/h PDlV9bctkMNmwwmEhslMCn3JiRgY2Wsh5RTeee9yGHOmARkHnubjg9WhcYwoEOw2 mIIU5iI4rHpC2y9BODxRiYwvOlT+GOt/i4V+5yiqWlU=; X-AuditID: c1b4fb25-48bff7000000341b-a3-5a71fe7d5441 Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 35.E0.13339.D7EF17A5; Wed, 31 Jan 2018 18:35:57 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 18:35:57 +0100 From: Christer Holmberg To: Liviu Chircu , "sipcore@ietf.org" Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Editorial Comments - Liviu's comments Thread-Index: AdOaudemZVs5nL4DRKSATpfGYlNi9w== Date: Wed, 31 Jan 2018 17:35:56 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14C1D1@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.149] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM2K7h27tv8Iog7WPNCw+bG1ms/j6YxOb A5PHkiU/mTyevbjEGsAUxWWTkpqTWZZapG+XwJVxdPl19oIZPBX7Tno2MH7g7mLk5JAQMJHo /n2EpYuRi0NI4DCjxJyJe5ghnCWMEtN7vgFlODjYBCwkuv9pgzSICPhIvPoxgQnEFhZIkti/ 6xgLRDxZ4tSum2DlIgJ6Ej97kkHCLAKqEl+u7GMDsXkFfCVOz5jDDGIzCohJfD+1BmwMs4C4 xK0n85kg7hGQWLLnPDOELSrx8vE/VghbSWLt4e1g45kFNCXW79KHaFWUmNL9kB1ivKDEyZlP WCYwCs1CMnUWQscsJB2zkHQsYGRZxShanFqclJtuZKyXWpSZXFycn6eXl1qyiREY1ge3/Fbd wXj5jeMhRgEORiUe3tWfC6OEWBPLiitzDzFKcDArifDuuQgU4k1JrKxKLcqPLyrNSS0+xCjN waIkznvSkzdKSCA9sSQ1OzW1ILUIJsvEwSnVwJh2aT1DW0Ou/kmBE05mE4+wHeufVtPpODng RDPX7q61vXJ+U5xXt7QrtqulHv7Z6+wceDsswC6j8Xnvievn/aUlHzeWG3O31MVxtRvfCDqj 4cVYa8PtIqShlB/DHC/4XZk5idt4zbmJ/bOjLfaJz762dE3jM0d+xxk60yVLjvnUybSyPnmt xFKckWioxVxUnAgAfLWjr2cCAAA= Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Editorial Comments - Liviu's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 17:36:18 -0000 SGkgTGl2aXUsDQoNClRoYW5rcyBmb3IgeW91ciBjb21tZW50cyEgUGxlYXNlIHNlZSBpbmxpbmUu DQoNCj5JIHNwb3R0ZWQgc29tZSBtaW5vciBudWlzYW5jZXM6DQo+DQo+U2VjdGlvbiA3LjEgLSB0 eXBvDQo+DQo+IMKgIjU1NSAoUHVzaCBOb3RmaWNpYXRpb24gU2VydmljZSBOb3QgU3VwcG9ydGVk KSINCg0KV2lsbCBiZSBmaXhlZC4NCg0KLS0tDQoNCj5TZWN0aW9uIDcuMiAtIGluY29uc2lzdGVu Y3kgKHBvc3NpYmx5IGR1ZSB0byBhbiBvbGQgaXRlcmF0aW9uKQ0KPg0KPlRoZSBCTkYgZ3JhbW1h ciBkZWZpbmVzIGEgc2VyaWVzIG9mICJwbi0qIiBwYXJhbXMsIHlldCB0aGUgbGFzdCBzZW50ZW5j ZSByZWZlcmVuY2VzIGEgY291cGxlIG9mIHVuZGVmaW5lZCAicG5zLSoiIHBhcmFtczoNCj4NCj4i VGhlIGZvcm1hdCBhbmQgc2VtYW50aWNzIG9mIHBucy1wYXJhbSBpcyBzcGVjaWZpYyB0byBhIGdp dmVuIHBucy1wcm92aWRlciB2YWx1ZS4iDQoNCldpbGwgYmUgZml4ZWQuDQoNClJlZ2FyZHMsDQoN CkNocmlzdGVyDQoNCg0KDQoNCg0KDQpPbiAyNS4wMS4yMDE4IDIyOjM1LCBBLiBKZWFuIE1haG9u ZXkgd3JvdGU6DQo+IEhpIGFsbCwNCj4NCj4gV29ya2luZyBHcm91cCBMYXN0IENhbGwgc3RhcnRz IHRvZGF5IGZvciBkcmFmdC1pZXRmLXNpcGNvcmUtc2lwLXB1c2guDQo+DQo+IGh0dHBzOi8vZGF0 YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtc2lwY29yZS1zaXAtcHVzaC8NCj4NCj4g UGxlYXNlIHByb3ZpZGUgYW55IGZlZWRiYWNrIHRvIHRoZSBzaXBjb3JlIG1haWxpbmcgbGlzdCBi eSBGcmlkYXksIA0KPiBGZWJydWFyeSA5dGguDQo+DQo+DQo+IFRoYW5rcyENCj4NCj4gSmVhbg0K Pg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBz aXBjb3JlIG1haWxpbmcgbGlzdA0KPiBzaXBjb3JlQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3Lmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwY29yZQ0KDQpfX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fXw0Kc2lwY29yZSBtYWlsaW5nIGxpc3QNCnNpcGNvcmVA aWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwY29yZQ0K From nobody Wed Jan 31 09:42:58 2018 Return-Path: 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 50189126DCA for ; Wed, 31 Jan 2018 09:42:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.321 X-Spam-Level: X-Spam-Status: No, score=-4.321 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] 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 Aq1RVZ2fLwQr for ; Wed, 31 Jan 2018 09:42:56 -0800 (PST) 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 B3C7912EAED for ; Wed, 31 Jan 2018 09:42:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517420574; 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=fwL1ZBSKiiNmhm5meILjK5nY8VEabFdKJ4q4y88ag0Q=; b=Ff9i82eV+yU6RnxUfR4Zeb6c4eanNNN9ZfSq6n29Yz/Cwo4RqWAQyEXXNqVAzoa6 +8r5enHaV6yXLbzY6GMYGNUjmV4Pcf1Y+6spi+cpwuHyNoBntZHm79TMIJBK33D1 FoJPk1Ve8CKFaAYpRp7nY46CD1HzGgcWiDfC9ta0Q/U=; X-AuditID: c1b4fb25-859119c00000341b-97-5a72001d5d2c Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 2A.D1.13339.D10027A5; Wed, 31 Jan 2018 18:42:54 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 18:42:39 +0100 From: Christer Holmberg To: Liviu Chircu , "sipcore@ietf.org" Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments Thread-Index: AdOarhvXN/SIYCSZQy2pLjQXhqV0ev//+i8A///iQ0A= Date: Wed, 31 Jan 2018 17:42:39 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14C20C@ESESSMB109.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> <1d25dfde-8d78-9820-0cbb-c44815fa644e@opensips.org> In-Reply-To: <1d25dfde-8d78-9820-0cbb-c44815fa644e@opensips.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.149] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM2J7iK4cQ1GUwf0eNosPW5vZLL7+2MTm wOSxZMlPJo9nLy6xBjBFcdmkpOZklqUW6dslcGV8PvGBveAdb8WsEy2sDYwHeLsYOTgkBEwk rrU6dDFycQgJHGaUmPDoLCuEs4RRovPeBxaQIjYBC4nuf9pdjJwcIgI+Eq9+TGACCQsLeEs8 7eCFCZ/qecMCYVtJ7F/WzApiswioSpz6tAbM5hXwlThxZQUzxPhmRoldc7+zgSQ4BRwkGlaf ZAKxGQXEJL6fWgNmMwuIS9x6Mh/MlhAQkFiy5zwzhC0q8fLxP1YIW0li7eHtYGcyC2hKrN+l D9GqKDGl+yE7xF5BiZMzn7BMYBSZhWTqLISOWUg6ZiHpWMDIsopRtDi1OCk33chYL7UoM7m4 OD9PLy+1ZBMjMBIObvmtuoPx8hvHQ4wCHIxKPLyrPxdGCbEmlhVX5h5ilOBgVhLh3XMRKMSb klhZlVqUH19UmpNafIhRmoNFSZz3pCdvlJBAemJJanZqakFqEUyWiYNTqoEx/MRn15mnHhyd kHSvqESyfd+iNO+dyZNeT2U3X69UPGuSQ1io8N8MxWPxFzRyHb+sL3n3RiBYdPeHtCr35dzP DmzjZKtn93jySE+ig6nnj7DuJGYlw/u3FfZJpidYNmTxZKTbhty62e/PzdCjP1Fj1uZNDnXr jstK+L2+tLZG/ku/3pqXmRJKLMUZiYZazEXFiQAUssHpgAIAAA== Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 17:42:57 -0000 SGkgTGl2aXUsDQoNCj4+PiAzLiBEb2VzIHRoZSBwcm94eSBzdHJpcCB0aGUgcG4tWFhYIHBhcmFt ZXRlcnMgd2hlbiBmb3J3YXJkaW5nIG1lc3NhZ2UgDQo+Pj4gdG8gdGhlIGNsaWVudCBvciBhcmUg dGhleSBrZXB0PyBEb2VzIGl0IHN0cmlwIHRoZW0gd2hlbiBjb21wYXJpbmcgDQo+Pj4gY29udGFj dCByZWdpc3RyYXRpb24gVVJJPyBXaXRob3V0IHRoaXMsIGNoYW5nZSBpbiBwbi1YWFggcGFyYW1l dGVycyB3aWxsIHJlc3VsdCBpbiBhIG5ldyByZWdpc3RyYXRpb24gaW5zdGVhZCBvZiBleGlzdGlu ZyByZWdpc3RyYXRpb24gdXBkYXRlLg0KPj4gVGhlcmUgaXMgbm8gc3RyaXBwaW5nIG9mIHBhcmFt ZXRlcnMuIFRoZSBwbi0gcGFyYW1ldGVycyB3aWxsIHR5cGljYWxseSBub3QgY2hhbmdlIGJldHdl ZW4gVUEgZGV2aWNlIHJlYm9vdHMuIEJ1dCwgaWYgdGhleSBkbywgaXQgZG9lcyByZXF1aXJlIGEg bmV3IHJlZ2lzdHJhdGlvbi4NCj4+DQo+IFRoZW4gd2hhdCBoYXBwZW5zIGlmIGEgInBuLVhYWCIg ZW5hYmxlZCBJTlZJVEUgUi1VUkkgZnJvbSBVQSAiYSIgdG8gVUEgImIiIHRyYXZlcnNlcyBhIGNo YWluIG9mIFNJUCBwcm94aWVzIHdoaWNoIGFyZSBhbGwgInNpcC1wdXNoIiBhd2FyZT8gDQo+IFdp bGwgdGhleSBub3QgZWFjaCBwZXJmb3JtIHRoZSBmb2xsb3dpbmc6DQo+DQo+IMKgwqDCoCAqIGxh dW5jaCBQTlMgcHJvdmlkZXIgcXVlcnkNCj4gwqDCoMKgICogd2FpdCBmb3IgcmUtUkVHSVNURVIN Cj4gwqDCoMKgICogZm9yd2FyZCBJTlZJVEUgdG8gdGhlIG5leHQgInNpcC1wdXNoIiBhd2FyZSBw cm94eQ0KDQpUaGUgUi1VUkkgd2lsbCBvbmx5IHRyYXZlcnNlIGJldHdlZW4gdGhlIFVBIGFuZCBp dHMgcmVnaXN0cmFyLg0KDQpNeSBhc3N1bXB0aW9uIGhhcyBiZWVuIHRoYXQgdGhlIG9wZXJhdG9y IGNvbmZpZ3VyZXMgdGhlIG5ldHdvcmsgaW4gYSB3YXkgdGhhdCB0aGVyZSBpcyBvbmx5IG9uZSBT SVAgcHJveHkgZG9pbmcgdGhlIHB1c2guDQoNCkhvd2V2ZXIsIGlmIHBlb3BsZSB0aGluayB3ZSBj YW4ndCBtYWtlIHN1Y2ggYXNzdW1wdGlvbiBJIGd1ZXNzIG9uZSBvcHRpb24gd291bGQgYmUgdGhh dCB0aGUgcHJveHkgc3VwcG9ydGluZyB0aGUgcHVzaCB3b3VsZCBpbnNlcnQgZS5nLiwgdGhlIHNp cC5wbnMgZmVhdHVyZS1jYXBhYmlsaXR5IGluZGljYXRvciBpbiB0aGUgUkVHSVNURVIgcmVxdWVz dCwgaW4gb3JkZXIgdG8gaW5mb3JtIGRvd25zdHJlYW0gcHJveGllcyB0aGF0IHRoZXkgZG9uJ3Qg aGF2ZSB0byBkbyBpdC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K From nobody Wed Jan 31 11:07:20 2018 Return-Path: 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 3A1F812EBF0 for ; Wed, 31 Jan 2018 11:07:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.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 NiTZBkilcjiD for ; Wed, 31 Jan 2018 11:07:16 -0800 (PST) Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0605C129C6C for ; Wed, 31 Jan 2018 11:07:16 -0800 (PST) Received: by mail-pf0-x22b.google.com with SMTP id 17so12182085pfw.11 for ; Wed, 31 Jan 2018 11:07:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qdA3fFzWWo5tCeurvUnO3TDkci8/7UZiCq+k3brwukU=; b=cEQaaIsW3jD+qLKmXcr9s8OU8hNkfCKqDyw0yw2Cu/y4RNUwbXVplKeXabSIMon41u ovGOXli/KO09WNEnq0wc4kW6ZxhR0YdqFl7lVtW1FWGzUNRUHRVDo1lKmAqJnXdWf66R b7aKkjtpPIxoo9vlcn3VIQSMTxd9cq2SBJyFG8IF7TYGwnrFtI0NjkbULpLtTkdLEzuh bwMY4Djxg3nandPLRf6cJdgEtTglg/xPL5xgUhDDsfShKtBMMW4cAT0soBaAV005/8eI pLXTiIKMAUZve+2gFAAhoaEqbqbBWE7erjzfCxySmwE+ob2cVSl/bekDih7jRMSO/adR ZHtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qdA3fFzWWo5tCeurvUnO3TDkci8/7UZiCq+k3brwukU=; b=lQcNG8TNxfFU2vwEMxuc8jjneJmfZH4UsUqA1g98VHBhb3X5t9rSUJaMcc+q6YClj6 X8kRLXCRXPFi40qMWQ7uYcu1l/k4VkjdW5oWkkMVVmBANSc44NfPxJ6uadZxwCp9SVhi VYwUxbX77TJAoAMId8PbXDMvABVwsffRNVx4PMAy5x6drPTO0/yHEaNmujoJ051hBdaR U8K9REHPeK6hnZ0zx5gqHa2yCMMhTtqi2Zcv+dqJd9cXQMV2Lo9c9mIp8Q7inxoqY0EV pez6RrUobJJc4ex/ydOYX0oOTljVOYhDLI0YbLvfDwEPMPpCO0UZXV9TessFP6Avnq1v JLDw== X-Gm-Message-State: AKwxytccyr5Sfs+IptAkh9YDGlKNEbg/dBysFWgDLya4+yyxzOjgVQIw PpPip8AZS/6QPQVAy85SOPE4MC5l X-Google-Smtp-Source: AH8x225tgw8XmaOMYzYsK3LXJkjCgkZudcnpaJSQ2ZTCKAtHWi1LyBFR2FNpjXlm9yL3em8a+4sEMQ== X-Received: by 10.98.155.157 with SMTP id e29mr34373909pfk.78.1517425635369; Wed, 31 Jan 2018 11:07:15 -0800 (PST) Received: from mail-pf0-f178.google.com (mail-pf0-f178.google.com. [209.85.192.178]) by smtp.gmail.com with ESMTPSA id q10sm37260370pff.181.2018.01.31.11.07.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 11:07:14 -0800 (PST) Received: by mail-pf0-f178.google.com with SMTP id e76so13641021pfk.1 for ; Wed, 31 Jan 2018 11:07:14 -0800 (PST) X-Received: by 10.98.162.10 with SMTP id m10mr34315205pff.168.1517425634072; Wed, 31 Jan 2018 11:07:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.191.3 with HTTP; Wed, 31 Jan 2018 11:07:13 -0800 (PST) In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> From: Roman Shpount Date: Wed, 31 Jan 2018 14:07:13 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Christer Holmberg Cc: SIPCORE , "A. Jean Mahoney" Content-Type: multipart/alternative; boundary="f4030437dbcce475630564172fed" Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 19:07:18 -0000 --f4030437dbcce475630564172fed Content-Type: text/plain; charset="UTF-8" Hi Christer, On Wed, Jan 31, 2018 at 11:37 AM, Christer Holmberg < christer.holmberg@ericsson.com> wrote: > >Our solution for the similar problem was to store the message and only > transmit it when registration from the client was received. > > Correct. And, that is described in the following paragraph :) > > The reason for allowing the request to be forwarded before the REGISTER > arrives is more an optimization, in case the connection between the UA and > proxy is still available from a previous session. > OK, this makes sense. >2. Does this document always require for a SIP Proxy to send regular timer > based push messages to keep SIP Registrations > >active? Such policy will result in additional load and cost for the SIP > Service operator. In most cases client application can > >be woken up on timer and does not need this, so this should be optional > and controlled by pn-XXX parameter. > > At least in the case of iOS, the application can NOT be woken up by an > application timer, as far as I understand. Push (or user interaction) is > the only way to wake the application :) > > (There used to be a "VoIP mode" in iOS, but it has been deprecated.) > > But, in general, re-registrations are normally not that frequent, so I > don't think it will cause too much load. > I think in case of Android you can setup a wake up timer. Depending on the number of registered users vs number of concurrent calls SIP Registrations can create quite a significant portion of the load. Having an option not to trigger the push notification when client can send a new registration would be useful. Another way to approach is for the push enabled proxy to specify the interval after which it intends to refresh the registration. This way SIP client can send a registration refresh slightly earlier and avoid the push notification. > >3. Does the proxy strip the pn-XXX parameters when forwarding message to > the client or are they kept? Does it strip > >them when comparing contact registration URI? Without this, change in > pn-XXX parameters will result in a new registration > >instead of existing registration update. > > There is no stripping of parameters. The pn- parameters will typically not > change between UA device reboots. But, if they do, it does require a new > registration. > > This makes sense. I think sip.instance with reg-id can be used to maintain the same registration and change the pn-xxx parameters at the same time. Regards, ______________ Roman Shpount --f4030437dbcce475630564172fed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Christer,

On Wed, Jan 31, 2018 at 1= 1:37 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>Our solution for the similar problem was to store the= message and only transmit it when registration from the client was receive= d.

Correct. And, that is described in the following paragraph :)

The reason for allowing the request to be forwarded before the REGISTER arr= ives is more an optimization, in case the connection between the UA and pro= xy is still available from a previous session.

OK, this makes sense.=C2=A0

>2. Does this document always require for a SIP Proxy to s= end regular timer based push messages to keep SIP Registrations
>active? Such policy will result in additional load and cost for the SIP= Service operator. In most cases client application can
>be woken up on timer and does not need this, so this should be optional= and controlled by pn-XXX parameter.

At least in the case of iOS, the application can NOT be woken up by an appl= ication timer, as far as I understand. Push (or user interaction) is the on= ly way to wake the application :)

(There used to be a "VoIP mode" in iOS, but it has been deprecate= d.)

But, in general, re-registrations are normally not that frequent, so I don&= #39;t think it will cause too much load.

I think in case of Android you can setup a wake up timer. Depending on th= e number of registered users vs number of concurrent calls SIP Registration= s can create quite a significant portion of the load. Having an option not = to trigger the push notification when client can send a new registration wo= uld be useful.

>3. Does the proxy strip the pn-XXX parameters = when forwarding message to the client or are they kept? Does it strip
>them when comparing contact registration URI? Without this, change in p= n-XXX parameters will result in a new registration
>instead of existing registration update.

There is no stripping of parameters. The pn- parameters will typically not = change between UA device reboots. But, if they do, it does require a new re= gistration.

=C2=A0
This makes sense. I think sip.instan= ce with reg-id can be used to maintain the same registration and change the= pn-xxx parameters at the same time.

Regards,
______________
Roman Shpount=C2=A0
--f4030437dbcce475630564172fed-- From nobody Wed Jan 31 13:27:46 2018 Return-Path: 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 0CAC712FAAE for ; Wed, 31 Jan 2018 13:27:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.321 X-Spam-Level: X-Spam-Status: No, score=-4.321 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] 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 TWQI3MH7_ScR for ; Wed, 31 Jan 2018 13:27:44 -0800 (PST) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 6A0DD12EBAB for ; Wed, 31 Jan 2018 13:27:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517434062; 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=XQv2Ud5/gH3ijdsk8q7+MFmFrQZBQ5R2Uon107WynzY=; b=d74Aj0uDD5x4zSjzrJs1U4HkO8cW4lwEVL1a7YGuYiEiNODHkspBzbFynFodow+6 nsN7Xj4i10UP8JSNL1buifi3ObEBRMse2z+X7qRMvxrXtE1taxOce6FyotzoferG kI7NYLPDZMEq39dkC/uoq5oXSsFQM12/83sWuAaxtSc=; X-AuditID: c1b4fb30-d49ff70000006bc7-ef-5a7234ceb370 Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id CB.75.27591.EC4327A5; Wed, 31 Jan 2018 22:27:42 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 22:27:42 +0100 From: Christer Holmberg To: Roman Shpount CC: SIPCORE , "A. Jean Mahoney" Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments Thread-Index: AdOarhvXN/SIYCSZQy2pLjQXhqV0egAEDXqAAAbafaA= Date: Wed, 31 Jan 2018 21:27:41 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14CAE2@ESESSMB109.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.154] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbFdWvecSVGUwan5ehYNnStZLWZcmMps 8fXHJjYHZo8lS34yecza+YTF49aUggDmKC6blNSczLLUIn27BK6MS9evsBYckq1YMvM7UwPj A5kuRk4OCQETie5NR5i6GLk4hAQOM0qc2PACylnCKLGw8SdbFyMHB5uAhUT3P22QBhEBVYm/ 3yczgdjMAu4SHfvWsIKUCAt4Szzt4IUo8ZE41fOGBcK2ktiwuh/MZgFqPX99IRuIzSvgK7Hp xV82iFVTgPau72AFSXAKBEr8mvodrIFRQEzi+6k1ULvEJW49mc8EcbSAxJI955khbFGJl4// sULYShKLbn9mArmHWUBTYv0ufYhWRYkp3Q/ZIfYKSpyc+YRlAqPoLCRTZyF0zELSMQtJxwJG llWMosWpxUm56UZGeqlFmcnFxfl5enmpJZsYgVFzcMtvgx2ML587HmIU4GBU4uG9rVkUJcSa WFZcmXuIUYKDWUmEd6MIUIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvSU/eKCGB9MSS1OzU1ILU IpgsEwenVAOjVNqn7yr35n393eHGHcbHu7es9uWJMK1Jlpy9jO3cpz/fjzv789GmA3czHS8+ 62W5Ypz1ufzqTz2Vj2+vRLjve3bAMaC5T7Td4UbhXt6NeYteXlJ/9mKqX+DaCPu14qeSLRVP 2RUzOHXo3yphl3zOG7r6ZcBf2wV/SlREuu6xSkw0ZLimprldiaU4I9FQi7moOBEAGc5UFJYC AAA= Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:27:46 -0000 SGksDQoNCj4+T3VyIHNvbHV0aW9uIGZvciB0aGUgc2ltaWxhciBwcm9ibGVtIHdhcyB0byBzdG9y ZSB0aGUgbWVzc2FnZSBhbmQgb25seSB0cmFuc21pdCBpdCB3aGVuIHJlZ2lzdHJhdGlvbiBmcm9t IHRoZSBjbGllbnQgd2FzIHJlY2VpdmVkLg0KPg0KPkNvcnJlY3QuIEFuZCwgdGhhdCBpcyBkZXNj cmliZWQgaW4gdGhlIGZvbGxvd2luZyBwYXJhZ3JhcGggOikNCj4NCj4+VGhlIHJlYXNvbiBmb3Ig YWxsb3dpbmcgdGhlIHJlcXVlc3QgdG8gYmUgZm9yd2FyZGVkIGJlZm9yZSB0aGUgUkVHSVNURVIg YXJyaXZlcyBpcyBtb3JlIGFuIG9wdGltaXphdGlvbiwgaW4gY2FzZSB0aGUgDQo+PmNvbm5lY3Rp b24gYmV0d2VlbiB0aGUgVUEgYW5kIHByb3h5IGlzIHN0aWxsIGF2YWlsYWJsZSBmcm9tIGEgcHJl dmlvdXMgc2Vzc2lvbi4NCj4NCj5PSywgdGhpcyBtYWtlcyBzZW5zZS7CoA0KDQpIb3dldmVyLCBN aWNrZXkgY29tbWVudGVkIHRoYXQgb25lIHNob3VsZCB3YWl0IGZvciB0aGUgUkVHSVNURVIgcmVz cG9uc2UgYmVmb3JlIGZvcndhcmRpbmcgdGhlIHJlcXVlc3QuDQoNCi0tLQ0KDQo+Pj4yLiBEb2Vz IHRoaXMgZG9jdW1lbnQgYWx3YXlzIHJlcXVpcmUgZm9yIGEgU0lQIFByb3h5IHRvIHNlbmQgcmVn dWxhciB0aW1lciBiYXNlZCBwdXNoIG1lc3NhZ2VzIHRvIGtlZXAgU0lQIFJlZ2lzdHJhdGlvbnMN Cj4+PmFjdGl2ZT8gU3VjaCBwb2xpY3kgd2lsbCByZXN1bHQgaW4gYWRkaXRpb25hbCBsb2FkIGFu ZCBjb3N0IGZvciB0aGUgU0lQIFNlcnZpY2Ugb3BlcmF0b3IuIEluIG1vc3QgY2FzZXMgY2xpZW50 IGFwcGxpY2F0aW9uIGNhbg0KPj4+YmUgd29rZW4gdXAgb24gdGltZXIgYW5kIGRvZXMgbm90IG5l ZWQgdGhpcywgc28gdGhpcyBzaG91bGQgYmUgb3B0aW9uYWwgYW5kIGNvbnRyb2xsZWQgYnkgcG4t WFhYIHBhcmFtZXRlci4NCj4+DQo+PkF0IGxlYXN0IGluIHRoZSBjYXNlIG9mIGlPUywgdGhlIGFw cGxpY2F0aW9uIGNhbiBOT1QgYmUgd29rZW4gdXAgYnkgYW4gYXBwbGljYXRpb24gdGltZXIsIGFz IGZhciBhcyBJIHVuZGVyc3RhbmQuIFB1c2ggKG9yIHVzZXIgaW50ZXJhY3Rpb24pIGlzIHRoZSBv bmx5IHdheSB0byB3YWtlIHRoZSA+PmFwcGxpY2F0aW9uIDopDQo+Pg0KPj4oVGhlcmUgdXNlZCB0 byBiZSBhICJWb0lQIG1vZGUiIGluIGlPUywgYnV0IGl0IGhhcyBiZWVuIGRlcHJlY2F0ZWQuKQ0K Pj4NCj4+QnV0LCBpbiBnZW5lcmFsLCByZS1yZWdpc3RyYXRpb25zIGFyZSBub3JtYWxseSBub3Qg dGhhdCBmcmVxdWVudCwgc28gSSBkb24ndCB0aGluayBpdCB3aWxsIGNhdXNlIHRvbyBtdWNoIGxv YWQuDQo+DQo+SSB0aGluayBpbiBjYXNlIG9mIEFuZHJvaWQgeW91IGNhbiBzZXR1cCBhIHdha2Ug dXAgdGltZXIuIERlcGVuZGluZyBvbiB0aGUgbnVtYmVyIG9mIHJlZ2lzdGVyZWQgdXNlcnMgdnMg bnVtYmVyIG9mIGNvbmN1cnJlbnQgY2FsbHMgU0lQIFJlZ2lzdHJhdGlvbnMgY2FuIGNyZWF0ZSBx dWl0ZSBhID5zaWduaWZpY2FudCBwb3J0aW9uIG9mIHRoZSBsb2FkLiBIYXZpbmcgYW4gb3B0aW9u IG5vdCB0byB0cmlnZ2VyIHRoZSBwdXNoIG5vdGlmaWNhdGlvbiB3aGVuIGNsaWVudCBjYW4gc2Vu ZCBhIG5ldyByZWdpc3RyYXRpb24gd291bGQgYmUgdXNlZnVsLg0KPg0KPkFub3RoZXIgd2F5IHRv IGFwcHJvYWNoIGlzIGZvciB0aGUgcHVzaCBlbmFibGVkIHByb3h5IHRvIHNwZWNpZnkgdGhlIGlu dGVydmFsIGFmdGVyIHdoaWNoIGl0IGludGVuZHMgdG8gcmVmcmVzaCB0aGUgcmVnaXN0cmF0aW9u LiBUaGlzIHdheSBTSVAgY2xpZW50IGNhbiBzZW5kIGEgcmVnaXN0cmF0aW9uID5yZWZyZXNoIHNs aWdodGx5IGVhcmxpZXIgYW5kIGF2b2lkIHRoZSBwdXNoIG5vdGlmaWNhdGlvbi4NCsKgDQpOb3Qg c3VyZSBJIGZvbGxvdy4gSWYgdGhlIFVBIGNhbiB1c2UgYSB0aW1lciB0byB3YWtlIHVwLCBhbmQg c2VuZCBwZXJpb2RpYyByZS1yZWdpc3RyYXRpb25zIChvciB3aGF0ZXZlciBtZXNzYWdlcykgZm9y IGtlZXBpbmcgdGhlIGNvbm5lY3Rpb24gYWxpdmUsIHdoeSBkb2VzIHRoZSBVQSBoYXZlIHRvIHVz ZSBTSVAgcHVzaCB0byBiZWdpbiB3aXRoPw0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0K My4gRG9lcyB0aGUgcHJveHkgc3RyaXAgdGhlIHBuLVhYWCBwYXJhbWV0ZXJzIHdoZW4gZm9yd2Fy ZGluZyBtZXNzYWdlIHRvIHRoZSBjbGllbnQgb3IgYXJlIHRoZXkga2VwdD8gRG9lcyBpdCBzdHJp cA0KdGhlbSB3aGVuIGNvbXBhcmluZyBjb250YWN0IHJlZ2lzdHJhdGlvbiBVUkk/IFdpdGhvdXQg dGhpcywgY2hhbmdlIGluIHBuLVhYWCBwYXJhbWV0ZXJzIHdpbGwgcmVzdWx0IGluIGEgbmV3IHJl Z2lzdHJhdGlvbg0KaW5zdGVhZCBvZiBleGlzdGluZyByZWdpc3RyYXRpb24gdXBkYXRlLg0KDQpU aGVyZSBpcyBubyBzdHJpcHBpbmcgb2YgcGFyYW1ldGVycy4gVGhlIHBuLSBwYXJhbWV0ZXJzIHdp bGwgdHlwaWNhbGx5IG5vdCBjaGFuZ2UgYmV0d2VlbiBVQSBkZXZpY2UgcmVib290cy4gQnV0LCBp ZiB0aGV5IGRvLCBpdCBkb2VzIHJlcXVpcmUgYSBuZXcgcmVnaXN0cmF0aW9uLg0KwqANClRoaXMg bWFrZXMgc2Vuc2UuIEkgdGhpbmsgc2lwLmluc3RhbmNlIHdpdGggcmVnLWlkIGNhbiBiZSB1c2Vk IHRvIG1haW50YWluIHRoZSBzYW1lIHJlZ2lzdHJhdGlvbiBhbmQgY2hhbmdlIHRoZSBwbi14eHgg cGFyYW1ldGVycyBhdCB0aGUgc2FtZSB0aW1lLg0KDQoNCg0KUmVnYXJkcywNCl9fX19fX19fX19f X19fDQpSb21hbiBTaHBvdW50wqANCg== From nobody Wed Jan 31 13:55:03 2018 Return-Path: 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 C36F412FADE for ; Wed, 31 Jan 2018 13:55:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.888 X-Spam-Level: X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.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 35U2FdvXR4Iz for ; Wed, 31 Jan 2018 13:54:59 -0800 (PST) Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CFDB12FAD0 for ; Wed, 31 Jan 2018 13:54:59 -0800 (PST) Received: by mail-pf0-x230.google.com with SMTP id t5so14067226pfi.0 for ; Wed, 31 Jan 2018 13:54:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pCX8/74bmenQI67fWQmYuBoa8g+Zhn7YTWSwkbY4N7w=; b=nP2dh3Y+CLBkSPGPke8vQt4UHd0b7k50F3JhInkkzVLrvrpwR80d1Ugwgy5aRrfOqI eJauVk48cWPSKiNrHLxgrjcpZh/9Bd5/opSBkNcRc1eP7GPl2JtsfPErz9aorF2bGbw7 gNrSYHZvUF/Xz2xRDO95/XjHIxFLtxAh0eEPWoPnf6qufPGC6BPR89noCrXfD9OMStXv XnvSs0xWBBb1RwxMKNrQXuXNorOw4AXPFFOUCvRdVpoVAZpc3c+Jw0Zy9wHn0W/2bfVP OpS8I8jBkz5ujml3CfxiVxlSJtmlWpEmyJSe0PofANePKOPvPhYr/kfb/kUdbpFkh/h3 R6dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pCX8/74bmenQI67fWQmYuBoa8g+Zhn7YTWSwkbY4N7w=; b=ph0XpWmArtdaegnmlAEdB/o1w/K3V1CmYkcU4+dxOH8jQZ2NH3tOH22I8H3z/Vi9EH HKm/HfJsLNqGRw2W4zDqHJYDrz8wKXzOphAVBdSM+yanNkAeMAFObTi+VooOTX3xI2JO 8RC+dmomQLTkh6WhHyKQRgUhDXX8bS9S9AILlxIlHUeVE5I0YvnKH5hRwvg/+dLBXTlw 5blTZTB37OEib0ZIzWpVnJ0FH4+NUGFmzIKOExvZgZAHVyKu3reqyyobjMgfFcci4rsx L4tlfm0zwgt0nrfYYLP/jp4PV624y+8W7Xv8oFv+ayuMhlN+5BUAl5K88zgyvYhTNcIH iVaA== X-Gm-Message-State: AKwxyteQHI4zI0KyRzD5LgWDXwOKr0Cv+RGIWJ+K7tX3lqyvfyduwdOg kCeeLTSUqn/SDlQ38R9iSuLH28qN X-Google-Smtp-Source: AH8x224h4496CzqcvWg6QjQeJS5dFonndfuaXcsd7tHuVWB2v4m9gJ/ViF5D8heTPVVUeGh/iL2FuQ== X-Received: by 2002:a17:902:8c87:: with SMTP id t7-v6mr15991934plo.205.1517435698465; Wed, 31 Jan 2018 13:54:58 -0800 (PST) Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com. [209.85.192.182]) by smtp.gmail.com with ESMTPSA id n82sm45762675pfa.45.2018.01.31.13.54.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 13:54:57 -0800 (PST) Received: by mail-pf0-f182.google.com with SMTP id b25so14042311pfd.9 for ; Wed, 31 Jan 2018 13:54:57 -0800 (PST) X-Received: by 10.99.3.6 with SMTP id 6mr269302pgd.334.1517435697419; Wed, 31 Jan 2018 13:54:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.236.191.3 with HTTP; Wed, 31 Jan 2018 13:54:56 -0800 (PST) In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C14CAE2@ESESSMB109.ericsson.se> References: <7594FB04B1934943A5C02806D1A2204B6C14BD3B@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B6C14CAE2@ESESSMB109.ericsson.se> From: Roman Shpount Date: Wed, 31 Jan 2018 16:54:56 -0500 X-Gmail-Original-Message-ID: Message-ID: To: Christer Holmberg Cc: SIPCORE , "A. Jean Mahoney" Content-Type: multipart/alternative; boundary="001a114f3190b6dace05641987ba" Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Roman's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 21:55:02 -0000 --001a114f3190b6dace05641987ba Content-Type: text/plain; charset="UTF-8" On Wed, Jan 31, 2018 at 4:27 PM, Christer Holmberg < christer.holmberg@ericsson.com> wrote: > >>Our solution for the similar problem was to store the message and only > transmit it when registration from the client was received. > > > >Correct. And, that is described in the following paragraph :) > > > >>The reason for allowing the request to be forwarded before the REGISTER > arrives is more an optimization, in case the > >>connection between the UA and proxy is still available from a previous > session. > > > >OK, this makes sense. > > However, Mickey commented that one should wait for the REGISTER response > before forwarding the request. > Agreed. Registration would have to be properly verified and SIP message should only be sent if 200 OK response is sent to the Registration message. > >>>2. Does this document always require for a SIP Proxy to send regular > timer based push messages to keep SIP Registrations > >>>active? Such policy will result in additional load and cost for the SIP > Service operator. In most cases client application can > >>>be woken up on timer and does not need this, so this should be optional > and controlled by pn-XXX parameter. > >> > >>At least in the case of iOS, the application can NOT be woken up by an > application timer, as far as I understand. Push (or user interaction) is > the only way to wake the >>application :) > >> > >>(There used to be a "VoIP mode" in iOS, but it has been deprecated.) > >> > >>But, in general, re-registrations are normally not that frequent, so I > don't think it will cause too much load. > > > >I think in case of Android you can setup a wake up timer. Depending on > the number of registered users vs number of concurrent calls SIP > Registrations can create quite a >significant portion of the load. Having > an option not to trigger the push notification when client can send a new > registration would be useful. > > > >Another way to approach is for the push enabled proxy to specify the > interval after which it intends to refresh the registration. This way SIP > client can send a registration >refresh slightly earlier and avoid the push > notification. > > Not sure I follow. If the UA can use a timer to wake up, and send periodic > re-registrations (or whatever messages) for keeping the connection alive, > why does the UA have to use SIP push to begin with? > > Imagine an Android phone behind NAT. Without Push notification support it will need to wake up often enough to maintain NAT binding (every 30 sec or so creating huge load on both the client and the server). With push notifications it only needs to wake up often enough to maintain Registration (about once very hour). At the same time, if client can wake up on its own and send a registration, then push enabled proxy does not need to generate a push request -- less load on the proxy and fewer things to break. In general, I think it would be useful for the client to get some sort of indication that it should expect a registration refreshing push notification no sooner then in x seconds. So, in the registration response client will get indication that registration will expire in y seconds (expires URI parameter in contact or SIP header) and that push notification will be send no sooner then in x seconds (x < y). This additional value can be provided in something like pn-refresh Contact URL parameter. This way client can prevent the push notification by proactively sending registration. This value can also be extremely useful for debugging. Regards, _____________ Roman Shpount --001a114f3190b6dace05641987ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Wed, Jan 31, 2018 at 4:27 PM, Christer Holmberg <c= hrister.holmberg@ericsson.com> wrote:
>>Our solution for the similar problem wa= s to store the message and only transmit it when registration from the clie= nt was received.
>
>Correct. And, that is described in the following paragraph :)
>
>>The reason for allowing the request to be forwarded before the REGI= STER arrives is more an optimization, in case the
>>connection between the UA and proxy is still available from a previ= ous session.
>
>OK, this makes sense.=C2=A0

However, Mickey commented that one should wait for the REGISTER resp= onse before forwarding the request.

Agr= eed. Registration would have to be properly verified and SIP message should= only be sent if 200 OK response is sent to the Registration message.
=
=C2=A0
>>&g= t;2. Does this document always require for a SIP Proxy to send regular time= r based push messages to keep SIP Registrations
>>>active? Such policy will result in additional load and cost for= the SIP Service operator. In most cases client application can
>>>be woken up on timer and does not need this, so this should be = optional and controlled by pn-XXX parameter.
>>
>>At least in the case of iOS, the application can NOT be woken up by= an application timer, as far as I understand. Push (or user interaction) i= s the only way to wake the >>application :)
>>
>>(There used to be a "VoIP mode" in iOS, but it has been d= eprecated.)
>>
>>But, in general, re-registrations are normally not that frequent, s= o I don't think it will cause too much load.
>
>I think in case of Android you can setup a wake up timer. Depending on = the number of registered users vs number of concurrent calls SIP Registrati= ons can create quite a >significant portion of the load. Having an optio= n not to trigger the push notification when client can send a new registrat= ion would be useful.
>
>Another way to approach is for the push enabled proxy to specify the in= terval after which it intends to refresh the registration. This way SIP cli= ent can send a registration >refresh slightly earlier and avoid the push= notification.
=C2=A0
Not sure I follow. If the UA can use a timer to wake up, and send pe= riodic re-registrations (or whatever messages) for keeping the connection a= live, why does the UA have to use SIP push to begin with?


Imagine an Android phone behind NAT. W= ithout Push notification support it will need to wake up often enough to ma= intain NAT binding (every 30 sec or so creating huge load on both the clien= t and the server). With push notifications it only needs to wake up often e= nough to maintain Registration (about once very hour). At the same time, if= client can wake up on its own and send a registration, then push enabled p= roxy does not need to generate a push request -- less load on the proxy and= fewer things to break.

In general, I think it wou= ld be useful for the client to get some sort of indication that it should e= xpect a registration refreshing push notification no sooner then in x secon= ds. So, in the registration response client will get indication that regist= ration will expire in y seconds (expires URI parameter in contact or SIP he= ader) and that push notification will be send no sooner then in x seconds (= x < y). This additional value can be provided in something like pn-refre= sh Contact URL parameter. This way client can prevent the push notification= by proactively sending registration. This value can also be extremely usef= ul for debugging.

Regards,
<= div class=3D"gmail_signature">_____________
Roman Shpount
=C2=A0
--001a114f3190b6dace05641987ba-- From nobody Wed Jan 31 16:28:32 2018 Return-Path: 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 56D9C13145C for ; Wed, 31 Jan 2018 16:28:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MmhpS9bUp9Da for ; Wed, 31 Jan 2018 16:28:27 -0800 (PST) Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8B9131452 for ; Wed, 31 Jan 2018 16:28:25 -0800 (PST) Received: by mail-ot0-x231.google.com with SMTP id 73so6076056oti.12 for ; Wed, 31 Jan 2018 16:28:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s59OuxBqk1HxG19293vL+i433lMeKuicqhTQraCz1f8=; b=aiCf8FZdnwalJnOFTojuK647fIu36KBy+wfkLRxhtyougiUE1JRV1vQbYa8wunq0nn nkVPo01O3LX/2xcz2UibFKz5EjtqlIu9HOda5PWKGwX649usFC5rwhRACm+T8gjqYdo2 G2an8avYxg7y3gnvBEbTcPuXpkxIdf8zxPErqNXVBCvISqinkJUx1RDfWXtEYCp1MJ1M J4v0HyRvPq2XRd637zh2ZZIWC8c51BB3JMWDfTVlJ7fXbYDKc0JJQKdG54Nnoi/LEEfs fmCE0PdEQP4N9YfhqewCK/x0q45oE/eIgUgOjqEQQs04nsDMFqEeXbgBB0fkf35X5Iia QeKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s59OuxBqk1HxG19293vL+i433lMeKuicqhTQraCz1f8=; b=HhUX4O25ysTsE2VKnEe1q3pUQ8IZPbgZguweV5BeVbVIuVud/5Vxdsd3SoAKxuH+rs /XpuStjUFbcRA3kfnkaDoN8ZDtsOKXQiIPRsqx5UmdF92WRs5tmzLv8LrJXJZXiicHKN ZmuGEdBriO34i2cdWdVf7xI6uk4AMxmCO1YS0wRPykqW0hqaVDfkl/nCDO7NAQNDYPwj F5RREC+vQlw5TEQjD2z0+G0yjm6+R/tXxfoT3wYqbOFdFsXIKJYM76i6ZbKEGWgXRh8A SzSvWz4YMVeFo0IHy7Iveh7lnku5mecIebAnYsgE2QcMhIT6dfs1aw18AHzhZplYkaSB IM3A== X-Gm-Message-State: AKwxytdyQGr2k5YYD3UIl+bAjX3OqAUYnzqTedOHGB5wc+rCR5vV9RO6 hTls3e/wCmptSWXrTJZDgP3o1trM8cPgJZg1uZCp2CxP X-Google-Smtp-Source: AH8x226z+6xKu4XvscxP98iXch3KZ1DTEBzm3RkC5kox6nuTtc0zmmKcwofHugYByqtEC5qTAY2KeQ4W/w1+UAOpVJk= X-Received: by 10.157.50.132 with SMTP id u4mr2702911otb.133.1517444904678; Wed, 31 Jan 2018 16:28:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.52.249 with HTTP; Wed, 31 Jan 2018 16:28:24 -0800 (PST) In-Reply-To: References: From: Martin Thomson Date: Thu, 1 Feb 2018 11:28:24 +1100 Message-ID: To: "A. Jean Mahoney" Cc: SIPCORE Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 00:28:30 -0000 On Fri, Jan 26, 2018 at 7:35 AM, A. Jean Mahoney wrote: > Hi all, > > Working Group Last Call starts today for draft-ietf-sipcore-sip-push. > > https://datatracker.ietf.org/doc/draft-ietf-sipcore-sip-push/ > > Please provide any feedback to the sipcore mailing list by Friday, February > 9th. This document should not be published without significant changes. This document addresses a serious shortcoming. For a long time, we have had SIP UAs on mobile devices that are privileged by virtue of being developed and installed by the device vendor, but the nature of these platforms makes developing an alternative UA impossible. But it swaps one type of vendor lock-in for another. This is a rare case of a (intended for) proposed standard document enshrining proprietary protocols into the RFC series. And only proprietary protocols. No definition is added for RFC 8030, despite that having a well-documented (and deployed) protocol. The two proprietary protocols (for APNS and FCM) are not documented here, nor does the document normatively reference specifications for those protocols. Given that there are only two registered values for pn-provider, I don't see how this specification could be implemented by a proxy without information that is not normatively referenced. This document should discuss its relationship with RFC 5626 (outbound) and the existing mechanisms used to keep connections and NAT bindings between UA and proxy alive. My expectation is that if the parameters were supported connections would be allowed to drop and the push notification channel would be preferred. I don't understand why the terminology established in RFC 8030 wasn't used. It's well-defined and clear. The discussion about what is sent in the push notification message isn't actionable. It says that the payload is undefined. I think that is unwise. Either say that the payload is empty (which is possible) or it isn't. That raises the question of whether you care about authentication of the message. I don't think that it is as simple as saying that authentication isn't important - you need to explain why. RFC 8030 talks about the measures that it puts in place to ensure that user agents don't receive unwanted push messages, but now you have a whole spectrum of potential proprietary protocols and systems that could be used here, with unknown properties. Section 12.4 doesn't define the registration policy for the new registry. From nobody Wed Jan 31 22:32:31 2018 Return-Path: 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 3AD20127735 for ; Wed, 31 Jan 2018 22:32:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.321 X-Spam-Level: X-Spam-Status: No, score=-4.321 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] 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 Zn3rLn2WnSVh for ; Wed, 31 Jan 2018 22:32:28 -0800 (PST) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 47C2F12762F for ; Wed, 31 Jan 2018 22:32:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517466746; 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=LmeCglW2XXxA0/4vPlzUXdlCrQeQigyGjlxgfPkpnJo=; b=F9tVvuwZClBSf2S3lIg0hIt/DIkSxxA3XPr6NNV40LeBuDFSRr4qkYVTVKdpfd/d Lubq/QJiDd1JAd/GnRvZgx967wDIEBmFmBc/OG52I43+dzjDvE8MWuiTPNwxFYxB e0grUyz1uKq+p3xWzOy4uIDc8bZlqWnE0SfLFbOpWMo=; X-AuditID: c1b4fb3a-34dff700000037f2-3d-5a72b47a268f Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id FA.A1.14322.A74B27A5; Thu, 1 Feb 2018 07:32:26 +0100 (CET) Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0352.000; Thu, 1 Feb 2018 07:32:25 +0100 From: Christer Holmberg To: Martin Thomson , "A. Jean Mahoney" CC: SIPCORE Thread-Topic: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Martin's comments Thread-Index: AdObJnqq6c/Mum6qRQ+COrQnfoW9wQ== Date: Thu, 1 Feb 2018 06:32:25 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14D52E@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.149] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM2K7um7VlqIog6vbBCwaOleyWlw784/R 4uuPTWwOzB47Z91l91iy5CeTx6ydT1gCmKO4bFJSczLLUov07RK4Mr6838BasFyy4u6my2wN jMtEuhg5OSQETCQan55mA7GFBA4zShzuB7K5gOzFjBL3jjYDORwcbAIWEt3/tEFqRAQiJF50 zQerZxaQk7j+YSOYLSzgI9Hy4CAjRI2vxNJr/SwQtp7E8QPTmUBsFgEViXMLZoDZvEA1n2+d BqthFBCT+H5qDRPETHGJW0/mM0HcJiCxZM95ZghbVOLl43+sELaSxNrD21kg6nUkFuz+BHWP tsSyha+ZIeYLSpyc+YRlAqPwLCRjZyFpmYWkZRaSlgWMLKsYRYtTi4tz042M9FKLMpOLi/Pz 9PJSSzYxAiPh4JbfVjsYDz53PMQowMGoxMPrN78oSog1say4MvcQowQHs5II79UNQCHelMTK qtSi/Pii0pzU4kOM0hwsSuK8TmkWUUIC6YklqdmpqQWpRTBZJg5OqQbGjI1L9m5esL4yYGHU Aq8cwyTRuwkd1f3aJybYhEX/kDrm8NpvxsTH97fEJVezzn9ro2mr5Nz09mLqM4bDVx+elLli 9GvduWkNDpuOfA06I8/T7LN9ygLu2h3vTh7SzCoM8mVz4bVlr6yayBK8+sbhN4c17W7xzeOL PXlyxmod4T/TW3ktVNOtlViKMxINtZiLihMBqcCn84ACAAA= Archived-At: Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-sip-push - Martin's comments X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 06:32:30 -0000 Hi, > This document addresses a serious shortcoming. For a long time, we have = had SIP UAs on mobile devices that are privileged=20 > by virtue of being developed and installed by the device vendor, but the = nature of these platforms makes developing an alternative UA impossible. > > But it swaps one type of vendor lock-in for another. This is a rare case= of a (intended for) proposed standard document enshrining proprietary=20 > protocols into the RFC >series. And only proprietary protocols. No defi= nition is added for RFC 8030, despite that having a well-documented (and de= ployed) protocol. If you can provide pointers to RFC 8030-based services, I would love to inc= lude them. I assume the Mozilla Push Service is one of them? >The two proprietary protocols (for APNS and FCM) are not documented here, = nor does the document normatively reference specifications for those protoc= ols. Given that >there are only two registered values for pn-provider, I d= on't see how this specification could be implemented by a proxy without inf= ormation that is not normatively >referenced. The purpose of the document is not to define a push service, but to allow u= sage of existing ones with SIP. And, the documentation on how to use those = services is available. >This document should discuss its relationship with RFC 5626 (outbound) and= the existing mechanisms used to keep connections and NAT bindings between = UA and proxy >alive. My expectation is that if the parameters were support= ed connections would be allowed to drop and the push notification channel w= ould be preferred. Outbound uses periodic keep-alives, and the whole reason for this document = is applications that cannot wake up (using timers) in order to e.g., send s= uch keep-alives.=20 > I don't understand why the terminology established in RFC 8030 wasn't use= d. It's well-defined and clear. > The discussion about what is sent in the push notification message isn't = actionable. It says that the payload is undefined. I think that is unwise= .=20 > Either say that the payload is empty (which is possible) or it isn't. =20 This SIP push does not mandate any payload - in addition to what the push m= echanism itself may include. The reason it talks about payload was because you requested a reference to = RFC 8291 for allowing end-to-end encryption of possible payload.=20 > That raises the question of whether you care about authentication of the = message. > > I don't think that it is as simple as saying that authentication isn't im= portant - you need to explain why. =20 > RFC 8030 talks about the measures that it puts in place to ensure that us= er agents don't receive unwanted=20 > push messages, but now you have a whole spectrum of potential proprietary= protocols and systems that=20 > could be used here, with unknown properties. I am not saying that authentication is not important. The push services I a= m aware of do provide authentication. But, I see your point, and I will add some text about authentication. > Section 12.4 doesn't define the registration policy for the new registry. I'll look into that. Regards, Christer